You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by "Jackson, Douglas" <do...@siemens.com> on 2009/04/14 18:12:38 UTC
Axis2 Addressing producing invalid headers?
Hi!
In the following message coming out of ode, the addressing module appears to be declaring the "addr" prefix in one element and then using it in a sibling. As far as I can tell by looking at the XML standards, that is not valid. The Axis2 service that receives the message also fails saying the "addr" prefix is used and not declared.
I think I can work around it by disabling addressing or using some alternative classpath (TBD). I searched around though and did not see any complaints about this on the web. Has anyone seen this issue?
-Doug.
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header>
<addr:To xmlns:addr="http://www.w3.org/2005/08/addressing">http://localhost:7001/xxx </addr:To>
<addr:Action>getUniqueID</addr:Action>
<addr:ReplyTo>
<addr:Address>http://www.w3.org/2005/08/addressing/anonymous</addr:Address>
</addr:ReplyTo>
<addr:MessageID>uuid:hqejbhcnphr473xlkvaga9</addr:MessageID>
</soapenv:Header>
...
RE: Axis2 Addressing producing invalid headers?
Posted by "Jackson, Douglas" <do...@siemens.com>.
Hi!
When run on tomcat, the addressing stuff looks correct:
<addr:To xmlns:addr="http://www.w3.org/2005/08/addressing">http://</addr:To>
<addr:Action xmlns:addr="http://www.w3.org/2005/08/addressing">g</addr:Action>
<addr:ReplyTo xmlns:addr="http://www.w3.org/2005/08/addressing">
So it is specific to weblogic using OOTB ode without rampart.
-Doug.
-----Original Message-----
From: Alex Boisvert [mailto:boisvert@intalio.com]
Sent: Tuesday, April 14, 2009 5:23 PM
To: user@ode.apache.org
Subject: Re: Axis2 Addressing producing invalid headers?
Are you seeing the same issue on Tomcat or only on Weblogic?
On Tue, Apr 14, 2009 at 3:01 PM, Jackson, Douglas <
douglas.s.jackson@siemens.com> wrote:
>
> Hi!
> I am seeing that issue in Weblogic 10.1 with the Ode 2 beta 2 release.
> I saw something similar when using Rampart previously in another app/web
> server (tomcat maybe) with ode built from trunk and was able to work around
> it by disabling addressing (not sure if on the invoked services or on ode -
> I forget).
> In this instance I am not using rampart - just the ode.war as packaged in
> the download.
> -Doug.
>
> -----Original Message-----
> From: Alex Boisvert [mailto:boisvert@intalio.com]
> Sent: Tuesday, April 14, 2009 3:29 PM
> To: user@ode.apache.org
> Subject: Re: Axis2 Addressing producing invalid headers?
>
> You're right, the message you pasted below is invalid... but I've never
> seen
> this issue. Are you using a stock Ode distribution?
>
> alex
>
>
> On Tue, Apr 14, 2009 at 9:12 AM, Jackson, Douglas <
> douglas.s.jackson@siemens.com> wrote:
>
> > Hi!
> > In the following message coming out of ode, the addressing module appears
> > to be declaring the "addr" prefix in one element and then using it in a
> > sibling. As far as I can tell by looking at the XML standards, that is
> not
> > valid. The Axis2 service that receives the message also fails saying the
> > "addr" prefix is used and not declared.
> > I think I can work around it by disabling addressing or using some
> > alternative classpath (TBD). I searched around though and did not see
> any
> > complaints about this on the web. Has anyone seen this issue?
> > -Doug.
> >
> > <?xml version='1.0' encoding='UTF-8'?>
> > <soapenv:Envelope xmlns:soapenv="
> http://schemas.xmlsoap.org/soap/envelope/
> > ">
> > <soapenv:Header>
> > <addr:To xmlns:addr="http://www.w3.org/2005/08/addressing">
> > http://localhost:7001/xxx </addr:To>
> > <addr:Action>getUniqueID</addr:Action>
> > <addr:ReplyTo>
> > <addr:Address>http://www.w3.org/2005/08/addressing/anonymous
> > </addr:Address>
> > </addr:ReplyTo>
> > <addr:MessageID>uuid:hqejbhcnphr473xlkvaga9</addr:MessageID>
> > </soapenv:Header>
> > ...
> >
> >
> >
> >
> >
>
Re: Axis2 Addressing producing invalid headers?
Posted by Alex Boisvert <bo...@intalio.com>.
Are you seeing the same issue on Tomcat or only on Weblogic?
On Tue, Apr 14, 2009 at 3:01 PM, Jackson, Douglas <
douglas.s.jackson@siemens.com> wrote:
>
> Hi!
> I am seeing that issue in Weblogic 10.1 with the Ode 2 beta 2 release.
> I saw something similar when using Rampart previously in another app/web
> server (tomcat maybe) with ode built from trunk and was able to work around
> it by disabling addressing (not sure if on the invoked services or on ode -
> I forget).
> In this instance I am not using rampart - just the ode.war as packaged in
> the download.
> -Doug.
>
> -----Original Message-----
> From: Alex Boisvert [mailto:boisvert@intalio.com]
> Sent: Tuesday, April 14, 2009 3:29 PM
> To: user@ode.apache.org
> Subject: Re: Axis2 Addressing producing invalid headers?
>
> You're right, the message you pasted below is invalid... but I've never
> seen
> this issue. Are you using a stock Ode distribution?
>
> alex
>
>
> On Tue, Apr 14, 2009 at 9:12 AM, Jackson, Douglas <
> douglas.s.jackson@siemens.com> wrote:
>
> > Hi!
> > In the following message coming out of ode, the addressing module appears
> > to be declaring the "addr" prefix in one element and then using it in a
> > sibling. As far as I can tell by looking at the XML standards, that is
> not
> > valid. The Axis2 service that receives the message also fails saying the
> > "addr" prefix is used and not declared.
> > I think I can work around it by disabling addressing or using some
> > alternative classpath (TBD). I searched around though and did not see
> any
> > complaints about this on the web. Has anyone seen this issue?
> > -Doug.
> >
> > <?xml version='1.0' encoding='UTF-8'?>
> > <soapenv:Envelope xmlns:soapenv="
> http://schemas.xmlsoap.org/soap/envelope/
> > ">
> > <soapenv:Header>
> > <addr:To xmlns:addr="http://www.w3.org/2005/08/addressing">
> > http://localhost:7001/xxx </addr:To>
> > <addr:Action>getUniqueID</addr:Action>
> > <addr:ReplyTo>
> > <addr:Address>http://www.w3.org/2005/08/addressing/anonymous
> > </addr:Address>
> > </addr:ReplyTo>
> > <addr:MessageID>uuid:hqejbhcnphr473xlkvaga9</addr:MessageID>
> > </soapenv:Header>
> > ...
> >
> >
> >
> >
> >
>
RE: Axis2 Addressing producing invalid headers?
Posted by "Jackson, Douglas" <do...@siemens.com>.
Hi!
I am seeing that issue in Weblogic 10.1 with the Ode 2 beta 2 release.
I saw something similar when using Rampart previously in another app/web server (tomcat maybe) with ode built from trunk and was able to work around it by disabling addressing (not sure if on the invoked services or on ode - I forget).
In this instance I am not using rampart - just the ode.war as packaged in the download.
-Doug.
-----Original Message-----
From: Alex Boisvert [mailto:boisvert@intalio.com]
Sent: Tuesday, April 14, 2009 3:29 PM
To: user@ode.apache.org
Subject: Re: Axis2 Addressing producing invalid headers?
You're right, the message you pasted below is invalid... but I've never seen
this issue. Are you using a stock Ode distribution?
alex
On Tue, Apr 14, 2009 at 9:12 AM, Jackson, Douglas <
douglas.s.jackson@siemens.com> wrote:
> Hi!
> In the following message coming out of ode, the addressing module appears
> to be declaring the "addr" prefix in one element and then using it in a
> sibling. As far as I can tell by looking at the XML standards, that is not
> valid. The Axis2 service that receives the message also fails saying the
> "addr" prefix is used and not declared.
> I think I can work around it by disabling addressing or using some
> alternative classpath (TBD). I searched around though and did not see any
> complaints about this on the web. Has anyone seen this issue?
> -Doug.
>
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> ">
> <soapenv:Header>
> <addr:To xmlns:addr="http://www.w3.org/2005/08/addressing">
> http://localhost:7001/xxx </addr:To>
> <addr:Action>getUniqueID</addr:Action>
> <addr:ReplyTo>
> <addr:Address>http://www.w3.org/2005/08/addressing/anonymous
> </addr:Address>
> </addr:ReplyTo>
> <addr:MessageID>uuid:hqejbhcnphr473xlkvaga9</addr:MessageID>
> </soapenv:Header>
> ...
>
>
>
>
>
Re: Axis2 Addressing producing invalid headers?
Posted by Alex Boisvert <bo...@intalio.com>.
You're right, the message you pasted below is invalid... but I've never seen
this issue. Are you using a stock Ode distribution?
alex
On Tue, Apr 14, 2009 at 9:12 AM, Jackson, Douglas <
douglas.s.jackson@siemens.com> wrote:
> Hi!
> In the following message coming out of ode, the addressing module appears
> to be declaring the "addr" prefix in one element and then using it in a
> sibling. As far as I can tell by looking at the XML standards, that is not
> valid. The Axis2 service that receives the message also fails saying the
> "addr" prefix is used and not declared.
> I think I can work around it by disabling addressing or using some
> alternative classpath (TBD). I searched around though and did not see any
> complaints about this on the web. Has anyone seen this issue?
> -Doug.
>
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
> ">
> <soapenv:Header>
> <addr:To xmlns:addr="http://www.w3.org/2005/08/addressing">
> http://localhost:7001/xxx </addr:To>
> <addr:Action>getUniqueID</addr:Action>
> <addr:ReplyTo>
> <addr:Address>http://www.w3.org/2005/08/addressing/anonymous
> </addr:Address>
> </addr:ReplyTo>
> <addr:MessageID>uuid:hqejbhcnphr473xlkvaga9</addr:MessageID>
> </soapenv:Header>
> ...
>
>
>
>
>