agreed - that is one reason covered by: > it depends on the implementation (in the application)
regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2012/3/15 Mark Struberg <strub...@yahoo.de> > using a @TransactionScoped EM is possible, but if you already have all > your Services using a @RequestScoped EM, then you will not come far... > > LieGrue, > strub > > > > ----- Original Message ----- > > From: Gerhard Petracek <gerhard.petra...@gmail.com> > > To: MyFaces Discussion <users@myfaces.apache.org> > > Cc: > > Sent: Thursday, March 15, 2012 3:32 PM > > Subject: Re: [CODI] ThreadScoped / EntityManager in a new Thread > > > > hi thomas, > > > > see [1] -> you just have to switch to v1.0.4 > > > > regards, > > gerhard > > > > [1] https://issues.apache.org/jira/browse/EXTCDI-258 > > > > http://www.irian.at > > > > Your JSF/JavaEE powerhouse - > > JavaEE Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > > > > > > 2012/3/15 Thomas Andraschko <zoi...@googlemail.com> > > > >> Hi, > >> > >> In our webapp, we have an asynchronous XML sender and receiver and we > also > >> need db access with transactions in this thread. > >> Currently, our EntityManager is procuded in RequestScoped and will not > work > >> in a new thread. > >> > >> How can i solve this? > >> Does any ThreadScoped implementation exists? > >> > >> Thanks and best regards, > >> Thomas > >> > > >
