• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Customize AXISFault before reaching the Operation

 
mohammed bakhti
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I'm acctually working with Axis2 and trying to do something (maybe can't be done) :

When i send a wrong request to my service using WS-ADDRESSING (let say : a wrong was:action ) the axis angine reply with an soapevn:server fault somethig like :


<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Action>http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action>
<wsa:RelatesTo>1285</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>com.ctc.wstx.exc.WstxParsingException: Unexpected close tag.
at [row,col {unknown-source}]: [12,46]</faultstring>
<detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>


this reply is from axis (my service hasn't been contacted yet) and i can see some WSA data : Action and RelatesTo .

What i need to accomplish is to add more information to the header (ws-addressing) like : FROM Content, replyto ... and other stuff .

As the exception throws before reaching my service (code) how can i do this ? is it possible?

Thanks
 
Randall Vasquez
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
how did you resolve this ?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic