[
http://issues.apache.org/jira/browse/AXIS2-1803?page=comments#action_12459547 ]
Amila Chinthaka Suriarachchi commented on AXIS2-1803:
-----------------------------------------------------
can you please describe this with an example.
As I understood you talk about this.
_operationClient.execute(true);
// some code here to excecute the correct response
}catch(org.apache.axis2.AxisFault f){
org.apache.axiom.om.OMElement faultElt = f.getDetail();
if (faultElt!=null){
if (faultExeptionNameMap.containsKey(faultElt.getQName())){
// code to data bind the fault element
here we data bind an exception only if it contains in the faultExceptionNameMap
(i.e. only if it contains in wsdl) otherwise throws the AxisFault as it is.
> Default stubs do not handle unexpected faults
> ---------------------------------------------
>
> Key: AXIS2-1803
> URL: http://issues.apache.org/jira/browse/AXIS2-1803
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: codegen
> Affects Versions: 1.1
> Environment: Any
> Reporter: Paul Fremantle
> Assigned To: Amila Chinthaka Suriarachchi
> Fix For: 1.2
>
>
> By default, when I generate a stub with ADB it assumes ALL messages conform
> to the WSDL. I havent any fault definitions in my WSDL, so suppose I get a
> security fault back from the server, the client will try to demarshall this
> as if it was a proper response. It would be really nice to spot SOAP faults
> in this case and not try to demarshall them using my business logic response
> databinding.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
