Re: [Springframework-developer] JTA transaction suspension on WebSphere

[Colin S. <col...@ex...>]

'Eu' on his blog 3-4 days ago commented based on my own blog entry, and 
a forum message:
  http://jroller.com/page/eu/20040826#using_spring_jta_interfaces_from
that section / C.2.4 /of the EJB spec says that the container, for EJBs, 
must implement the UserTransaction interface (and JTA 1.0.1) extension, 
but doesn't have to implement the other interfaces defined in the JTA 
specification. Fine, I've actually seen that before, coincidentally, 
when I was tracking something down a while ago, but I think a container 
is fundamentally broken if it _does_ expose the JTA TransactionManager 
interface, and it doesn't behave as per the spec. The spec for an API is 
the spec for the API. If you expose the interface at all, then you need 
to expose it correctly... That's essentially how I read that clause, and 
how I see things. In any case, I hope the situation is going to improve, 
certainly WLS 8 works where WLS 7 doesn't, with out WL specific adapter...

Colin

jürgen höller [werk3AT] wrote:

>After our recent issues with JTA resume (with the outer transaction marked as rollback-only) on WebLogic, which we were just able to solve for WebLogic 8.1 but not for 7.0:
> 
>http://opensource.atlassian.com/projects/spring/browse/SPR-251 <http://opensource.atlassian.com/projects/spring/browse/SPR-251> 
> 
>we now have similar problems on WebSphere 4.0, seemingly with suspension of an ordinary transaction:
> 
>http://opensource.atlassian.com/projects/spring/browse/SPR-295 <http://opensource.atlassian.com/projects/spring/browse/SPR-295> 
> 
>Any WebSphere user that can shed some light on this? I'm afraid that we'll have to invoke some proprietary WebSphere API for JTA suspend/resume, just like we had to do for WebLogic...
> 
>Oh how do I wish that J2EE considered javax.transaction.TransactionManager as proper public API...
> 
>Juergen
> 
>  
>