So we have a method that throws a checked Exception, and that one has
a nested Exception. I haven't been able to find a way to configure
things so that the nested Exception is passed to the client (the
generated schema for the main Exception just does not include any
elements for the nested Exception). I've tried setting the cause on
the main exception, adding a brand new property to hold the nested
exception, using @XmlSeeAlso to ensure the class of the nested
Exception class is seen, and none of these work (the generated schema
just ignores the nested Exception property). Other properties added
to the main Exception do show up as expected.
I'm wondering if there's some part of the JAXB or JAX-WS spec that
says nested exceptions shouldn't be propagated? Or is there some
other reason why this behavior is expected?
Thanks,
Aaron
