RE: [Axis 1.4 & WSS4J] - WS-Addressing

[Alick Buckley]

Hi Jose,
 
I have used WS-Addressing and WS-Security with Axis 1.4 as an Agent to talk
to a .NET server.
 
I used WSSJ4 1.5.1, XMLSecurity 1.4 and the addressing-SNAPSHOT.jar from
Sandesha 1.0
 
WS-Addressing is using the 2004/08 namespace and .NET expects the older
2004/03 namespace, so use the following to change it.
stub._setProperty (
org.apache.axis.message.addressing.Constants.ENV_ADDRESSING_NAMESPACE_URI,
org.apache.axis.message.addressing.Constants.NS_URI_ADDRESSING_2004_03 ) ;

The biggest headache is the SOAP message failing the .NET policy checks and
.NET not telling you what it is complaining about.

==========================================================================

 
<deployment name="defaultClientConfig" xmlns="
http://xml.apache.org/axis/wsdd/ <http://xml.apache.org/axis/wsdd/> "
xmlns:java=" http://xml.apache.org/axis/wsdd/providers/java
<http://xml.apache.org/axis/wsdd/providers/java> ">
 
 <globalConfiguration>
   <parameter name="disablePrettyXML" value="true"/>
   <parameter name="addressing.sendReplyTo" value="true"/>
   <parameter name="enableNamespacePrefixOptimization" value="false"/>
 </globalConfiguration>
 
 <service name="XXXXXXPort">
   <requestFlow>
     <handler
type="java:org.apache.axis.message.addressing.handler.AddressingHandler">
       <!-- Reference elements are added in the same order -->
       <parameter name="referencePropertyNames"
 
value="{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}Action;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}MessageID;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}ReplyTo;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}To;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}From"/>
     </handler>
     <handler type="java:org.apache.ws.axis.security.WSDoAllSender">
       <!-- action order is important, do Timestamp then Signature if
signing Timestamp -->
       <parameter name="action" value="Timestamp Signature"/>
       <parameter name="user" value="XXXX"/>
       <parameter name="passwordCallbackClass"
value="com.acme.security.PasswordCallback"/>
       <parameter name="signatureKeyIdentifier" value="DirectReference"/>
       <parameter name="signaturePropFile" value="security.properties"/>
       <parameter name="timeToLive" value="300"/>
       <parameter name="precisionInMilliseconds" value="false" />
       <!-- Reference elements are added in the same order -->
       <parameter name="signatureParts"
 
value="{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}Action;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}MessageID;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}ReplyTo;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}To;
 
{Element}{http://schemas.xmlsoap.org/ws/2004/03/addressing}From;
 
{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity
-utility-1.0.xsd}Timestamp;
 
{Element}{http://schemas.xmlsoap.org/soap/envelope/}Body"/>
     </handler>
   </requestFlow>
 </service>
 
 <transport name="http"
pivot="java:org.apache.axis.transport.http.HTTPSender"/>
 <transport name="java"
pivot="java:org.apache.axis.transport.java.JavaSender"/>
 <transport name="local"
pivot="java:org.apache.axis.transport.local.LocalSender"/>
 
</deployment>

==========================================================================

-----Original Message-----
From: José Ferreiro [mailto:[EMAIL PROTECTED]
Sent: Thursday, 15 February 2007 7:22 AM
To: axis-user@ws.apache.org; wss4j-dev@ws.apache.org
Subject: [Axis 1.4 & WSS4J] - WS-Addressing


Hello,
 
Did someone try to implement WS-addressing using Axis 1.4 and WSS4J?
I am working in a prototype for interoperability ( C#, .net 2.0, and WSE 3.0
).
 
Any coments, suggestions are welcome.
 
Regards

-- 
José Ferreiro
EPFL Communication Systems engineer
ing.sys.com.dipl.EPFL