Win a copy of Getting started with Java on the Raspberry Pi this week in the Raspberry Pi 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 ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Tim Cooke
  • Jeanne Boyarsky
  • Rob Spoor
  • Devaka Cooray
  • Liutauras Vilda
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Tim Moores
  • Mikalai Zaikin
  • Piet Souris

exception handling

Ranch Hand
Posts: 94
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I found a paragraph in blueprint.

A SOAP fault defines system-level exceptions, such as RemoteException,
which are nonrecoverable errors. The WSDL fault denotes service-specific
exceptions, such as CityNotFoundException, and these are recoverable application
error conditions. Since the WSDL fault denotes a recoverable error condition,
the service can pass it as part of the SOAP response message. Thus, the
standards provide a way to exchange fault messages and map these messages to
operations on the endpoint.

I thought, in the Document/Literal, sender and recevier are mainly exchange xml documents. Then in which way an application exception is supposed to be transmiited? Above paragraph indicates that it is not appropariate to send back an application exception to client as a soap fault, in stead it should construct a normal soap message that describes the appliaton specific excetpion. Is this right?
Maybe he went home and went to bed. And took this tiny ad with him:
Low Tech Laboratory
    Bookmark Topic Watch Topic
  • New Topic