[ http://issues.apache.org/jira/browse/MUSE-28?page=all ] Dan Jemiolo closed MUSE-28: ---------------------------
> Rely solely on WS-A Action URI for mapping of requests to capability methods > ---------------------------------------------------------------------------- > > Key: MUSE-28 > URL: http://issues.apache.org/jira/browse/MUSE-28 > Project: Muse > Type: Bug > Environment: Axis2 and OSGi > Reporter: Dan Jemiolo > Assignee: Dan Jemiolo > > Presently, Muse uses the SOAP body to determine what Java method should be > called for a web service operation, because the OASIS and W3C specs are not > consistent in how they format the WS-A Action URIs. The SOAP body requests > are the only things that provide an easy-to-translate name (just lowercase > the first character of the operation name). This is not "proper" WS-A, > though, and some web services specs (see Microsoft/W3C submissions) rely > solely on WS-A Action and even have operations with empty SOAP bodies. > The WS-A 1.0 spec shows (in its examples) a convention for specifying the > WS-A action of an operation's messages in the WSDL. It is not defined > normatively in the spec, but it is in the document, and we should use that as > a means of appeasing both web services camps ("empty bodies are bad" vs > "empty bodies are okay"). This will require extra processing of the > resources' WSDLs at initialization time and a change in the data structure > that maps names (now URIs) to methods. > The test case for this bug should be support of WS-Transfer's Get operation, > which has a WS-A Action URI and an empty SOAP body. -- 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]
