axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ajith Ranabahu <ajith.ranab...@gmail.com>
Subject Re: Axis2 WSDL compliance and intelligent support for generation
Date Tue, 07 Feb 2006 13:24:38 GMT
Yes Anne, you are quite right.
In Axis2 when a message is located with a type, we generate a piece of
schema and make it look like a doc/lit. We use the rules you mentioned
to generate this wrapper schema.
I've a feeling that this problem is related to the wrapper schema
QNames not being right!

On 2/7/06, Anne Thomas Manes <atmanes@gmail.com> wrote:
> Probably not a bug. If you use @type with document style, then you have no
> element QName. When using RPC style, the SOAP engine dynamically generates a
> QName from the operation name and the @namespace attribute from <soap:body>
> in the binding. When using Document style, the QName comes from the @element
> attribute in the <wsdl:part>. If you don't have an @element, then it has no
> QName.
>
> Anne
>
>
> On 2/6/06, Ajith Ranabahu <ajith.ranabahu@gmail.com> wrote:
> > Hi Hui,
> >
> > > "org.apache.axis2.om.OMElement.MY_QNAME" could not be
> found
> > > in the following line of code:
> > >
> (org.apache.axis2.om.OMAbstractFactory.getOMFactory(),
> > > param.getPullParser
> (org.apache.axis2.om.OMElement.MY_QNAME));
> >
> > This could be a bug actually (usually occurs when the databinding
> > failed. OMElement is the default). Can you post the WSDL ?
> >
> > --
> > Ajith Ranabahu
> >
>
>


--
Ajith Ranabahu

Mime
View raw message