Sorry, not what I meant to say at all.
You can use CMT (Container-Managed Transactions)
The commit happens automatically at the end of your business method and nested
and XA transactions are supported via annotations.
On May 22, 2012, at 2:41 PM, Lenny Primak wrote:
> No. You can use BMP (Bean-Managed Persistence).
> The commit happens automatically at the end of your business method and
> nested and XA transactions are supported via annotations.
>
>
>
> On May 22, 2012, at 2:36 PM, bhorvat <horvat.z.bo...@gmail.com> wrote:
>
>> With JEE transaction I would have to handle everything manually? Like so
>>
>> UserTransaction transaction = (UserTransaction)new
>> InitialContext().lookup("java:comp/UserTransaction");
>> transaction.begin();
>> EntityManager em = getEntityManager();
>> Employee employee = em.find(Employee.class, id);
>> employee.setSalary(employee.getSalary() + 1000);
>> transaction.commit();
>>
>> http://en.wikibooks.org/wiki/Java_Persistence/Transactions
>>
>> --
>> View this message in context:
>> http://tapestry.1045711.n5.nabble.com/Tapestry-Transactions-tp5713299p5713334.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
