WS-MEX capability implementation class should default to WsrfMetadataExchange when RMD file specified.
------------------------------------------------------------------------------------------------------
Key: MUSE-302
URL:
https://issues.apache.org/jira/browse/MUSE-302 Project: Muse
Issue Type: Bug
Components: Tooling - Code Generation
Affects Versions: 2.2.0
Environment: latest SVN trunk to data
Reporter: Jonas Buys
Assignee: Dan Jemiolo
When running WSDL2JAVA on a WSDL and RMD file that contain all the necessary XML for WS-MetadataExchange, in the generated muse.xml file the default MUSE class org.apache.muse.ws.metadata.impl.SimpleMetadataExchange is specified as implementation class for WS-MEX. This is sufficient in the case there is a WSDL without an RMD file.
The side effect is that, when invoking getRMD() on your WsrfMetadataExchangeClient proxy object, the SOAP message will return an EMPTY metadata response. The issue can be resolved by manually setting the MUSE class org.apache.muse.ws.resource.metadata.ext.WsrfMetadataExchange as implemantation class for the MEX capability.
An easy way to fix this issue is to modify org.apache.muse.tools.generator.analyzer.SimpleAnalyzer, by inserting the WsrfMetadataExchange class at line 106 in the _internalImplMap instead of the default SimpleMetadataExchange. Or it can of course also be done manually.
A better solution would be for the generator tool to check whether an RMD file is specified, and if so, use the WsrfMetadataExchange instead of the SimpleMetadataExchange class.
--
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:
muse-dev-unsubscribe@...
For additional commands, e-mail:
muse-dev-help@...
