Win a copy of Head First Android this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Soap Handler question

 
Ranch Hand
Posts: 629
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

I have written a soap handler for a web service I am calling. I have the log level set as fatal for handleFault method. How do I print the request message along with the fault message when a fault happens?

Thanks.
 
Ranch Hand
Posts: 1512
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What about just logging it and the print that as you choose.
 
Arjun Reddy
Ranch Hand
Posts: 629
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Bosun Bello wrote:What about just logging it and the print that as you choose.



Hi,

Sorry, I did not understand. Currently I have the code as below. If you look at it, when there is a fault, logToSystemOut2 method is called and the fault (either inbound or outbound) is printed. I want to print the request messsage only if there is a fault. How can I do it?

 
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The problem is that by the time the error is generated, the actual request stream has been consumed by the parser and parser internals are pretty hard to get at.

Right off-hand I know of no way to get it back on the server side. You might use something like SOAPui or TCPMON on the client side to record ALL requests and later figure out which caused the error.

Bill
 
Arjun Reddy
Ranch Hand
Posts: 629
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

William Brogden wrote:The problem is that by the time the error is generated, the actual request stream has been consumed by the parser and parser internals are pretty hard to get at.

Right off-hand I know of no way to get it back on the server side. You might use something like SOAPui or TCPMON on the client side to record ALL requests and later figure out which caused the error.

Bill




Thanks for replying.
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic