Axis2 reads WS-A reference parameter headers into wsa:Metadata element of EPR
-----------------------------------------------------------------------------
Key: MUSE-30
URL: http://issues.apache.org/jira/browse/MUSE-30
Project: Muse
Type: Bug
Environment: Axis2
Reporter: Dan Jemiolo
For some reason, the SOAP requests sent from our current Muse client code cause
Axis2 to form an improper EPR on the server side.
When Axis2 is processing the SOAP headers, it seems to ignore the
wsa:IsReferenceParameter attribute on the SOAP headers for WS-A reference
parameters. This causes it to lump those headres into the EPR's wsa:Metadata
section. Since only the reference params are used for resource resolution, this
causes WS-A DestinationUnreachable faults - the data is in the EPR, but it's
under Metadata, not ReferenceParameters.
Looking at the SOAP request on the server side shows that a) the
wsa:IsReferenceParameter attribute is present, and is set to "true", and b) wsa
is mapped to the proper WS-A namespace. Right now there is a commented-out hack
in AxisEnvironment that gets around this, but the problem should be fixed so
that we don't have to "fix" the EPR for every request.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
