You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by quzhe <zh...@hotmail.com> on 2008/12/10 08:12:10 UTC
a bug in the xmlbean binding
hi,All:
I write a webservice with xmlbean binding, and each service throw some
excetion:
void method1()throws AuthorityFault,ValidationFault,SystemFault;
void method2()throws AuthorityFault,ValidationFault,SystemFault;
void method3()throws AuthorityFault,ValidationFault,SystemFault;
I hope I can get correct exception in the client side, but I found only
one method can get correct exception in the client, others can not, so I
dedug cxf's code, I found
in the XmlBeansSchemaInitializer.java at line 138
here have a "part", and first time part.getXmlSchema==null, and
system will set xmlshcema to this part, then put xmlschema into schemas.
when system binding method1 , not problem, and mothod2 looks not problem,
but in the method3, there have some thing happen, that part.getXmlSchema has
been set to null, because at line 206, this fault have exist in the schemas,
so el will not be mapping again, and from this method, all fault part's
xmlshcema will be null, cxf will not throw any exception here.
the problem will happen in the WebFaultOutInterceptor, at line 112, will
call DataWriterImpl
in the DataWriterImpl, line 95, SchemaType st will be null, and here will
throw a nullpoint exception, when WebFaultOutInterceptor catch
nullpointexception, will throws a SoapFaultException, not the faults I
wanted.
--
View this message in context: http://www.nabble.com/a-bug-in-the-xmlbean-binding-tp20930183p20930183.html
Sent from the cxf-user mailing list archive at Nabble.com.
RE: a bug in the xmlbean binding
Posted by quzhe <zh...@hotmail.com>.
please see attachment, it is a maven project
Sean O'Callaghan wrote:
>
> Hi,
>
> Can you please provide a testcase so that we can try and debug the
> problem.
>
> Thanks,
>
> Seán.
>
>
>
> -----Original Message-----
> From: quzhe [mailto:zhe_qu@hotmail.com]
> Sent: 10 December 2008 07:12
> To: users@cxf.apache.org
> Subject: a bug in the xmlbean binding
>
>
> hi,All:
>
> I write a webservice with xmlbean binding, and each service throw some
> excetion:
> void method1()throws AuthorityFault,ValidationFault,SystemFault;
> void method2()throws AuthorityFault,ValidationFault,SystemFault;
> void method3()throws AuthorityFault,ValidationFault,SystemFault;
>
> I hope I can get correct exception in the client side, but I found
> only
> one method can get correct exception in the client, others can not, so I
> dedug cxf's code, I found
> in the XmlBeansSchemaInitializer.java at line 138
> here have a "part", and first time part.getXmlSchema==null, and
> system will set xmlshcema to this part, then put xmlschema into schemas.
> when system binding method1 , not problem, and mothod2 looks not problem,
> but in the method3, there have some thing happen, that part.getXmlSchema
> has
> been set to null, because at line 206, this fault have exist in the
> schemas,
> so el will not be mapping again, and from this method, all fault part's
> xmlshcema will be null, cxf will not throw any exception here.
>
> the problem will happen in the WebFaultOutInterceptor, at line 112,
> will
> call DataWriterImpl
>
> in the DataWriterImpl, line 95, SchemaType st will be null, and here
> will
> throw a nullpoint exception, when WebFaultOutInterceptor catch
> nullpointexception, will throws a SoapFaultException, not the faults I
> wanted.
>
>
>
> --
> View this message in context:
> http://www.nabble.com/a-bug-in-the-xmlbean-binding-tp20930183p20930183.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
>
http://www.nabble.com/file/p20955346/common-webservice.rar
common-webservice.rar
--
View this message in context: http://www.nabble.com/a-bug-in-the-xmlbean-binding-tp20930183p20955346.html
Sent from the cxf-user mailing list archive at Nabble.com.
RE: a bug in the xmlbean binding
Posted by quzhe <zh...@hotmail.com>.
hi,please use this project,download common-webservice2.rar, I change test
case, there have 3 test, 2 failed, 1 success, hope this can help you
understand, thanks
Sean O'Callaghan wrote:
>
> Hi,
>
> Can you please provide a testcase so that we can try and debug the
> problem.
>
> Thanks,
>
> Seán.
>
>
>
> -----Original Message-----
> From: quzhe [mailto:zhe_qu@hotmail.com]
> Sent: 10 December 2008 07:12
> To: users@cxf.apache.org
> Subject: a bug in the xmlbean binding
>
>
> hi,All:
>
> I write a webservice with xmlbean binding, and each service throw some
> excetion:
> void method1()throws AuthorityFault,ValidationFault,SystemFault;
> void method2()throws AuthorityFault,ValidationFault,SystemFault;
> void method3()throws AuthorityFault,ValidationFault,SystemFault;
>
> I hope I can get correct exception in the client side, but I found
> only
> one method can get correct exception in the client, others can not, so I
> dedug cxf's code, I found
> in the XmlBeansSchemaInitializer.java at line 138
> here have a "part", and first time part.getXmlSchema==null, and
> system will set xmlshcema to this part, then put xmlschema into schemas.
> when system binding method1 , not problem, and mothod2 looks not problem,
> but in the method3, there have some thing happen, that part.getXmlSchema
> has
> been set to null, because at line 206, this fault have exist in the
> schemas,
> so el will not be mapping again, and from this method, all fault part's
> xmlshcema will be null, cxf will not throw any exception here.
>
> the problem will happen in the WebFaultOutInterceptor, at line 112,
> will
> call DataWriterImpl
>
> in the DataWriterImpl, line 95, SchemaType st will be null, and here
> will
> throw a nullpoint exception, when WebFaultOutInterceptor catch
> nullpointexception, will throws a SoapFaultException, not the faults I
> wanted.
>
>
>
> --
> View this message in context:
> http://www.nabble.com/a-bug-in-the-xmlbean-binding-tp20930183p20930183.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
>
http://www.nabble.com/file/p20955470/common-webservice2.rar
common-webservice2.rar
--
View this message in context: http://www.nabble.com/a-bug-in-the-xmlbean-binding-tp20930183p20955470.html
Sent from the cxf-user mailing list archive at Nabble.com.
RE: a bug in the xmlbean binding
Posted by Sean O'Callaghan <SE...@progress.com>.
Hi,
Can you please provide a testcase so that we can try and debug the problem.
Thanks,
Seán.
-----Original Message-----
From: quzhe [mailto:zhe_qu@hotmail.com]
Sent: 10 December 2008 07:12
To: users@cxf.apache.org
Subject: a bug in the xmlbean binding
hi,All:
I write a webservice with xmlbean binding, and each service throw some
excetion:
void method1()throws AuthorityFault,ValidationFault,SystemFault;
void method2()throws AuthorityFault,ValidationFault,SystemFault;
void method3()throws AuthorityFault,ValidationFault,SystemFault;
I hope I can get correct exception in the client side, but I found only
one method can get correct exception in the client, others can not, so I
dedug cxf's code, I found
in the XmlBeansSchemaInitializer.java at line 138
here have a "part", and first time part.getXmlSchema==null, and
system will set xmlshcema to this part, then put xmlschema into schemas.
when system binding method1 , not problem, and mothod2 looks not problem,
but in the method3, there have some thing happen, that part.getXmlSchema has
been set to null, because at line 206, this fault have exist in the schemas,
so el will not be mapping again, and from this method, all fault part's
xmlshcema will be null, cxf will not throw any exception here.
the problem will happen in the WebFaultOutInterceptor, at line 112, will
call DataWriterImpl
in the DataWriterImpl, line 95, SchemaType st will be null, and here will
throw a nullpoint exception, when WebFaultOutInterceptor catch
nullpointexception, will throws a SoapFaultException, not the faults I
wanted.
--
View this message in context: http://www.nabble.com/a-bug-in-the-xmlbean-binding-tp20930183p20930183.html
Sent from the cxf-user mailing list archive at Nabble.com.