geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1574) Spring integration -- wrap our components in spring interfaces
Date Thu, 02 Feb 2006 10:57:19 GMT
    [ ] 

Guillaume Nodet commented on GERONIMO-1574:

Why not simply expose the TransactionManager in JNDI ?
It may already be the case, and there would be no need of such a factory bean.

Btw, i have made lots of tests on this area for the jencks project and the main problem is
that spring sometime assumes that the TransactionManager and UserTransaction are somewhat

In facts, as the spring transaction manager may be used in EJB, web apps, etc to access managed
resources, I think the factory bean should return the UserTransaction instead of the TransactionManager.
But some functions won't be available such as suspend / resume, because the UserTransaction
and TransactionManager implementations are not linked.

In the jencks project, i have written some classes to make the bridge between the UserTransaction
and TransactionManager.

Here is a working example on how to use spring with geronimo transaction layer:

> Spring integration -- wrap our components in spring interfaces
> --------------------------------------------------------------
>          Key: GERONIMO-1574
>          URL:
>      Project: Geronimo
>         Type: New Feature
>     Versions: 1.1
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.1

> For a reasonable spring integration, we need to expose some of our components wrapped
in spring interfaces.  The most obvious is the transaction manager.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message