Skip to main content

JAX-WS: Propagation of Server-side Stacktrace using Glassfish 3.1.x

No replies
berges
Offline
Joined: 2009-12-22
Points: 0

Hello.
The problem I am having is explained/related to these articles:
- http://weblogs.java.net/blog/ramapulavarthi/archive/2007/02/useful_goodi... (under section "Propagation of Server-side Stacktrace")
- http://xml.sys-con.com/node/952427

In my case, I want the full stack trace propagated to the webservice clients.

When I used Glassfish 3.0.1, it allowed me to have my SOAP clients view the full stack trace, even when Runtime Exceptions occured.

Moving on to Glassfish 3.1.2 the SOAP fault details seems to be suppressed by default, and I can't find a way to enable them. I've tried setting
-Dcom.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace=true in domain.xml and setting the same property in Glassfish "System Properties", both without any luck.

Looking at the WSDL-endpoints of the deployed web service I am testing, it looks like Glassfish 3.1.2 is using "Metro/2.2-b13 (branches/2.2-6964; 2012-01-09T18:04:18+0000) JAXWS-RI/2.2.6-promoted-b20 JAXWS/2.2 svn-revision#unknown" and Glassfish 3.0.1 is using "JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.2.1-hudson-28-".

Other details about my environment:
JDK: 1.6.0_33
OS: Windows Server 2008 R2 Enterprise

Any ideas to how I can get Glassfish 3.1.2 to propagate the full stack trace?

Thanks