008-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
>
&g
?
>>>
>>> On Wed, Aug 20, 2008 at 1:42 AM, Andrew Zielinski >> gmail.com> wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> Like many users I was having issues with 'unexpected ele
elp
>>> 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/
>>> ">
>>>
>>> htt
gt;> 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/
>>> ">
>>>
>>>
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
t;;>
>>
>>
>> 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 t
0: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
>
>
> --
&
1T00: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-AXI
