1. wsit
  2. WSIT-517

Needs SPI to make the undering JTA Transaction Manager pluggable


    • Type: Improvement Improvement
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: current
    • Fix Version/s: not determined
    • Component/s: transaction
    • Labels:
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:


      Currently the implementation of WS-AT depends on some features not standardized
      by JTA/JTS spec, like the JNDI name of transaction manager and contract
      represented by com.sun.enterprise.TransactionImport. If there is a SPI
      reprensenting all these requirement, the integration of the WSIT transaction
      with other JEE5 container will be much easier.

      Here is the eamil thread: wrote:
      > Hi Joseph,
      > Looks like WS-AT sample can only run with Glassfish. Because WS-AT
      > implementation
      > in WSIT depends on internal API from Glassfish Transaction Manager.
      WSIT WS-TX implementatino depends on JTA 1.0.1 API as much as it can.
      It also needed to depend on methods used to implement the Transaction Inflow
      contract from Java Connector API 1.5. The SPI contract represented by
      com.sun.enterprise.TransactionImport interface is all that required to
      be implemented above
      and beyond JTA 1.0.1 API.

      TransactionImport interface represents exposing methods used to
      implement Transaction Inflow
      contract in JCA 1.5.

      > it's
      > impossible to deploy the sample into Tomcat integrated a third-party
      > Transaction
      > manager like JTOM. Is there any plan to make the underlying
      > Transaction Manager
      > pluggable so WS-AT sample can run out of Glassfish?
      The initial WSIT WS-TX design center was to work with an Application
      Server having a JTA Transaction Manager.
      Any Java EE application server implementing JCA 1.5 can trivially
      implement the TransactionImport interface
      mentioned above.

      Please file an enhancement request in wsit issue tracker[1] if this a
      functionality that you would like to see considered for
      a future release. As I stated above, The WSIT WS-TX code dependencies on
      a Transaction Manager are
      mostly on JTA 1.0.1 API. Note that there is a WS-AT coordinator service
      deployed as a system level service in
      Glassfish v2 App Server that would have to be deployed into Tomcat.




        There are no comments yet on this issue.


          • Assignee:
          • Votes:
            1 Vote for this issue
            0 Start watching this issue


            • Created: