Ticket #154 (closed defect: fixed)

Opened 2 years ago

Last modified 1 year ago

Flatten exceptions returned through axis server

Reported by: ronald Assigned to: ronald
Priority: critical Milestone:
Component: topaz Version: 0.5-SNAPSHOT
Keywords: SOAP exception Cc:
Blocking: Blocked By:

Description

Axis does not follow the chained exceptions when serializing them for a response. This means the client sees only the message string from the top-level exception. All our *SoapBindingImpl?'s should therefore "flatten" the exceptions, i.e. merge the messages from the complete chain of exceptions into a single message.

Dependency Graph

Change History

09/11/06 19:20:55 changed by ebrown

  • priority changed from unassigned to critical.
  • milestone changed from TBD to september24.

09/11/06 21:59:55 changed by amit

  • owner changed from somebody to ronald.

Assigned to Ronald.

09/11/06 22:49:50 changed by ronald

  • status changed from new to assigned.

09/20/06 12:46:09 changed by ronald

  • status changed from assigned to closed.
  • resolution set to fixed.

(In [646]) Closes #154: created a generic exception handler for the soap-binding-impl's which flattens exception chains so that the exception message returned to the client contains the messages from all the chained exceptions.

The handler also handles logging of the exceptions.

Additionally, all NoSuchXYZIdExceptions and DuplicateXYZIdExceptions have been given a constructor which takes a message, and the id-only constructor will generate a default message containing the id (so that toString() and printStackTrace() show the id).

There is a caveat introduced by this change regarding the exceptions which is documented in the ExceptionUtils?.flattenException method.

10/29/07 21:13:03 changed by

  • milestone deleted.

Milestone september24 deleted