axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Punnoose, Roshan" <punnoo...@bah-systems.com>
Subject RE: [Axis2] Custom Faults
Date Fri, 22 Sep 2006 14:24:18 GMT
Hi,

I am trying to write a custom SOAP 1.2 fault and my code looks like:

AxisFault fault = new AxisFault(new QName("", "faultCode"),
				"FaultReason", "FaultNode",
"FaultRolde", data);
throw fault;

But no matter how I change it, it always looks like:
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
	<soapenv:Header>
	
<wsa:To>http://192.168.104.25:6060/axis2/services/annonService6586390/an
nonOutInOp</wsa:To>
		<wsa:ReplyTo>
	
<wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address
>
		</wsa:ReplyTo>
	
<wsa:MessageID>urn:uuid:AC206497C0CD80ACB511589347892291</wsa:MessageID>
	
<wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
		<wsa:RelatesTo
wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply">urn:uu
id:8ED4E782A3CE671B3611589347874631</wsa:RelatesTo>
	</soapenv:Header>
	<soapenv:Body>
		<soapenv:Fault>
			<soapenv:Code>
	
<soapenv:Value>soapenv:Sender</soapenv:Value>
			</soapenv:Code>
			<soapenv:Reason>
				<soapenv:Text
xml:lang="en-US">unknown</soapenv:Text>
			</soapenv:Reason>
			<soapenv:Detail>
	
<Exception>org.apache.axis2.AxisFault&#13;
	at
org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver.invokeBusinessLog
ic(RawXMLINOnlyMessageReceiver.java:104)&#13;
	at
org.apache.axis2.receivers.AbstractInMessageReceiver.receive(AbstractInM
essageReceiver.java:36)&#13;
	at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:492)&#13;
	at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques
t(HTTPTransportUtils.java:324)&#13;
	at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:230)
&#13;
	at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)&#13;
	at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)&#13;
	at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Se
rvletStubImpl.java:971)&#13;
	at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:402)&#13;
	at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.
java:305)&#13;
	at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
un(WebAppServletContext.java:6350)&#13;
	at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:317)&#13;
	at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118
)&#13;
	at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServl
etContext.java:3635)&#13;
	at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.
java:2585)&#13;
	at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)&#13;
	at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)&#13;
</Exception>
			</soapenv:Detail>
		</soapenv:Fault>
	</soapenv:Body>
</soapenv:Envelope>



I do not want the stack trace, but I want to put my own OMElement in the
detail section. Any ideas why I can't create the custom fault?

Roshan Punnoose
Phone: 301-497-6039


Mime
View raw message