Hi Berin,

I was thinking that .NET interoperability arises only because of cascading.
Has some one succeeded in this effort? Please enlighten me.

.NET (client) -----> XML sec (signature verification)

Your help is much appreciated.

Thanks & Regards,
Ayyappan Gandhirajan
---------------------------------------------
Office: 91.80.2225.1554 Extn 1472
Mobile: 91.94483.14969
E-Mail: [EMAIL PROTECTED]
-----------------------------------------------


-----Original Message-----
From: Berin Lautenbach [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 27, 2004 3:01 PM
To: [EMAIL PROTECTED]
Subject: Re: From XML Sec to WSS4J????


GANDHIRAJAN,AYYAPPAN (HP-India,ex2) wrote:
> I have been using xml sec for signature verification in my application. As
> long as Axis clients are used for sigining the XML, the signature
> verification is succeeded. But it has interoperability issue when .NET is
> used for generating signed XML. I learnt that verification is failed due
to
> namespace cascading.

?? Namespace cascading won't (shouldn't) cause a signature validation 
failure.

Cheers,
        Berin

Reply via email to