One thing though: it's not always enough to store only the object's id: imagine the case of the collapsible panel, or a server side switched tabbed panel, where the full information is not always wrapped in the http-request. For these cases, you'll need to provide a possibility to save data in between requests without using the database directly or the HTTP parameters. What is your position on this?
regards, Martin On 4/3/06, Alexey Maslov <[EMAIL PROTECTED]> wrote: > > Hi, > > > > >A developer can get LazyInitializationException > > only > > >if he/she keeps a reference to the persistent > > object, > > >for instance storing it in HTTP session. We have > > >provided a simple and convenient abstraction - > > >ObjectProxy - that may be used to have a persistent > > >object reference that is always valid. > > > > Actually this is what I was looking for, spring also > > has a filter to apply > > the session per request pattern but the main problem > > is as you mentioned, > > keeping the reference in the http session causes > > lazy initialization errors. > > There are solutions for this like aspects, session > > merge, session lock but > > all of these are hard to apply. It is great if Rumba > > takes care of it simply > > using ObjectProxy. > > > > We do believe that Rumba should be as simple as > possible (...but not simpler :)). > > Regards, > Alexey > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
