Secateurs,
I think we'll need one more stylesheet - for soap faults and
socketprojectexception reports. The client ought not to see the naked
exception, but we'll have to produce a nice screen to say that something
has gone wrong, and that it's been logged and that a nice person is
looking into it. There are a number of possible faults - network down,
service producer fail, security exception (not handling the session
properly), or invalid soap or message response. Perhaps some extensions
to SocketProjectException are required?
Atif will add another two elements to the response-type enumeration -
soap fault and socketprojectexception - and I'll knock up a simple
schema for the xml on which Rob's stylesheet can operate.
In the service-oriented world a delegate class is often used here to
buffer the client from the raw exception. This would normally sit on
the client side. In this case we might have a servlet filter as the
delegate. It intercepts any fault/error messages and renders an
appropriate response.
Regards,
Brian
|
