You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2007/04/30 11:38:17 UTC
[jira] Updated: (AXIS2-1803) Default stubs do not handle unexpected
faults
[ https://issues.apache.org/jira/browse/AXIS2-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe updated AXIS2-1803:
-------------------------------------
Fix Version/s: (was: 1.2)
nightly
> Default stubs do not handle unexpected faults
> ---------------------------------------------
>
> Key: AXIS2-1803
> URL: https://issues.apache.org/jira/browse/AXIS2-1803
> Project: 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: nightly
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org