Yeah, I wasn't using transactions when reading data in service methods, using read-only transactions fixed my problem.
Now I can make most of the Orchestra features work with an exception. Whenever I try to remove an entity, I get message: "the detached instance cant be removed, try to merge it first". But that doesn't make sense because the backing bean that loads and tries to delete the entity is in conversation access scope, it is in the same unit of work so it's supposed to be the same entity manager. Cagatay On Thu, May 22, 2008 at 10:11 AM, Dan Tran <[EMAIL PROTECTED]> wrote: > > > Also, the most common problem with entity close is your service bean is not > marked as Transational. > > -D > > > Mario Ivankovits wrote: > > > > Hi Cagatay! > >> I'm trying to convert an existing application to use Orchestra. > >> Followed the installation documentation but I'm getting > >> org.hibernate.SessionException: Session is closed! exception after I > >> add Orchestra. Just cant make it work so far. > > Unfortunately I can't see anything obviously wrong in your configuration > > file. > > > > Is the Session closed issued after the first request or after an > > exception? > > > > Normally I'd think that there is some filter active which will close the > > session and that your application do not really use the Orchestra > > provided persistence context. > > No clue why this can happen. > > > > Probably debugging into Orchestra's JpaPersistenceContextFactory and see > > if the created PersistenceContext is the same you'll use in your method > > then will help. > > > > If you can't solve your problem and nobody else has a better idea we > > need to get in touch with your application, I think :-( > > > > > > Ciao, > > Mario > > > > > > > > -- > View this message in context: > http://www.nabble.com/-Orchestra--Session-is-closed-tp17367957p17398627.html > Sent from the MyFaces - Users mailing list archive at Nabble.com. > >
