This week's book giveaway is in the JavaScript forum.
We're giving away four copies of JavaScript Promises Essentials and have Rami Sarieddine 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 JavaScript Promises Essentials this week in the JavaScript 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.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Java WS Clients