IMHO, a conversation should behave exactly the same as the session
does today - per default. There is nothing elementary different just
because you can have a multitude of conversations per user.
regards,
Martin
On 9/8/07, Mario Ivankovits [EMAIL PROTECTED] wrote:
Simon,
If this element is
Like a scheduler within the webapp? this way i can have orchestra to keep
EntityManager round to do
lazy loading of a huge object.
Thanks
--
View this message in context:
http://www.nabble.com/-Orchestra--Does-Orchestra-work-with-non-web-client--tf4410349.html#a12581733
Sent from the My
Hi!
Like a scheduler within the webapp? this way i can have orchestra to keep
EntityManager round to do
lazy loading of a huge object.
No, many of Orchestra's data-structures are kept in the session scope
which is not available during a non http request.
Is there any reason to use
well, both of my webclient and scheduler call the same service bean, with
the help of
orchestra, the web client can have objects lazy loaded.
However, after the scheduler retreive it pojo via the service bean, the pojo
is put into
detached state and therefor I cannot load the rest when
