The work around to have scheduler's task to by pass the service bean and invoke the DAO beans directly with DAO's entity manager is manually injected by the scheduler's task
I think I have a good use case thou. -D Dan Tran wrote: > > 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 needed. > > Please keep in mind, my schedule'task knows nothing about entity manager. > > -D > > > > > > > Mario Ivankovits wrote: >> >> 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 Orchestra for a non-request-based lifecycle? >> I mean, once the scheduler triggers an event a new bean might be >> instantiated doing all the work and holding the entityManager until the >> process ends - should work pretty well with plain Spring I think. >> >> Could you please provide some additional infos about what you would like >> to do. >> >> Ciao, >> Mario >> >> >> > > -- View this message in context: http://www.nabble.com/-Orchestra--Does-Orchestra-work-with-non-web-client--tf4410349.html#a12605914 Sent from the My Faces - Dev mailing list archive at Nabble.com.
