Thank you so much for all the useful advice and explanation. They are most helpful. I really appreciate it.
"...IF you want the response to be treated and displayed as a string, you are already there.
IF you want the response to be parsed (XML, CSV, some other format) THEN will have to write some response handling code, which I suppose will be called a web client. There is no useful framework for REST clients as far as I know but it should be simple....
I am indeed already there as the Server App is displaying the HTTP Response returned by it to the sender URL on the screen as formatted text. I am going to create a Response View (Show) so that the Server App can return this View instead of a String for the browser user to see it more easily.
Nevertheless, I have 2 scenarios:
1.) For a Web Client (vs Wireless Client), I can return this Response View just like any other Views. No Problem
2.) For a Wireless Client, I am calling XStream to serialize the HTTP Response to XML before sending it out to the URL of the wireless endpoint.
I am doing both in my Web Server App. It sounds like that if the Browse User is not expected to do anything but simply to receive the HTTP Response either via a View constructed and sent back by the Server App (in which case, user simply sees a returned formatted web page) or for a wireless device, to receive the HTTP Response in XML format as is, then I don't need a Web Client.
The RESTFUL Web Client web site that talks about using the "RestTemplate" (http://blog.springsource.com/2009/03/27/rest-in-spring-3-resttemplate/
) is the scenario that I don't think mine resembles but just want to make sure.
From your clear and precise explanation, I am convinced that I don't need a separate Web client.
My very sincere THANKS!