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 Ted Jones <Tj...@metamatrix.com> on 2007/08/23 22:49:22 UTC
[Axis2] WS-Addressing version on server
I am testing a .Net client with WSE 3.0 for compatibility with an Axis2
1.2 deployed web service. I have the addressing enabled and engaged on
the server along with Rampart. WSE 3.0 only supports the submission
version of WS-Addressing while Axis2 defaults to the final version (I
believe). Is there a way in the Axis2 server to tell it to use the
submission version (perhaps in the service.xml as a parameter to the
moduleConfig)?
If not, is there another way of having the client indicating to the
server which version to use other than the Options object?
Thanks,
Ted
RE: [Axis2] WS-Addressing version on server
Posted by "Drooker, Matthew" <Ma...@Turner.com>.
unsubscribe
From: Ted Jones [mailto:Tjones@metamatrix.com]
Sent: Friday, August 24, 2007 4:53 PM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] WS-Addressing version on server
Is anyone using WS-Addressing with Axis2 web services and a .Net client?
________________________________
From: Ted Jones [mailto:Tjones@metamatrix.com]
Sent: Thursday, August 23, 2007 3:49 PM
To: axis-user@ws.apache.org
Subject: [Axis2] WS-Addressing version on server
I am testing a .Net client with WSE 3.0 for compatibility with an Axis2
1.2 deployed web service. I have the addressing enabled and engaged on
the server along with Rampart. WSE 3.0 only supports the submission
version of WS-Addressing while Axis2 defaults to the final version (I
believe). Is there a way in the Axis2 server to tell it to use the
submission version (perhaps in the service.xml as a parameter to the
moduleConfig)?
If not, is there another way of having the client indicating to the
server which version to use other than the Options object?
Thanks,
Ted
RE: [Axis2] WS-Addressing version on server
Posted by Ted Jones <Tj...@metamatrix.com>.
Thanks for the reply Anthony. My use case is the actually the reverse:
Axis2 Server with a .NET WSE 3 client.
Is there some way to configure the WS-Addressing namespace version to be the older version in the Axis2 server?
Thanks,
Ted
-----Original Message-----
From: Anthony Bull [mailto:anthony.bull@bcsoft.co.nz]
Sent: Sun 8/26/2007 4:31 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2] WS-Addressing version on server
I am - I've done three different interop projects with .NET WSE 3
clients and servers.
I use the options object to tell my client to use the older namespace
(see below) when sending to .NET servers, but you wanted a different way
of achieving it?
options.setProperty(org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION,
org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE);
anthony.
Ted Jones wrote:
> Is anyone using WS-Addressing with Axis2 web services and a .Net client?
>
> ------------------------------------------------------------------------
> *From:* Ted Jones [mailto:Tjones@metamatrix.com]
> *Sent:* Thursday, August 23, 2007 3:49 PM
> *To:* axis-user@ws.apache.org
> *Subject:* [Axis2] WS-Addressing version on server
>
> I am testing a .Net client with WSE 3.0 for compatibility with
> an Axis2 1.2 deployed web service. I have the addressing enabled and
> engaged on the server along with Rampart. WSE 3.0 only supports the
> submission version of WS-Addressing while Axis2 defaults to the final
> version (I believe). Is there a way in the Axis2 server to tell it to
> use the submission version (perhaps in the service.xml as a parameter
> to the moduleConfig)?
>
> If not, is there another way of having the client indicating to the
> server which version to use other than the Options object?
>
> Thanks,
> Ted
--
Anthony
-------------------------------------
Anthony Bull
Senior Developer
Black Coffee Software Ltd
PO Box 10-192 The Terrace
Wellington, New Zealand
anthony.bull@bcsoft.co.nz
Ph +64 4 472 8818
Fax +64 4 472 8811
Mobile 021 303 692
-------------------------------------
www.bcsoft.co.nz
---------------------------------------------------------------
This email may contain confidential or privileged information,
and is intended for use only by the addressee, or addressees.
If you are not the intended recipient please advise the sender
immediately and do not copy, use or disclose the contents to
any other person or organisation.
Black Coffee Software Ltd accepts no responsibility for viruses
received with this email, or to any changes made to the original
content. Any views or opinions expressed in this email may be
personal to the sender and are not necessarily those of Black
Coffee Software Ltd.
---------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2] WS-Addressing version on server
Posted by Anthony Bull <an...@bcsoft.co.nz>.
I am - I've done three different interop projects with .NET WSE 3
clients and servers.
I use the options object to tell my client to use the older namespace
(see below) when sending to .NET servers, but you wanted a different way
of achieving it?
options.setProperty(org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION,
org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE);
anthony.
Ted Jones wrote:
> Is anyone using WS-Addressing with Axis2 web services and a .Net client?
>
> ------------------------------------------------------------------------
> *From:* Ted Jones [mailto:Tjones@metamatrix.com]
> *Sent:* Thursday, August 23, 2007 3:49 PM
> *To:* axis-user@ws.apache.org
> *Subject:* [Axis2] WS-Addressing version on server
>
> I am testing a .Net client with WSE 3.0 for compatibility with
> an Axis2 1.2 deployed web service. I have the addressing enabled and
> engaged on the server along with Rampart. WSE 3.0 only supports the
> submission version of WS-Addressing while Axis2 defaults to the final
> version (I believe). Is there a way in the Axis2 server to tell it to
> use the submission version (perhaps in the service.xml as a parameter
> to the moduleConfig)?
>
> If not, is there another way of having the client indicating to the
> server which version to use other than the Options object?
>
> Thanks,
> Ted
--
Anthony
-------------------------------------
Anthony Bull
Senior Developer
Black Coffee Software Ltd
PO Box 10-192 The Terrace
Wellington, New Zealand
anthony.bull@bcsoft.co.nz
Ph +64 4 472 8818
Fax +64 4 472 8811
Mobile 021 303 692
-------------------------------------
www.bcsoft.co.nz
---------------------------------------------------------------
This email may contain confidential or privileged information,
and is intended for use only by the addressee, or addressees.
If you are not the intended recipient please advise the sender
immediately and do not copy, use or disclose the contents to
any other person or organisation.
Black Coffee Software Ltd accepts no responsibility for viruses
received with this email, or to any changes made to the original
content. Any views or opinions expressed in this email may be
personal to the sender and are not necessarily those of Black
Coffee Software Ltd.
---------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: [Axis2] WS-Addressing version on server
Posted by Ted Jones <Tj...@metamatrix.com>.
Is anyone using WS-Addressing with Axis2 web services and a .Net client?
________________________________
From: Ted Jones [mailto:Tjones@metamatrix.com]
Sent: Thursday, August 23, 2007 3:49 PM
To: axis-user@ws.apache.org
Subject: [Axis2] WS-Addressing version on server
I am testing a .Net client with WSE 3.0 for compatibility with an Axis2
1.2 deployed web service. I have the addressing enabled and engaged on
the server along with Rampart. WSE 3.0 only supports the submission
version of WS-Addressing while Axis2 defaults to the final version (I
believe). Is there a way in the Axis2 server to tell it to use the
submission version (perhaps in the service.xml as a parameter to the
moduleConfig)?
If not, is there another way of having the client indicating to the
server which version to use other than the Options object?
Thanks,
Ted