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 "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2007/11/16 13:33:44 UTC
[jira] Created: (AXIS2-3347) JAXWS: Add support for
SOAPMessageContext.getHeaders(QName qname, JAXBContext jaxbcontext, boolean
allRoles)
JAXWS: Add support for SOAPMessageContext.getHeaders(QName qname, JAXBContext jaxbcontext, boolean allRoles)
-------------------------------------------------------------------------------------------------------------
Key: AXIS2-3347
URL: https://issues.apache.org/jira/browse/AXIS2-3347
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Reporter: Rich Scheuerle
Assignee: Rich Scheuerle
Problem:
JAX-WS provides a javax.xml.ws.handler.soap.SOAPMessageContext to JAX-WS web service handlers.
The SOAPMessageContext.getHeaders(QName qname, JAXBContext jaxbcontext, boolean allRoles) is supposed to return all of the
specificed headers rendered as JAXB objects. In addition, if the "allRoles" argument is false, only those headers which match the current node's role
are returned.
The method is currently broken. (1) It only returns one header even if there are multiple headers matching the criteria. (2) It does not do any role matching.
Solution:
I am testing a change to fix this issue. The JAX-WS "Message model" is upgraded to do more advanced header processing. I am also using the
Axiom RolePlayer interface to do the role matching. This change only affects the JAX-WS functionality.
In addition, I am upgrading the addNumbersTest to verify these changes.
Future:
This change and the recent changes for OMDataSourcedExt are exposing the fragility of the JAX-WS "Message Model" (especially XMLSpineImpl).
I am starting to work on a design to correct this fragility. Once I have some solid ideas I will open a JIRA.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-3347) JAXWS: Add support for
SOAPMessageContext.getHeaders(QName qname, JAXBContext jaxbcontext, boolean
allRoles)
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-3347.
-----------------------------------
Resolution: Fixed
Committed Revision 595647
> JAXWS: Add support for SOAPMessageContext.getHeaders(QName qname, JAXBContext jaxbcontext, boolean allRoles)
> -------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3347
> URL: https://issues.apache.org/jira/browse/AXIS2-3347
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
>
> Problem:
> JAX-WS provides a javax.xml.ws.handler.soap.SOAPMessageContext to JAX-WS web service handlers.
> The SOAPMessageContext.getHeaders(QName qname, JAXBContext jaxbcontext, boolean allRoles) is supposed to return all of the
> specificed headers rendered as JAXB objects. In addition, if the "allRoles" argument is false, only those headers which match the current node's role
> are returned.
> The method is currently broken. (1) It only returns one header even if there are multiple headers matching the criteria. (2) It does not do any role matching.
> Solution:
> I am testing a change to fix this issue. The JAX-WS "Message model" is upgraded to do more advanced header processing. I am also using the
> Axiom RolePlayer interface to do the role matching. This change only affects the JAX-WS functionality.
> In addition, I am upgrading the addNumbersTest to verify these changes.
> Future:
> This change and the recent changes for OMDataSourcedExt are exposing the fragility of the JAX-WS "Message Model" (especially XMLSpineImpl).
> I am starting to work on a design to correct this fragility. Once I have some solid ideas I will open a JIRA.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org