-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, I cannot upgrade the .net service since this is not managed by me or under my control in any way (or even this company).
I have no idea what so ever, which version the .net service is, and I really in general think that the version number should not matter. Do you have such transactions working with any of the versions you mention (WSE 2.0, 3.0 or WCF) ? thanx - [EMAIL PROTECTED] Anne Thomas Manes wrote: > Which version of .NET are you using? WSE 2.0, WSE 3.0, or WCF? > Perhaps you need to upgrade? > > Anne > > On 2/28/06, *Reynir Hubner* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hi, > > I'm trying to create Axis 1.3 client using WS-Addressing and WSS4J with > .NET server. > > My problem is that the WS-Addressing header has the wrong namespace, > it's using the 2004/08 version instead of the 2004/03 version the .NET > service uses. There for .NET service will not find the correct header in > the XML. > > > Does anyone know a good way around this problem ? I found some websites > suggesting it would be possible to change the Constants class of > WS-Addressing, so that the default Namespace would be the 2004/03 > version. > > I think that's pretty much a hack, and I'm not sure if it will work. > > Is it possible to set this some other way ? > > thanx > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEBFQq19KgIQihNwgRArCOAKCoNWjT8z6GREP7YoJ1pky8I/XLsQCbBAGI FFgBfZhvJ3Kdu4sVbYiJYJc= =0PpJ -----END PGP SIGNATURE-----
