Add elementFormDefault="qualified" to the declaration in your WSDL.
In your message you specify a default namespace in the
element, so that namespace then applies to all child
elements in the message instance. If you do not specify
elementFormDefault, then your child elements are defined as
unqu
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.
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 y
0700
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: 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
Here you go. Any help is much appreciated.
http://www.w3.org/2001/XMLSchema";
targetNamespace="http://online.nielsen.com/ca/api/";>
Can you share the types section of your WSDL file?
On Wed, Aug 20, 2008 at 1:42 AM, Andrew Zielinski 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 th
