WSS4J Interoperability

[Rami Jaamour <rj...@parasoft.com>]

Hello,

It appears that in the last few weeks there were a couple of changes 
that have caused WSS4J not to interoperate with itself anymore, namely 
the ValueType and EncodingType in the BinarySecurityToken. How is WSS4J 
entering into beta stage going to affect its stability as far as interop 
with its previous builds and other WS providers?

I might have missed it here, but I wonder if you can summarize what is 
known about the interoperability status of the current WSS4J with major 
WS providers like .NET, IBM, BEA, GLUE, etc. I found that at least .NET 
-> WSS4J was mentioned on the list here, right? Or is it a matter of 
others catching up with OASIS to reach interop? I am trying to get the 
big picture as far as latest OASIS Vs. current w3c WS-Security specs and 
who conforms to what and why.

Thank you,

Rami Jaamour
Software Engineer
SOAPtest <http://www.parasoft.com/jsp/products/home.jsp?product=SOAP> 
Development
Parasoft Corporation <http://www.parasoft.com>


Davanum Srinivas wrote:

>Werner,
>
>Can you please update build.xml with targets for binaries and source distribution ZIP/tars? Let's
>see if we can do a beta soon-ish. (since Axis 1.2 is now in Beta)
>
>-- dims
>
>=====
>Davanum Srinivas - http://webservices.apache.org/~dims/
>
>  
>