Hope this helps...
/// MSG ///
<wsdl:message name="doSomethingResponse">
<wsdl:part name="return"
element="response:doSomethingResponse" />
</wsdl:message>
<wsdl:message name="doSomething">
<wsdl:part name="parameters"
element="request:doSomething" />
</wsdl:message>
<wsdl:message name="ProbOneException">
<wsdl:part name="fault"
element="exception:ProbOneException" />
</wsdl:message>
<wsdl:message name="ProbTwoException">
<wsdl:part name="fault"
element="exception:ProbTwoException" />
</wsdl:message>
/// PORT TYPE ////
<wsdl:operation name="doSeomthing">
<wsdl:input message="intf:doSomething"
name="doSomething" />
<wsdl:output message="intf:doSomethingResponse"
name="doSomethingResponse" />
<wsdl:fault message="intf:ProbOneException"
name="ProbOneException" />
<wsdl:fault message="intf:ProbTwoException"
name="ProbTwoException" />
</wsdl:operation>
/// BINDINGS ////
<wsdl:operation name="doSomething">
<wsdlsoap:operation soapAction="" />
<wsdl:input>
<wsdlsoap:body use="literal" />
</wsdl:input>
<wsdl:output>
<wsdlsoap:body use="literal" />
</wsdl:output>
<wsdl:fault name="ProbOneException">
<wsdlsoap:fault use="literal" />
</wsdl:fault>
<wsdl:fault name="ProbTwoException">
<wsdlsoap:fault use="literal" />
</wsdl:fault>
</wsdl:operation>
-----Original Message-----
From: Amitesh Pandya [mailto:[EMAIL PROTECTED]
Sent: 17 May 2006 08:28
To: [email protected]
Subject: HELLLLLLLLLLLPPPPPPP
Come on ! I can't believe no one has got this error???
I know you've got the answer. Please let me know....
Here is the problem Again.........
Hi,
I'm currently working on project and we are using Axis2 + Sandesha2
(Both Version 1.0) for the WS-RM.
One of my requirements is to return a SOAP Fault after the validation
fails.
I've created the service using WSDL2Java. The service works fine. But
when I try to throw an exception (Axis Fault) from the generated
"Skeleton" I get another Axis exception.
I looked into it and it seems to be a problem with the AXIOM. The real
problem happens when I try to call
inMessage.getEnvelope().getHeader()
Actually this method is called in the "AxisEngine" which is causing all
the troubles.
Please let me know if this is the known problem or If I'm missing
something.
Kindly suggest what is the best way of sending the Custom SOAP Fault.
Your response to this query is greatly appreciated.
Thanks in advance
Amitesh
Please find the attached Stacktrace:
##################################################
[16/05/06 11:22:49:505 BST] 00000035 SystemErr R
org.apache.axiom.om.OMException
at
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementIm
pl.java:265)
at
org.apache.axiom.om.impl.traverse.OMChildrenQNameIterator.hasNext(OMChil
drenQNameIterator.java(Compiled
Code))
at
org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName(OMElem
entImpl.java:222)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeI
mpl.java:76)
at
uk.gov.cjse.schemas.DeliverPortMessageReceiverInOnly.invokeBusinessLogic
(DeliverPortMessageReceiverInOnly.java:102)
at
org.apache.axis2.receivers.AbstractInMessageReceiver.receive(AbstractInM
essageReceiver.java:34)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:454)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReques
t(HTTPTransportUtils.java:284)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.ja
va:1212)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrap
per.java:629)
at
com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:2837)
at
com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:220)
at
com.ibm.ws.webcontainer.VirtualHost.handleRequest(VirtualHost.java:204)
at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:168
1)
at
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:7
7)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscriminatio
n(HttpInboundLink.java:421)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformatio
n(HttpInboundLink.java:367)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLi
nk.java:276)
at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscr
iminaters(NewConnectionInitialReadCallback.java:201)
at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(Ne
wConnectionInitialReadCallback.java:103)
at
com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueMa
nager.java:548)
at
com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.
java:601)
at
com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.
java:934)
at
com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager
.java:1021)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)
-----------------------------------------------------
THE INFORMATION IN THIS E-MAIL AND IN ANY ATTACHMENTS IS CONFIDENTIAL
AND MAY BE PRIVILEGED OR OTHERWISE PROTECTED FROM DISCLOSURE.
IF YOU ARE NOT THE INTENDED RECIPIENT AND HAVE RECEIVED IT IN ERROR YOU ARE ON
NOTICE OF ITS STATUS.
PLEASE NOTIFY THE SENDER IMMEDIATELY BY RETURN EMAIL AND THEN DELETE THIS EMAIL
AND ANY ATTACHMENT FROM YOUR SYSTEM.
YOU MUST NOT RETAIN, COPY OR USE THIS E-MAIL OR ANY ATTACHMENT FOR ANY PURPOSE,
NOR DISCLOSE ALL OR ANY PART OF ITS CONTENTS TO ANY OTHER PERSON:
TO DO SO COULD BE A BREACH OF CONFIDENCE
EMAIL MAY BE SUSCEPTIBLE TO DATA CORRUPTION, INTERCEPTION AND UNAUTHORISED
AMENDMENT,
AND WE DO NOT ACCEPT LIABILITY FOR ANY SUCH CORRUPTION, INTERCEPTION OR
AMENDMENT OR THE CONSEQUENCES THEREOF.
WE MAY MONITOR THE CONTENT OF EMAILS SENT AND RECEIVED VIA OUR NETWORK FOR
VIRUSES OR UNAUTHORISED USE AND FOR OTHER LAWFUL BUSINESS PURPOSES.
WE DO NOT ACCEPT RESPONSIBILITY FOR ANY LOSS OR DAMAGE ARISING FROM A VIRUS IN
ANY EMAIL OR ATTACHMENT.
-----------------------------------------------
[EMAIL PROTECTED]
