wolfie78uk
Programmer
Hi,
We have recently migrated from JBuilder to Eclipse/Ant for Java Web Service creation and deployment.
I am using the "wsdeploy" ant task (contained the in the JAXRPC 1.1 distribution) and a JAXRPC-RI.xml file for configuration.
The problem I am having is that, when built using JBuilder, all StringHolder types in the Java Interface were mapped to xsd:string type during the WSDL generation. However, using the wsdeploy Ant task, they are mapped to "m0:StringHolder".
What I require is a way of telling wsdeploy to map all StringHolder types to xsd:string in the wsdl.
The route to go appears to be to use a config.xml file. However, I can't seem to make the wsdeploy task find that file.
I have seen examples on the web of using a "config" attribute in the wsdeploy task but this attribute is unsupported in the version that I am using.
Any help would be greatly appreciated.
Thanks,
Si
We have recently migrated from JBuilder to Eclipse/Ant for Java Web Service creation and deployment.
I am using the "wsdeploy" ant task (contained the in the JAXRPC 1.1 distribution) and a JAXRPC-RI.xml file for configuration.
The problem I am having is that, when built using JBuilder, all StringHolder types in the Java Interface were mapped to xsd:string type during the WSDL generation. However, using the wsdeploy Ant task, they are mapped to "m0:StringHolder".
What I require is a way of telling wsdeploy to map all StringHolder types to xsd:string in the wsdl.
The route to go appears to be to use a config.xml file. However, I can't seem to make the wsdeploy task find that file.
I have seen examples on the web of using a "config" attribute in the wsdeploy task but this attribute is unsupported in the version that I am using.
Any help would be greatly appreciated.
Thanks,
Si