Hi Lasitha, I don't know if the thread you pointed out is applicable to this topic, I started that one, the problem was due to the pesisted object, I finally solve that problem by removing the @Persist, now I'm trying to persist everything in the client side to avoid this problem(only the object id, reload in onActivate), and program has been working well. the persisted object seems causing problems from time to time, I made the following rule in my coding: use @Persist only when an object is @InjectPage to another page and some instances have to be set, otheriwse all @Persist free, the rule does work well, but I don't know if this is a correct conclusion:
You need @Persist only when the page will be injected? Thanks, A.C. lasitha wrote: > > On Nov 23, 2007 1:57 PM, lasitha <[EMAIL PROTECTED]> wrote: > > I guess i should also point out the following thread which proposes an > alternate solution, though i personally don't agree with it :) > http://www.nabble.com/T5%3A-how-to-use-a-detached-hibernate-object-in-a-form--tf4669657.html#a13339389 > Cheers, lasitha. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/-T5--A-Hibernate-question--tf4860162.html#a13909796 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
