Re: Identified AXIS2 Unexpected Element issue but how do I get this to work with stubs
I thought I had fixed the issue but alas that wasn't the case :( Hi Jeff, I had it declared in the definitions element. I put the prefix in the schema element and that didn't seem to work either. Jeff Greif wrote: > > Note that in this snippet, you haven't declared the ca: prefix used > below. It could be declared in the definitions element, though. > > Perhaps it would help to declare the ca: prefix in the schema element. > > Jeff > > On Thu, Aug 21, 2008 at 4:35 PM, Andrew Zielinski > <[EMAIL PROTECTED]> wrote: >> >> Here you go. Any help is much appreciated. >> >> >>http://www.w3.org/2001/XMLSchema"; >> targetNamespace="http://online.nielsen.com/ca/api/";> >> >> >> >>> type="ca:SummaryRequest"/> >> >> >> >> >>> type="unsignedLong" nillable="false" /> >>> type="ca:DateRange" nillable="false" /> >>> type="string" minOccurs="0" maxOccurs="1" /> >>> type="ca:Pagination" minOccurs="0" >> maxOccurs="1" /> >>> type="ca:Sort" minOccurs="0" maxOccurs="1" /> >>> type="string" minOccurs="0" >> maxOccurs="unbounded" /> >> >> >> >> >> >> >>> minOccurs="1" maxOccurs="unbounded" >> /> >> >> >> >> >> >>> type="string"/> >>> type="string"/> >> >> >> >> >> >> >> >> >> >> >> >> >>> type="dateTime"/> >>> type="dateTime"/> >> >> >> >> >> >> >>> type="dateTime"/> >>> type="dateTime" minOccurs="0" >> maxOccurs="1"/> >>> type="long"/> >>> maxOccurs="unbounded"/> >> >> >> >> >> >>> minOccurs="0" maxOccurs="1"/> >>> maxOccurs="unbounded"/> >>> type="ca:Metric" maxOccurs="unbounded"/> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>> /> >>> use="optional" /> >> >> >> >> >> >> >> >> >> >> >> >>
Re: ( Fixed It )Identified AXIS2 Unexpected Element issue but how do I get this to work with stubs
When I do the following everything works out fine. I prefer to have all the elements at the top of the types section but the stubs working is more important to me. Andrew Zielinski wrote: > > Here you go. Any help is much appreciated. > > > http://www.w3.org/2001/XMLSchema"; > targetNamespace="http://online.nielsen.com/ca/api/";> > > > >type="ca:SummaryRequest"/> > > > > >type="unsignedLong" nillable="false" /> >type="ca:DateRange" nillable="false" /> >type="string" minOccurs="0" maxOccurs="1" /> >type="ca:Pagination" minOccurs="0" > maxOccurs="1" /> >type="ca:Sort" minOccurs="0" maxOccurs="1" /> >type="string" minOccurs="0" > maxOccurs="unbounded" /> > > > > > > >minOccurs="1" maxOccurs="unbounded" > /> > > > > > >type="string"/> >type="string"/> > > > > > > > > > > > > > > > > > > > > > >type="dateTime"/> >type="dateTime" minOccurs="0" > maxOccurs="1"/> > >maxOccurs="unbounded"/> > > > > > >minOccurs="0" maxOccurs="1"/> >maxOccurs="unbounded"/> >maxOccurs="unbounded"/> > > > > > > > > > > > > > > > > >use="optional" /> > > > > > > > > > > > > Eran Chinthaka-3 wrote: >> >> Can you share the types section of your WSDL file? >> >> On Wed, Aug 20, 2008 at 1:42 AM, Andrew Zielinski > gmail.com> wrote: >> >>> >>> Hi, >
Re: Identified AXIS2 Unexpected Element issue but how do I get this to work with stubs
Here you go. Any help is much appreciated. http://www.w3.org/2001/XMLSchema"; targetNamespace="http://online.nielsen.com/ca/api/";> Eran Chinthaka-3 wrote: > > Can you share the types section of your WSDL file? > > On Wed, Aug 20, 2008 at 1:42 AM, Andrew Zielinski gmail.com> wrote: > >> >> Hi, >> >> Like many users I was having issues with 'unexpected element'. With the >> help >> of TCPMon I was able to resolve the issue. Instead of the soap request >> being >> formed like this: >> >> >> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ >> "> >> >> http://online.nielsen.com/ca/api/";> >> 55 >> >> 2008-11-01T00:00:00.000+10:00 >> 2008-11-01T00:00:00.000+10:00 >> >> >> >> >> >> I would need to specify the namespace and prefix in soapenv:Envelope like >> this: >> >> >> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/ >> " >> xmlns:q0="http://online.nielsen.com/ca/api/";> >> >> >> 55 >> >> 2008-11-01T00:00:00.000+10:00 >> 2008-11-01T00:00:00.000+10:00 >> >> >> >> >> >> My question is, is there anyway to modify the stub request so it is like >> the >> second example or is there anything that I would I have to do to my WSDL >> for >> the first request to be valid. >> >> Cheers, >> >> Andrew >> >> >> -- >> View this message in context: >> http://www.nabble.com/Identified-AXIS2-Unexpected-Element-issue-but-how-do-I-get-this-to-work-with-stubs-tp19063214p19063214.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > With Mettha, > Eran Chinthaka > > >
Identified AXIS2 Unexpected Element issue but how do I get this to work with stubs
Hi, Like many users I was having issues with 'unexpected element'. With the help of TCPMon I was able to resolve the issue. Instead of the soap request being formed like this: http://schemas.xmlsoap.org/soap/envelope/";> http://online.nielsen.com/ca/api/";> 55 2008-11-01T00:00:00.000+10:00 2008-11-01T00:00:00.000+10:00 I would need to specify the namespace and prefix in soapenv:Envelope like this: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:q0="http://online.nielsen.com/ca/api/";> 55 2008-11-01T00:00:00.000+10:00 2008-11-01T00:00:00.000+10:00 My question is, is there anyway to modify the stub request so it is like the second example or is there anything that I would I have to do to my WSDL for the first request to be valid. Cheers, Andrew -- View this message in context: http://www.nabble.com/Identified-AXIS2-Unexpected-Element-issue-but-how-do-I-get-this-to-work-with-stubs-tp19063214p19063214.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
