Java Webservice Client (Best way)

Question

I have a third party WSDL, I need to write code in JAVA for a web service client to invoke the operations in the third party WSDL. Right now, I have generated the client stub using the WSDL2JAVA tool from Axis and used the XMLbeans for data binding.

1. What is the best approach to do this JAVA?
2. I read about SAAJ, looks like that will be more granular level of approach?
3. Is there any other way than using the WSDL2Java tool, to generate the code. Maybe wsimport in another option. What are the pros and cons?
4. Can someone send the links for some good tutorials on these topics?
5. What are the options we need to use while generating the code using the WSDL2Java?

I used some of the basic things initially. Now I have these options

C:\axis2-1.5.1\bin>wsdl2java -uri  mywsdlurl  -o client -p somepackage -d xmlbeans -s -t -ssi

Thanks in advance!

Answer 1

I have had good success using Spring WS for the client end of a web service app - see http://static.springsource.org/spring-ws/sites/1.5/reference/html/client.html

My project uses a combination of:

• XMLBeans (generated from a simple Maven job using the xmlbeans-maven-plugin)

• Spring WS - using marshalSendAndReceive() reduces the code down to one line for sending and receiving

• some Dozer - mapping the complex XMLBeans to simple beans for the client GUI

Answer 2

Some ideas in the following answer:

http://stackoverflow.com/questions/2559074/steps-in-creating-a-web-service-using-axis2-the-client-code/2564323#2564323

Gives an example of a Groovy client invoking the ADB classes generated from the WSDL.

There are lots of web service frameworks out there...

Answer 3

What is the best approach to do this JAVA?

I would personally NOT use Axis 2, even for client side development only. Here is why I stay away from it:

1. I don't like its architecture and hate its counter productive deployment model.
2. I find it to be low quality project.
3. I don't like its performances (see this benchmark against JAX-WS RI).
4. It's always a nightmare to setup dependencies (I use Maven and I always have to fight with the gazillion of dependencies) (see #2)
5. Axis sucked big time and Axis2 isn't better. No, this is not a personal opinion, there is a consensus.
6. I suffered once, never again.

The only reason Axis is still around is IMO because it's used in Eclipse since ages. Thanks god, this has been fixed in Eclipse Helios and I hope Axis2 will finally die. There are just much better stacks.

I read about SAAJ, looks like that will be more granular level of approach?

To do what?

Is there any other way than using the WSDL2Java tool, to generate the code. Maybe wsimport in another option. What are the pros and cons?

Yes! Prefer a JAX-WS stack like CXF or JAX-WS RI (you might also read about Metro, Metro = JAX-WS RI + WSIT), they are just more elegant, simpler, easier to use. In your case, I would just use JAX-WS RI which is included in Java 6 and thus wsimport.

Can someone send the links for some good tutorials on these topics?

That's another pro, there are plenty of (good quality) tutorials for JAX-WS, see for example:

• Developing JAX-WS Web Service Clients (start here)
• Introducing JAX-WS 2.0 With the Java SE 6 Platform, Part 1
• Creating a Simple Web Service and Client with JAX-WS
• Creating a SOAP client with either Apache CXF or GlassFish Metro (Glen Mazza's blog is a great resources)

What are the options we need to use while generating the code using the WSDL2Java?

No options, use wsimport :)

See also

• Elad’s Adventures in Java WebServiceLand
• Axis2: Why bother? on the BileBlog (be prepared for the bile) - you'll have to stop the redirect.

Related questions

• What is the best java webservice framework?
• Spring-ws or Axis2 or Something else for “Contract-First” approach to WS