AxisFault is probably unchecked so it gets
wrapped. I bet the spec says that only
checked exceptions have to get passed back
intact.
You could wrap AxisFault in a checked exception,
maybe...
JD
-----Original Message-----
From: Jonas Engman [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003 1:21 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] How to throw AxisFault in JBoss.net?
I'm using JBoss 3.2beta1/JBoss.net and I'm trying to throw an AxisFault
from a SessionBean but the exception seems somehow be wrapped inside a
javax.ejb.EJBException.
I'm throwing the fault using
throw new AxisFault("a fault has occurred");
but the faultString that appears on the client-side is
"javax.ejb.EJBException: null; CausedByException is: a fault has
occurred".
A closer look at the <detail>-body using TCPMon shows that the it
contains the full stacktrace followed by the original faultString but
it's all wrapped inside the <detail>-tag.
The same thing goes for the original faultCode, faultActor and
faultDetail.
Is it somehow possible to throw an AxisFault that doesn't get wrapped
inside a SOAPFault that contains the javax.ejb.EJBException?
Without the ability to throw a user-defined AxisFault I don't see how a
fault should be reported to the client-side.
Thanks
Jonas
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
