Yes, this is an oversight
Have a look at the jsr181ejb and jsr181pojo samples in the samples download.
<configuration ...> <wsdl-java file="resources/samples/jsr181ejb/META-INF/wsdl/TestService.wsdl"> <mapping file="jaxrpc-mapping.xml" /> </wsdl-java> </configuration>
CAn I generate stub with <wsdl-java/> configuration?
If I can, what is the configuraiton?
Based on the example found in the sample code, I have managed to generate the interfaces from the WSDL file, but not the implementing stub classes.
WS Tool Configuration
<configuration xmlns="http://www.jboss.org/jbossws-tools"> <wsdl-java file="resources/wsdl/DataRetrieve.wsdl"> <mapping file="jaxrpc-mapping.xml" /> </wsdl-java> </configuration>
My Web Service is named DataRetrieve.
Axis generates these files:
When running the JBossWS wsdl-java code generator, only these files are generated.
How should I configure the wstool to be able to generate the Stubs (e.g. DataRetrieveLocator and DataRetrieveServiceBindingStub) or is this not possible?
Likewise I generate two interfaces from a single pojo 181 jsr but no stubs. I noticed the client dir has no
jbossws-client.jar just the 14 version. Posted a topic about that because wstool.bat refers to it. Don't know if this is the culprit or not.
I installed via the installer jar downloading the zip now to see if it contains the correct jar
wstools does not generate staticly compilable stubs. We use the JSR109 client deployment model where you look au a preconfigured stub from JNDI.
Look at the sample clients