Charlouze,
I worked on a world class backbone (meaning multi flavored request broker
rmi/ejb/corba hostname:port ) for integrating supply chains bidders amidst a
slew of Javascript apps...
In our applications... we performed transactions... responsibly.
To say I am uncomfortable with tynamo's
Original Message-
> > From: Charlouze [mailto:m...@charlouze.com]
> > Sent: Thursday, September 25, 2014 9:56 AM
> > To: Tapestry users
> > Subject: Re: Tapestry-jpa commitAfter advisor problem
> >
> > @Chris: I'm using 5.4 and I don't really want to use
I was just trying to give you an easy option. It has worked well for me.
YMMV.
Tony
> -Original Message-
> From: Charlouze [mailto:m...@charlouze.com]
> Sent: Thursday, September 25, 2014 9:56 AM
> To: Tapestry users
> Subject: Re: Tapestry-jpa commitAfter advisor pro
>
> Tony
>
> > -Original Message-
> > From: Chris Mylonas [mailto:ch...@opencsta.org]
> > Sent: Thursday, September 25, 2014 9:43 AM
> > To: Tapestry users
> > Subject: Re: Tapestry-jpa commitAfter advisor problem
> >
> > I only know EJB/JPA bu
.
Tony
> -Original Message-
> From: Chris Mylonas [mailto:ch...@opencsta.org]
> Sent: Thursday, September 25, 2014 9:43 AM
> To: Tapestry users
> Subject: Re: Tapestry-jpa commitAfter advisor problem
>
> I only know EJB/JPA but I'm sure some people will say Sp
I only know EJB/JPA but I'm sure some people will say Spring. I prototype
in tapestry-hibernate because the docs were easier at the time to use than
tapestry-jpa, and when I hit nesting problems that's when I switch to using
the @EJB annotation.
I need to switch to tapestry-jpa to make my transi
Thx for your quick answer.
My method2 can be used in a "stand-alone way" so removing @CommitAfter is
not an option. I could get around the problem with another method called by
both method 1 and 2 but it'll bring mess to my code having one method that
commits the transaction and another one that d
The @CommitAfter annotation should be used as a convenience for simple
scenarios, it doesn't support nesting. This has been discussed many times
in the past on this mailing list.
For the scenario that you described, I would remove the @CommitAfter
annotation from method2, this way all of the code w
