Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-16763

Remove all ContextData on client and server that is not defined using 'jboss.returned.keys'

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 27.0.0.Alpha4
    • EJB
    • None
    • Hide

      Send ContextData from a client to a server and see the server and client side ContextData Maps, as well as the network payload via Wireshark

      Show
      Send ContextData from a client to a server and see the server and client side ContextData Maps, as well as the network payload via Wireshark
    • ---
    • ---

    Description

      When a EJB client send's ContextData to the server, all sent data should be cleared on the server side before marshalling the response and on the client side before unmarshalling a server response that is not requested using the jboss.returned.keys.

      Only ContextData that is being explicitly requested by a client should be sent back and forth.

      On the EJBClientInvocationContext class there's a convenient method addReturnedContextDataKey to add keys to that property.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. EJBCLIENT-424 EJB remote invocation response payload contain ContextData not part of 'jboss.returned.keys'

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. WEJBHTTP-83 WF Http EJB Client does not delete ContextData that has been removed on the server side

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. WFLY-16796 LocalEjbReceiver response contains ContextData that has been removed on the server side

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. WFLY-16567 EJB response contains ContextData that has been removed in the server side interceptors

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. EJBCLIENT-425 EJB client API does not delete ContextData that has been removed on the server side

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Pull Request Sent

          Activity

            People

              cfang@redhat.com Cheng Fang
              rhn-support-jbaesner Joerg Baesner
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: