File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Web Services and the fly likes client response and parsing behaviour Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of The Mikado Method this week in the Agile and other Processes forum!
JavaRanch » Java Forums » Java » Web Services
Reply Bookmark "client response and parsing behaviour" Watch "client response and parsing behaviour" New topic
Author

client response and parsing behaviour

Pratap koritala
Ranch Hand

Joined: Sep 27, 2006
Posts: 251
I am having couple of questions

1) In web service client( Preferably Axis), After it start receiving the response for return type.
What is the default behavior,
Does it buffer till the response stream ends and treats it as string and then parses it to java types, or
It will treat it as stream and uses a SAX parses and does the parse.

2) In the above case, can we able to override the behavior in case of Axis?

3) In Axis web service client , After the response but before parsing and generating the java return types.
I want to have the control back to me, so that I can enclose the response as stream and pass it to parser. Is it possible ?

Any help would be appreciated.
 
I agree. Here's the link: http://zeroturnaround.com/jrebel - it saves me about five hours per week
 
subject: client response and parsing behaviour
 
Similar Threads
XML parsers to garbage collect the part of the xml which is parsed
Need some advice on returning record sets from a web service to a C# client.
Axis "code portabiliy"
No output on .Net Client side
axis and soap