Thanks. Translating would make it easier to read… but also ruin the fun. :)
Robert > On Jan 22, 2015, at 1/222:03 AM , Poder, Jacob <jacob.po...@thermofisher.com> > wrote: > > Hi Robert, > > Sorry for the off-topic but I couldn't help notice your signature... easier > to read when translated to amino acids in reading frame 1 though :-) > Good one... > > Jacob Poder > > -----Original Message----- > From: Robert Zeigler [mailto:robert.zeig...@roxanemy.com] > Sent: 22. januar 2015 00:14 > To: Tapestry users > Subject: Re: Two fundamental questions. > > I haven't tried tapestry-cayenne with 5.4. I've been heavily involved in a > lot of other projects that don't involve tapestry or even java. That said, my > recollection is that the Library works with 5.3, at least. At some point, I > will migrate the code over to github, but that isn't likely to happen in the > next month or so. Still, the library had a lot of niceties for quickly > building cayenne-baked CRUD apps. I would be interested to hear whether it > works as is with 5.4. > > Robert > > GATAATGCTATTTCTTTAATTTTCGAA > >> On Jan 21, 2015, at 2:42 PM, zcsrs...@gmail.com wrote: >> >> Thank you Michael for your detailed comments. I will look into these >> once I am done with basic crud. >> >> On Wed, Jan 21, 2015 at 6:11 AM, Michael Gentry >> <mgen...@masslight.net> >> wrote: >> >>> Hi Charles, >>> >>> We generally don't use any kind of special integration with our >>> Tapestry+Cayenne applications here. A couple general scenarios are: >>> >>> 1. Your application is session-heavy (ours are). In this case you >>> store your Cayenne objects in your session objects >>> (page/component-based or >>> global) and reference them from your Tapestry pages/classes/components. >>> This can be a single Cayenne object or a List of Cayenne objects. >>> For Lists, you use the index when the user clicks on one to select it: >>> myListOfCayenneObjects.get(index). Typically, myListOfCayenneObjects >>> would come from a dataContext.performQuery(). >>> >>> 2. Your application is session-light and you use the Cayenne ID (in >>> the >>> URL) to restore your Cayenne objects between requests. If security >>> is a concern, you need to build in some additional access controls or >>> perhaps encrypt the Cayenne ID when you generate links and decrypt on >>> your next request. This can work well with onActivate/onPassivate, for >>> example. >>> >>> If you have more Cayenne-specific questions, you can ask on the >>> Cayenne User list, too (we are Tapestry-friendly there). >>> >>> mrg >>> >>> >>> On Tue, Jan 20, 2015 at 4:27 PM, Cheng Zhang >>> <charlesdenverj...@gmail.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> I am new to Tapestry. I have two questions. >>>> >>>> 1. What is the best solution for Tapestry-Cayenne integration? >>>> I found the only project is as below but it looks like no longer >>>> developed for over 4 years. And there are no many supporting >>>> documents. >>>> https://code.google.com/p/tapestry5-cayenne/ >>>> >>>> 2. I'd like to implement basic CRUD function with a group of data, >>>> eg show a list of Person(name, phone, address), update person >>>> information, add new person, delete a person from the list. >>>> I found there are several components might be used, like Editable >>>> Grid, Beaneditform, Editable loop. What is the best/widely used way >>>> to do CRUD? (just the java part, do not need to persist to DB). >>>> >>>> Many thanks. >>>> >>>> Charles >>>> >>>> -------------------------------------------------------------------- >>>> - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>>> For additional commands, e-mail: users-h...@tapestry.apache.org >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org