On Tue, Jan 6, 2009 at 1:21 AM, excess2 <gafo...@yahoo.com> wrote:

>
> The non-working request matches the wsdl.


wsdl2java tool assumes that the wsdl correctly describes the service. one
option is to change the wsdl
file to suite for the service and generate the code with that.

thanks,
Amila.

>
>
> Somehow the working request has apparently been tweaked.
>
> G
>
>
>
> Andreas Veithen-2 wrote:
> >
> > Can you check which of the two requests conforms to the WSDL?
> >
> > Andreas
> >
> > On Mon, Jan 5, 2009 at 20:21, excess2 <gafo...@yahoo.com> wrote:
> >>
> >> Thanks!
> >>
> >> I see the problem you pointed out.
> >>
> >> However, I have no idea how to fix this.
> >>
> >> The stubs I'm using for the client were generated from a
> >> VOIP_SIP_Trouble_Ticket10 wsdl.
> >>
> >> The <urn:AuthenticationInfo xmlns:urn = "urn:VOIP_SIP_Trouble_Ticket10">
> >> is
> >> populated by stub code
> >>
> >> not by an explicit call.  How do I force it to VOIP_SIP_Trouble_Ticket
> >> instead?
> >>
> >> Is there an axis2 method that lets me override the default
> >> VOIP_SIP_Trouble_Ticket10 with VOIP_SIP_Trouble_Ticket?
> >>
> >> Thanks,
> >>
> >> G
> >>
> >>
> >>
> >> Andreas Veithen-2 wrote:
> >>>
> >>> The difference between the two requests is in the namespace URIs of
> >>> AuthenticationInfo and its children. In the first request all elements
> >>> are in the "urn:VOIP_SIP_Trouble_Ticket10" namespace, while in the
> >>> second, AuthenticationInfo is in "urn:VOIP_SIP_Trouble_Ticket" and its
> >>> children in "AuthenticationInfo".
> >>>
> >>> Andreas
> >>>
> >>>
> >>>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21297434.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Axis2-client-request-to-IIS-5.0-returns-a-500-error.-tp21236655p21297928.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Reply via email to