Done. Thank you sir!.
-- dims
On 11/6/06, Sean Mullan <[EMAIL PROTECTED]> wrote:
Davanum Srinivas wrote:
> Raul, Sean,
>
> Looks like the prev patch from me for parseFragment does not really
> help much :( As XMLCipher has a private constructor and the
> parseFragment is in a private class Seri
Davanum Srinivas wrote:
Raul, Sean,
Looks like the prev patch from me for parseFragment does not really
help much :( As XMLCipher has a private constructor and the
parseFragment is in a private class Serializer inside that class. So
we are back to square one...
Can you first back out your fix
Hi Raul,
thanks a lot for the quick fix !
Thanks,
Ruchith
On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote:
On 11/5/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
> Hi Raul,
>
> On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote:
> > You Wss4j guy always using untested XMLSignature constructo
On 11/5/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
Hi Raul,
On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote:
> You Wss4j guy always using untested XMLSignature constructors!!! ;)
> Just joking. You hit again another XMLSignature constructor that there
> is no unit test for it.
> The probl
> Can you raise a bug report in bugzilla, for proper tracking?
will do.
Done :
http://issues.apache.org/bugzilla/show_bug.cgi?id=40896
Thanks,
Ruchith
--
www.ruchith.org
Hi Raul,
On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote:
You Wss4j guy always using untested XMLSignature constructors!!! ;)
Just joking. You hit again another XMLSignature constructor that there
is no unit test for it.
The problem is that for creating new Signatures(for signing)
public XMLS
Raul, Sean,
Looks like the prev patch from me for parseFragment does not really
help much :( As XMLCipher has a private constructor and the
parseFragment is in a private class Serializer inside that class. So
we are back to square one...
How about we cut a branch so that we don't disturb the rel
You Wss4j guy always using untested XMLSignature constructors!!! ;)
Just joking. You hit again another XMLSignature constructor that there
is no unit test for it.
The problem is that for creating new Signatures(for signing)
public XMLSignature( Document doc, String BaseURI,
Element Signat
Hi Raul,
I was able to reproduce the issue.
Please drop the attached interop.jks file to your classpath along with
xml-sec and other pre-reqs and run the test case (TestSig.java). I ran
this inside my IDE within the xml-security project.
The exception stack trace is here :
http://rafb.net/paste
Can you also post the exception backtrace?
Regards,
On 11/3/06, Raul Benito <[EMAIL PROTECTED]> wrote:
Hi Ruchith,
It is not feasible for me to checkout the whole wss4j in order to see
the problem.
Did the problem arise when you do something like this?
PrivateKey xk; PublicKey pk=xk.getPublickK
Hi Ruchith,
It is not feasible for me to checkout the whole wss4j in order to see
the problem.
Did the problem arise when you do something like this?
PrivateKey xk; PublicKey pk=xk.getPublickKey();
XMLSignature s1=...;
XMLSignature s2=...;
s1.sign(xk);
s2.sign(xk);
s1.checkSignatureValue(pk);
Or
Hi Raul,
I'm using the SVN head (revision : 470741).
I'm working on fixing the issue dims reported yesterday[1] and fixing
WSS4J/Rampart and AXIOM to work with the changes :-). And I have a
patch for [1] which I will post soon.
I will try to send a test case as soon as I possible,
Until then y
Hi Ruchith,
It looks strange to me, because all the junits that we pass do in
essence what are you describing(several verifying in one thread). But
on the other hand your explanation looks sound.
What version of xmlsec are you using?
Can you post a simple test case that triggers this error?
Rega
13 matches
Mail list logo
