Hi, I'm also having interoperability problems with JBossWS and WSE 3.0.
I call a JBossWS helloWorld service using a .Net WSE 3 client and it simple does not work with ws-encryption.
I tried every possible configuration on the .Net client.
Signing only the message, however, the server processes the message correctly and returns the SOAP response to the client.
The .Net client then throws an exception while processing the response: "An unsupported signature or encryption algorithm was used".
Did anyone try using ws-encryption (encrypting and/or signing messages) with .Net WSE 3.0 and JBossWS (jboss-4.0.5.GA)?
I'm afraid that I don't get this fixed I'm gonna have to transfer our complete system to another application server or throw the complete ws-security stack of jboss overboard and implement the security handler myself from scratch tailored to what the .Net client is sending out.
Currently the dev team is busy with JAXWS JEE5 certification. This type of interop issue will be addressed as part of the regular MSFT interop workshops.
If cost is a concern to your organization, then profsupport might be a valid option.