Mailing-List: contact java-user-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@axis.apache.org
Received-SPF: pass (nike.apache.org: domain of futhark77@gmail.com designates
 209.85.213.45 as permitted sender)
MIME-Version: 1.0
Date: Mon, 2 Apr 2012 12:38:06 -0400
Message-ID: 
 <CAB5i=YpJnPiBSg0VSoLpAofzfAS6Crq4ebfhO8oxpwi7_UZPCQ@mail.gmail.com>
Subject: Re: [axis2 or rampart?] client not including username and password in
 header
From: "Philippe A." <futhark77@gmail.com>
To: java-user@axis.apache.org
Content-Type: multipart/alternative; boundary=20cf305639719cdf8404bcb4d097

--20cf305639719cdf8404bcb4d097
Content-Type: text/plain; charset=ISO-8859-1

Sorry for the missing subject. I posted in a hurry.

2012/4/2 Philippe A. <futhark77@gmail.com>

> Hello,
>
> I have compiled Axis2 & rampart from trunk in order to workaround a bug
> with wsdl2java. The client I developed back with Axis 1.4.1 no longer
> works. More specifically, the username and password token does not get
> added by the client in the soap header (confirmed with tcpdump). Client
> requests are rejected by the server with "org.apache.axis2.AxisFault: SOAP
> header missing".
>
> I also see the following in my server logs (not sure if it is related or
> not):
> [WARN] Deprecated usage of OMElement#declareNamespace(String,String) with
> empty prefix
>
> My client is generated by wsdl2java and I wrote a simple wrapper class
> around it. The wrapper closely matches this example:
> http://blog.facilelogin.com/2008/11/security-policy-with-rampart.html
>
> I invoke wsdl2java with the following options: -s -uw.
>
> Debug traces show that rampart is being loaded by the client. I am not
> using any other security for now (encryption or other). I am using
> standalone axis server and I am in the process of replacing https transport
> security for ws-security encryption.
>
> All ideas welcome. Thank you!
>

--20cf305639719cdf8404bcb4d097
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Sorry for the missing subject. I posted in a hurry.<br><br><div class=3D"gm=
ail_quote">2012/4/2 Philippe A. <span dir=3D"ltr">&lt;<a href=3D"mailto:fut=
hark77@gmail.com">futhark77@gmail.com</a>&gt;</span><br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
Hello,<br><br>I have compiled Axis2 &amp; rampart from trunk in order to wo=
rkaround a bug with wsdl2java. The client I developed back with Axis 1.4.1 =
no longer works. More specifically, the username and password token does no=
t get added by the client in the soap header (confirmed with tcpdump). Clie=
nt requests are rejected by the server with &quot;org.apache.axis2.AxisFaul=
t: SOAP header missing&quot;. <br>

<br>I also see the following in my server logs (not sure if it is related o=
r not):<br>[WARN] Deprecated usage of OMElement#declareNamespace(String,Str=
ing) with empty prefix<br><br>My client is generated by wsdl2java and I wro=
te a simple wrapper class around it. The wrapper closely matches this examp=
le:<br>

<a href=3D"http://blog.facilelogin.com/2008/11/security-policy-with-rampart=
.html" target=3D"_blank">http://blog.facilelogin.com/2008/11/security-polic=
y-with-rampart.html</a><br><br>I invoke wsdl2java with the following option=
s: -s -uw. <br>
<br>
Debug traces show that rampart is being loaded by the client. I am not usin=
g any other security for now (encryption or other). I am using standalone a=
xis server and I am in the process of replacing https transport security fo=
r ws-security encryption.<br>

<br>All ideas welcome. Thank you!<br>
</blockquote></div><br>

--20cf305639719cdf8404bcb4d097--