wsit
  1. wsit
  2. WSIT-471

warn when WS-AT webmethod invoked in unsupported scenarios

    Details

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

      Operating System: All
      Platform: All

    • Issuezilla Id:
      471

      Description

      Issue a warning if can not flow a WS-AT transaction context due to following
      implementation limitations. Note warning only issued when
      there method is invoked with a current JTA transaction context.
      User would expect txn context to be flowed as WS-AT Txn Context with the request.

      1. Invoking a WS-AT annotated web method from an Application Client Container
      (not supported by WSIT 1.0)
      2. On an asynchronous,transacted web service invocation invoked
      with a current JTA transaction context.
      (probably will never support this, transaction processing by its very nature
      implies synchronization between client controlling the transactional context
      and the operations being processed in that transactional context.)

      TxClientPipe is a good place to identify these situations at runtime.
      Either can throw an exception or just warn that invoked operation is
      not participating in current client transaction.

      Statically, it might be possible to identify invalid combinations of
      program annotations. (@WebMethod that is both transacted AND asynchronous)

        Activity

        Hide
        jfialli added a comment -

        accept

        Show
        jfialli added a comment - accept
        Hide
        jfialli added a comment -

        Partial fix checked in to check when calling transacted method
        in application client and there is a current UserTransaction.
        WARNING notifies user that WS-AT txn context not flowed with message
        since flowing txn context not supported by current container.

        Still waiting for answer on how to know when async operation.

        Show
        jfialli added a comment - Partial fix checked in to check when calling transacted method in application client and there is a current UserTransaction. WARNING notifies user that WS-AT txn context not flowed with message since flowing txn context not supported by current container. Still waiting for answer on how to know when async operation.
        Hide
        m_potociar added a comment -

        Reassigning to the component owner

        Show
        m_potociar added a comment - Reassigning to the component owner
        Hide
        Marek Potociar added a comment -

        Reclassified as task

        Show
        Marek Potociar added a comment - Reclassified as task

          People

          • Assignee:
            arjavdesai
            Reporter:
            jfialli
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: