This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Web Services and the fly likes Webserice fundamentals: Endpoints. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Webserice fundamentals: Endpoints." Watch "Webserice fundamentals: Endpoints." New topic
Author

Webserice fundamentals: Endpoints.

milan doshi
Ranch Hand

Joined: Nov 03, 2000
Posts: 43
Hi,

I have developed few Webservices and also worked on the client side. But there are few things which I am not sure of :

We often say that "Messages goes through many endpoints on the way to their destinations..". What does this mean exactly?

Let us say my endpoint is :

http://dev.milan.com:9080/something/services/

When and how will the message go to ANOTHER endpoint?

when does the mustUnderstand attribute in the header come into play?

I have only read it theoritically but I do not understand its actual meaning. Can it be ellaborated.

Thanks in advance,
Milan Doshi
Peter Hu
Ranch Hand

Joined: Apr 15, 2005
Posts: 33
I think "endpoints" is not a proper term. It should use intermediates instead. These intermediates act just like network routers, forwarding the message till its final destnation.

The mustUnderstand attribute demands the message receiver have to know the meaning of the element and how to respond. Otherwise, stop processing the message further, thow an exception back to the originator.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Webserice fundamentals: Endpoints.