You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2006/07/19 03:37:28 UTC
[jira] Created: (SM-488) SoapHelper Improvement: Resolve WSDL
operation name based on message content
SoapHelper Improvement: Resolve WSDL operation name based on message content
-----------------------------------------------------------------------------
Key: SM-488
URL: https://issues.apache.org/activemq/browse/SM-488
Project: ServiceMix
Issue Type: Improvement
Components: servicemix-soap
Affects Versions: 3.0-M1, 3.0-M2
Reporter: Alex Boisvert
Fix For: 3.0
Attachments: SoapHelper.diff
The attached patch allows SoapHelper to resolve the WSDL operation name based on the message content. The approach follows the WS-I BasicProfile recommendation to identify the "operation signature [1]:
"The profile defines the "operation signature" to be the fully qualified name of the child element of SOAP body of the SOAP input message described by an operation in a WSDL binding."
[1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Operation_Signatures
If the operation cannot be resolved from the WSDL definition, the operation name default to the fully-qualified name of the SOAP body element (as before the patch).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SM-488) SoapHelper Improvement: Resolve WSDL
operation name based on message content
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-488?page=all ]
Guillaume Nodet resolved SM-488.
--------------------------------
Fix Version/s: 3.0-M3
(was: 3.0)
Resolution: Fixed
Assignee: Guillaume Nodet
Thanks for this patch Alex !
I have slightly modified it to
* retrieve the namespace for the operation QName
* the defaultOperation is only used when the operation on the wsdl
can not be found
Author: gnodet
Date: Mon Jul 24 02:48:16 2006
New Revision: 424984
URL: http://svn.apache.org/viewvc?rev=424984&view=rev
Log:
SM-488: SoapHelper Improvement: Resolve WSDL operation name based on message content
Patch provided by Alex Boisvert
Modified:
incubator/servicemix/trunk/servicemix-soap/src/main/java/org/apache/servicemix/soap/SoapHelper.java
> SoapHelper Improvement: Resolve WSDL operation name based on message content
> -----------------------------------------------------------------------------
>
> Key: SM-488
> URL: https://issues.apache.org/activemq/browse/SM-488
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-soap
> Affects Versions: 3.0-M1, 3.0-M2
> Reporter: Alex Boisvert
> Assigned To: Guillaume Nodet
> Fix For: 3.0-M3
>
> Attachments: SoapHelper.diff
>
>
> The attached patch allows SoapHelper to resolve the WSDL operation name based on the message content. The approach follows the WS-I BasicProfile recommendation to identify the "operation signature [1]:
> "The profile defines the "operation signature" to be the fully qualified name of the child element of SOAP body of the SOAP input message described by an operation in a WSDL binding."
> [1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Operation_Signatures
> If the operation cannot be resolved from the WSDL definition, the operation name default to the fully-qualified name of the SOAP body element (as before the patch).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira