You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by "Lori VanGulick (JIRA)" <ji...@apache.org> on 2009/10/14 01:23:31 UTC

[jira] Created: (AXIS2-4528) Performance issue with SOAPHANDLER'S HANDLEMESSAGE

Performance issue with SOAPHANDLER'S HANDLEMESSAGE
--------------------------------------------------

                 Key: AXIS2-4528
                 URL: https://issues.apache.org/jira/browse/AXIS2-4528
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: jaxws
            Reporter: Lori VanGulick
             Fix For: 1.6


Implementations of HandlerPostInvoker have no way to determine if the SOAP message has even been accessed by the handlers.  Without this information they may needlessly expand the message causing performance degradation. 

Add a property "jaxws.messageAccessed" to the SOAPMessageContext when a SOAPMessageContext.getMessage() is performed.  HandlerPostInvoker implementations can then check for the property.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (AXIS2-4528) Performance issue with SOAPHANDLER'S HANDLEMESSAGE

Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/AXIS2-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rich Scheuerle resolved AXIS2-4528.
-----------------------------------

    Resolution: Fixed

> Performance issue with SOAPHANDLER'S HANDLEMESSAGE
> --------------------------------------------------
>
>                 Key: AXIS2-4528
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4528
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Lori VanGulick
>             Fix For: 1.6
>
>         Attachments: AXIS2-4528patch.diff
>
>
> Implementations of HandlerPostInvoker have no way to determine if the SOAP message has even been accessed by the handlers.  Without this information they may needlessly expand the message causing performance degradation. 
> Add a property "jaxws.messageAccessed" to the SOAPMessageContext when a SOAPMessageContext.getMessage() is performed.  HandlerPostInvoker implementations can then check for the property.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AXIS2-4528) Performance issue with SOAPHANDLER'S HANDLEMESSAGE

Posted by "Lori VanGulick (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/AXIS2-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lori VanGulick updated AXIS2-4528:
----------------------------------

    Attachment: AXIS2-4528patch.diff

attached patch

> Performance issue with SOAPHANDLER'S HANDLEMESSAGE
> --------------------------------------------------
>
>                 Key: AXIS2-4528
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4528
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Lori VanGulick
>             Fix For: 1.6
>
>         Attachments: AXIS2-4528patch.diff
>
>
> Implementations of HandlerPostInvoker have no way to determine if the SOAP message has even been accessed by the handlers.  Without this information they may needlessly expand the message causing performance degradation. 
> Add a property "jaxws.messageAccessed" to the SOAPMessageContext when a SOAPMessageContext.getMessage() is performed.  HandlerPostInvoker implementations can then check for the property.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.