[weld-dev] persistence and transactions outside Java EE
Jonathan Halliday
jonathan.halliday at redhat.com
Mon Nov 23 12:19:30 EST 2009
None of the pools is XA aware - they will pool standard
connections, but not XA ones that need XAResource enlistment
to the JTA tx. The TransactionalDriver in JBossTS will do
that, but it's pretty primitive compared to a real JCA.
Jonathan.
On 11/23/2009 05:16 PM, Gavin King wrote:
> Ah. Standalone JCA is a problem. But do we really need JCA, or can we
> just let Hibernate use one of the standalone connection pools that it
> ships with?
>
> On Mon, Nov 23, 2009 at 7:13 AM, Pete Muir<pmuir at redhat.com> wrote:
>> I chatted to Jonathan about this, he tells me the binary for JBossTS JTA is under 1MB with no external dependencies other than the JTA API (but we would probably need standalone JCA too).
>>
>> On 18 Nov 2009, at 23:10, Gavin King wrote:
>>
>>> I think we should try and follow the Java EE models as closely as
>>> possible for this stuff. We should simply try and make the Java EE
>>> code work outside EE 6.
>>>
>>> e.g.
>>>
>>> (1) use a resource declaration with @PersistenceContext(unitName=....)
>>> to define a managed persistence context
>>> (2) use JBoss Transactions to manage transactions in a servlet engine
>>> - so instead of having a special tx manager for JDBC, it is just JTA
>>>
>>> Or is the 10meg download for JBoss Transactions just no good?
>>>
>>> --
>>> Gavin King
>>> gavin.king at gmail.com
>>> http://in.relation.to/Bloggers/Gavin
>>> http://hibernate.org
>>> http://seamframework.org
>>> _______________________________________________
>>> weld-dev mailing list
>>> weld-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>
>>
>
>
>
--
------------------------------------------------------------
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111
Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No.
3798903 Directors: Michael Cunningham (USA), Charlie Peters
(USA), Matt Parsons (USA) and Brendan Lane (Ireland)
More information about the weld-dev
mailing list