Why don't you use EJB SessionBeans with TransactionManagement BEAN, and
inject (@EJB) this session bean in session scoped managed bean. This way
you can preserve transaction along multiple requests. And yes, use
Eclipselink (it has lazy loading ;) ).
On 07/02/2010 08:07 PM, Mike Kienenberger
mkien...@gmail.com
To: MyFaces Discussion users@myfaces.apache.org
Sent: Fri, July 2, 2010 8:07:34 PM
Subject: Re: Long transactions
I am not familiar with orchestra, so I can't comment there. It has
not
been an option for us up to this point.
However, if you leave a
transaction active
Mike you left out the obvious one, simply use a conversation framework.
The problem is not transactions but it is that the entity manger is
dropped along the way hence silently detaching all objects and running
you into detached error hell. (You still can either setup your jpa
provider so that
- Original Message
From: Werner Punz werner.p...@gmail.com
To: users@myfaces.apache.org
Sent: Fri, July 2, 2010 9:39:05 AM
Subject: Re: Long transactions
Mike you left out the obvious one, simply use a conversation framework.
The
problem is not transactions but it is that the entity
effort into
the transition, but for me it made things alot easier again.
Ciao,
Mario
[1] www.avaje.org
-Ursprüngliche Nachricht-
Von: Mark Struberg [mailto:strub...@yahoo.de]
Gesendet: Freitag, 02. Juli 2010 10:12
An: MyFaces Discussion
Betreff: Re: Long transactions
Mike you left out
-
Von: Mario Ivankovits [mailto:ma...@ops.co.at]
Gesendet: Freitag, 02. Juli 2010 10:27
An: 'MyFaces Discussion'
Betreff: Re: Long transactions
Hi!
I know, I might sound like a broken record already ...
But also consider using a JPA-like persistence provider like Ebean [1].
If you are going
I am not familiar with orchestra, so I can't comment there. It has
not been an option for us up to this point.
However, if you leave a transaction active after a response, it's
always going to be an issue no matter what framework you use.
For us, the problem with holder objects is the deep
Hi,
Is anyone here using long JPA transactions in their applications
(transactions that span more than one request) but not using Orchestra?. How
are you doing it?
Cheers,
Bruno
I am, sort of.
You really can't leave the transaction open beyond the request
response as it may never complete.
Some of the ways you can deal with it are:
1) work with fake holder entities that get changed back into real
entities at the final commit. Very ugly -- tried this one at first,
but
9 matches
Mail list logo
