Hi All,
I am using the Java-first approach to Axis2: I have some
original Java interface that I chose as a base for my web service. Then
I use the Java2WSDL to have a WSDL generated. Methods of my original
interface throw some kinds of business exceptions. I am expecting to
obtain an adequate reflection of my business exceptions in the generated
WSDL just like it happens with my complex types. However I always get
only <methodName>Fault elements generated in WSDL instead which in any
case do not appear in actual SOAP fault messages. As far as I
understand, after I have had the server skeleton generated according to
the previously generated WSDL I can only invoke my original interface's
methods inside the skeleton implementation, catch my business exceptions
and re-throw a generated <methodName>FaultException keeping nothing but
the message. Still that seems so awkward! I want my exceptions
differentiated.
In a like manner, when I deploy an implementation of my interface
as a POJO web service, throwing business or unchecked exceptions from my
methods always results in a SOAP fault message carrying no information
of the exception type (but still carrying the exception message). The
auto-generated WSDL appears to hold no info of my specific exceptions
either.
So maybe someone has a ready solution as to handling situations
with specific exceptions in web services? Any help would be much
appreciated.
Thank you!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
