You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Reynir Hubner <re...@hugsmidjan.is> on 2006/08/24 18:00:54 UTC
WS-routing
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I am getting the following error when trying to access a remote service
(that I am not in control of), that uses WS-routing.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}MustUnderstand
faultSubcode:
faultString: Did not understand "MustUnderstand" header(s):
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:96)
this is because I get this kind of header, with the mustUnderstand flag
set:
<soap:Header>
<wsrp:path soap:actor="http://schemas.xmlsoap.org/soap/actor/next"
soap:mustUnderstand="1" xmlns:wsrp="http://schemas.xmlsoap.org/rp">
<wsrp:action>http://schemas.xmlsoap.org/soap/fault</wsrp:action>
<wsrp:id>uuid:9e6d818f-2b6e-4689-9877-9b855f400b27</wsrp:id>
<wsrp:fault>
<wsrp:code>701</wsrp:code>
<wsrp:reason>WS-Routing Header Required</wsrp:reason>
</wsrp:fault>
</wsrp:path>
</soap:Header>
And obviously Axis does not understand the wsrp headres, as it does not
understand WS-routing standard.
Can I somehow tell Axis not to evaluate what's marked as mustUnderstand ?
Does anyone by any change have implementation for WS-routing ?
Can anyone explain in short how I would implement WS-routing handler (or
show a sample of any simple handler) ?
thank you very much.
- -reynir
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFE7c0219KgIQihNwgRAvkGAKDyPV/qLcudDK1NvHVPCQ384+SZPACfQ7Qd
JkxY3I7lKfX4B5GVxyEhqug=
=ViWs
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WS-routing
Posted by Anne Thomas Manes <at...@gmail.com>.
Apache WSS4J is a sample Axis handler. (It implements support for WS-Security.)
Anne
On 8/25/06, Reynir Hubner <re...@hugsmidjan.is> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Anne,
> thanx for the reply.
>
> Yes I'm dealing with an old service, and I'm hoping it will be updated.
>
> I also realized that I have to add some ws-routing header too, I was
> thinking I might be able to put that in somehow.
>
> How does one add a handler ? wich interfaces do I need to implement, are
> there any simple handlers that I can copy to fake this behaviour ?
>
> thanx again...
>
> - -reynir
>
>
>
> Anne Thomas Manes wrote:
> > You must be dealing with an old service, because WS-Routing was
> > superceded by WS-Addressing 3 years ago.
> >
> > In any case, what you need to do is add a handler to add and process
> > the wsrp header. (Note that the return message is telling you that you
> > need to include a WS-Routing header in your input message, so it's not
> > just a matter of ignoring the header.)
> >
> > Anne
> >
> > On 8/24/06, Reynir Hubner <re...@hugsmidjan.is> wrote:
> >
> > Hi,
> > I am getting the following error when trying to access a remote service
> > (that I am not in control of), that uses WS-routing.
> >
> > AxisFault
> > faultCode: {http://schemas.xmlsoap.org/soap/envelope/}MustUnderstand
> > faultSubcode:
> > faultString: Did not understand "MustUnderstand" header(s):
> > faultActor:
> > faultNode:
> > faultDetail:
> > {http://xml.apache.org/axis/}stackTrace:
> > at
> > org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:96)
> >
> >
> > this is because I get this kind of header, with the mustUnderstand flag
> > set:
> >
> > <soap:Header>
> > <wsrp:path soap:actor="http://schemas.xmlsoap.org/soap/actor/next"
> > soap:mustUnderstand="1" xmlns:wsrp="http://schemas.xmlsoap.org/rp">
> > <wsrp:action>http://schemas.xmlsoap.org/soap/fault</wsrp:action>
> > <wsrp:id>uuid:9e6d818f-2b6e-4689-9877-9b855f400b27</wsrp:id>
> > <wsrp:fault>
> > <wsrp:code>701</wsrp:code>
> > <wsrp:reason>WS-Routing Header Required</wsrp:reason>
> > </wsrp:fault>
> > </wsrp:path>
> > </soap:Header>
> >
> > And obviously Axis does not understand the wsrp headres, as it does not
> > understand WS-routing standard.
> >
> >
> > Can I somehow tell Axis not to evaluate what's marked as mustUnderstand ?
> > Does anyone by any change have implementation for WS-routing ?
> > Can anyone explain in short how I would implement WS-routing handler (or
> > show a sample of any simple handler) ?
> >
> > thank you very much.
> > -reynir
> >
> >>
> - ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
> >>
> >>
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFE7yle19KgIQihNwgRApPpAJ98tMmSyNimSMveH31RSnk5H7T/mwCg4v8w
> hKDyHltOzXRbSvS0AGvXl/U=
> =wPhD
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WS-routing
Posted by Reynir Hubner <re...@hugsmidjan.is>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Anne,
thanx for the reply.
Yes I'm dealing with an old service, and I'm hoping it will be updated.
I also realized that I have to add some ws-routing header too, I was
thinking I might be able to put that in somehow.
How does one add a handler ? wich interfaces do I need to implement, are
there any simple handlers that I can copy to fake this behaviour ?
thanx again...
- -reynir
Anne Thomas Manes wrote:
> You must be dealing with an old service, because WS-Routing was
> superceded by WS-Addressing 3 years ago.
>
> In any case, what you need to do is add a handler to add and process
> the wsrp header. (Note that the return message is telling you that you
> need to include a WS-Routing header in your input message, so it's not
> just a matter of ignoring the header.)
>
> Anne
>
> On 8/24/06, Reynir Hubner <re...@hugsmidjan.is> wrote:
>
> Hi,
> I am getting the following error when trying to access a remote service
> (that I am not in control of), that uses WS-routing.
>
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}MustUnderstand
> faultSubcode:
> faultString: Did not understand "MustUnderstand" header(s):
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:
> at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:96)
>
>
> this is because I get this kind of header, with the mustUnderstand flag
> set:
>
> <soap:Header>
> <wsrp:path soap:actor="http://schemas.xmlsoap.org/soap/actor/next"
> soap:mustUnderstand="1" xmlns:wsrp="http://schemas.xmlsoap.org/rp">
> <wsrp:action>http://schemas.xmlsoap.org/soap/fault</wsrp:action>
> <wsrp:id>uuid:9e6d818f-2b6e-4689-9877-9b855f400b27</wsrp:id>
> <wsrp:fault>
> <wsrp:code>701</wsrp:code>
> <wsrp:reason>WS-Routing Header Required</wsrp:reason>
> </wsrp:fault>
> </wsrp:path>
> </soap:Header>
>
> And obviously Axis does not understand the wsrp headres, as it does not
> understand WS-routing standard.
>
>
> Can I somehow tell Axis not to evaluate what's marked as mustUnderstand ?
> Does anyone by any change have implementation for WS-routing ?
> Can anyone explain in short how I would implement WS-routing handler (or
> show a sample of any simple handler) ?
>
> thank you very much.
> -reynir
>
>>
- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFE7yle19KgIQihNwgRApPpAJ98tMmSyNimSMveH31RSnk5H7T/mwCg4v8w
hKDyHltOzXRbSvS0AGvXl/U=
=wPhD
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WS-routing
Posted by Anne Thomas Manes <at...@gmail.com>.
You must be dealing with an old service, because WS-Routing was
superceded by WS-Addressing 3 years ago.
In any case, what you need to do is add a handler to add and process
the wsrp header. (Note that the return message is telling you that you
need to include a WS-Routing header in your input message, so it's not
just a matter of ignoring the header.)
Anne
On 8/24/06, Reynir Hubner <re...@hugsmidjan.is> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
> I am getting the following error when trying to access a remote service
> (that I am not in control of), that uses WS-routing.
>
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}MustUnderstand
> faultSubcode:
> faultString: Did not understand "MustUnderstand" header(s):
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:
> at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:96)
>
> this is because I get this kind of header, with the mustUnderstand flag
> set:
>
> <soap:Header>
> <wsrp:path soap:actor="http://schemas.xmlsoap.org/soap/actor/next"
> soap:mustUnderstand="1" xmlns:wsrp="http://schemas.xmlsoap.org/rp">
> <wsrp:action>http://schemas.xmlsoap.org/soap/fault</wsrp:action>
> <wsrp:id>uuid:9e6d818f-2b6e-4689-9877-9b855f400b27</wsrp:id>
> <wsrp:fault>
> <wsrp:code>701</wsrp:code>
> <wsrp:reason>WS-Routing Header Required</wsrp:reason>
> </wsrp:fault>
> </wsrp:path>
> </soap:Header>
>
> And obviously Axis does not understand the wsrp headres, as it does not
> understand WS-routing standard.
>
>
> Can I somehow tell Axis not to evaluate what's marked as mustUnderstand ?
> Does anyone by any change have implementation for WS-routing ?
> Can anyone explain in short how I would implement WS-routing handler (or
> show a sample of any simple handler) ?
>
> thank you very much.
> - -reynir
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFE7c0219KgIQihNwgRAvkGAKDyPV/qLcudDK1NvHVPCQ384+SZPACfQ7Qd
> JkxY3I7lKfX4B5GVxyEhqug=
> =ViWs
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org