Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-1505

WS-BA transaction context not propagated if JTA transaction present.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 5.0.0.M3
    • None
    • TxBridge, XTS
    • None

      With default-context-propagation enabled:

      What happens if the Client is running in a JTA transaction, then begins a WS-BA transaction before calling a WS-BA enabled service? I suspect, as it stands, we would start a WS-AT transaction as well. This will cause the JaxBaseHeaderContextProcessor to default to WS-AT as it appears first in the if-then-elseif block:

                  final CoordinationContextType coordinationContext ;
                  if (atContext != null)
                  {
                      coordinationContext = atContext.getCoordinationContext() ;
                  }
                  else if (baContext != null)
                  {
                      coordinationContext = baContext.getCoordinationContext() ;
                  }
      

      I'm not yet sure how we handle this case. We certainly need a test for it though.

              gtrikler@redhat.com Gytis Trikleris (Inactive)
              paul.robinson@redhat.com Paul Robinson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 2 hours
                  2h
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour, 1 minute Time Not Required
                  1h 1m