I didn't have jboss-net.sar in the default package. oops. It looks like I can get a WSDL, but I haven't tried client code yet.
I wish simple things like this were spelled out a little better for noobies.
I am working through the same example and after struggling a little bit I finally started to make progress when I ran into a problem compiling the client application.
The WSDL2Java will not generate the files I keep getting a
whenever I try to use the client-stubs target and they do not even mention the build.xml entries necessary for compiling the HelloClient. At the beginning of this chapter they mention that all of this is contained within ws-ex directory of the ws-ex.zip file but I can't find that file either.
Are you having any problems generating the client stubs or building the HelloClient? And do you know where to get the ws-ex.zip by any chance?
Thanks in advance,
AFAIK, ws-ex.zip only exists in the documentation. I didn't find it anywhere. I contacted someone at JBoss about this, but so for I've received nothing.
I've got everything working, but I didn't set up the AXIS client stuff in the ant build. I've already got my Axis client environment set up, so I just run:
java org.apache.axis.wsdl.WSDL2Java -v -p client.soap.axis http://localhost:8080/jboss-net/services/MyAPI?wsdl
This command generates all the appropriate stubs. Once you get this working, you can put it in an ant task.
Right now, everything is working great with 1 exception. The custom type mapper (@jboss-net.xml-schema urn="mytypes:MyBean"), will allow for the WSDL to be generated with my complexType, but it follows different rules than the JAX-RPC spec (or at least Axis 1.1) does. It shouldn't publish read-only properties (methods with only a get vs. get/set pair). This is causing me some pain. If anybody has a workaround for this, please let me know.
Please tell me where can I get those ws-ex files.