On Wed, Dec 3, 2008 at 5:07 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> Well, the jaxws spec does specifically say: (section 3.7)
>
> The getCause, getLocalizedMessage and getStackTrace getters from
> java.lang.Throwable and the getClass getter from java.lang.Object are
> excluded from the list of getters to be mapped.
Aha! That's the spec reference I was unable to find! Thanks! :) It
does seem to extend a bit beyond that, though -- I tried defining a
separate property get/setNestedException of type Exception (in
addition to the Cause of type Throwable), and that seemed to be
omitted too. Oh, well.
On Wed, Dec 3, 2008 at 5:18 PM, Rao, Sameer V <[EMAIL PROTECTED]> wrote:
> From a technical perspective it would be completely valid expectation to
> be able to return the details of the nested exception.
> However, from a service orientation point of view, wouldn't it be
> preferable to not provide system-specific information/stack trace of you
> java packaging etc?
As it happens, all the usage of this particular service is within one
company. And when something goes wrong, the service developers want
the consumers elsewhere within the company to be able to give them a
stack trace or other information directly, rather than just "please go
look in your logs around 3 PM" or whatever. Plus it seems to help
with debugging during development. So in this case, those concerns
outweigh the pureness of service orientation. I guess you might argue
they should attach an e-mail appender to their log system... Not sure
how that would be received. :)
Thanks,
Aaron
