|
Patrick Linskey made changes - 16/Feb/07 04:28 PM
Patrick Linskey made changes - 16/Feb/07 04:29 PM
Patrick Linskey made changes - 16/Feb/07 04:41 PM
[
Permlink
| « Hide
]
Kevin Sutter added a comment - 20/Feb/07 12:50 AM
This is a temporary situation. WebSphere has always had the convention of "managed" datasources. All datasources would automatically be enlisted in the enclosing transaction. With the introduction of the non-jta-data-source in JPA, WebSphere will need to relax this requirement. Supposedly, the support for the non-jta-data-source will be available in the next Beta of the EJB3 Feature Pack.
I believe that the only remaining issue here is captured in
Patrick Linskey made changes - 01/Mar/07 01:14 AM
Patrick Linskey made changes - 01/Mar/07 02:11 AM
Confirming Kevin's comments above, support for non-jta-datasources is working and will be included in the next release of the WebSphere EJB3 feature pack.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||