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 "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org> on 2007/06/14 21:07:25 UTC
[jira] Resolved: (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 ]
Amila Chinthaka Suriarachchi resolved AXIS2-1803.
-------------------------------------------------
Resolution: Won't Fix
this is not a bug since generated code throw it out
> 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
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Blocker
> Fix For: 1.3
>
>
> 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
Re: [jira] Resolved: (AXIS2-1803) Default stubs do not handle unexpected faults
Posted by Paul Fremantle <pz...@gmail.com>.
The problem is that the generated code throws the wrong sort of fault.
It does throw a fault, but it doesn't throw a fault that lets you know
there's been a security error. Instead it throws some wierd and hard
to understand XML demarshalling fault.
I don't think this should be Wont Fix!
Paul
On 6/14/07, Amila Chinthaka Suriarachchi (JIRA) <ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/AXIS2-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Amila Chinthaka Suriarachchi resolved AXIS2-1803.
> -------------------------------------------------
>
> Resolution: Won't Fix
>
> this is not a bug since generated code throw it out
>
> > 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
> > Assignee: Amila Chinthaka Suriarachchi
> > Priority: Blocker
> > Fix For: 1.3
> >
> >
> > 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
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org