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 "Mike Rheinheimer (JIRA)" <ji...@apache.org> on 2009/05/12 15:55:45 UTC
[jira] Updated: (AXIS2-4345) provide more performant way to
manipulate SOAP headers in JAX-WS handlers
[ https://issues.apache.org/jira/browse/AXIS2-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Rheinheimer updated AXIS2-4345:
------------------------------------
Attachment: patch.diff
> provide more performant way to manipulate SOAP headers in JAX-WS handlers
> -------------------------------------------------------------------------
>
> Key: AXIS2-4345
> URL: https://issues.apache.org/jira/browse/AXIS2-4345
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Mike Rheinheimer
> Assignee: Mike Rheinheimer
> Attachments: patch.diff
>
>
> I have an improvement I'd like to commit.
> Background: JAX-WS handlers can retrieve and manipulate SOAP headers if they wish. However, this is a relatively expensive operation, considering the transformation of the underlying message OM data from Axiom to SAAJ (JAX-WS spec requires SAAJ, but for efficiency reasons, JAX-WS implentation uses Axiom under the covers).
> Proposal: Allow JAX-WS handler implementations to retrieve and manipulate SOAP headers by allowing them to retrieve headers off the MessageContext parameter passed into them.
> The patch is trivial to enable this support. Writing tests was the big effort in putting this together. See patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.