This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes Web Services and the fly likes Java WS Clients Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Java WS Clients" Watch "Java WS Clients" New topic
Author

Java WS Clients

Janardan Kelkar
Ranch Hand

Joined: May 05, 2008
Posts: 72

I have seen there to be two different ways of writing webservice clients in java:
Method#1


Method#2


Method#1 works even when the 'port name' element in the WSDL changes (the binding remains the same though). However, the second methods does not run when the 'port name' element changes in the WSDL it tries to hit. This is the difference in the behaviour that i see. I need to understand the functioning of the Method#1, as in, what exactly is happening when i am invoking a service in that way.

Not sure if its relevant, but i have generated the client artifacts using the wsconsume utility of JBoss EAP 6.

Thanks!


When the compiler's not happy, ain't nobody happy.
 
Consider Paul's rocket mass heater.
 
subject: Java WS Clients
 
Similar Threads
SAAJ client to simple hello world method
Unable to establish connection to WSDL. Failed to access the WSDL.
JAX WS multiple requests management
Jax-ws 2.2.1: creating clients for endpoints that are not in the WSDL
How to change WSDL url dynamically