BIRT 3.7
Written by: Michael Williams
Featured Refcardz: Top Refcardz:
  1. HTML5 Canvas
  2. Ruby
  3. iPhone/iPad
  4. Spring Web Flow
  5. REST
  1. jQuery Selectors
  2. Spring Config.
  3. Java
  4. Ajax
  5. Java Concurrency
150+ Refcardz Available · Get them all

Link Details

Previous | Next

Surprise Me!
Link 9611 thumbnail
User 111696 avatar

By bloid
via javaworld.com
Published: Dec 21 2006 / 14:16

Are your Web services exceptions naked or covered?
Using SOAP for system-to-system messaging and WSDL for interface description makes exception handling complex. In this article, we will explore exception handling and testing techniques, and their impact on Web services-based SOA.
Vote up
Vote down
  • 6
  • 0
  • 1284
  • 0
SaveShareSend Tags: ,

Comments

Add your comment
User 223844 avatar

abarnea_2000 replied ago:

0 votes Vote down Vote up Reply

The ULTIMATE exception handling: see www.cajoon.com . . . JVM upon exception 'wakes it up' and if passes criteria of type, class, method, extracts a snapshot of heap and stack values that were pertinent right after the exception and just before it is returned to the application (and to any exception handling therein). Completely transparent to the code . . . no instrumentation required

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (6)



Voters Against This Link (0)