Miroslav Nachev wrote:
> Dear Sean and Lijun,
>
> I try the suggested ideas using Transforms in Reference without
> successful results.
> Ricardo which is member of our XAdES Open Source project
> (http://xades.dev.java.net/) solve the problem when do XMLSignature
> without using of namespace pref
Dear Sean and Lijun,
I try the suggested ideas using Transforms in Reference without
successful results.
Ricardo which is member of our XAdES Open Source project
(http://xades.dev.java.net/) solve the problem when do XMLSignature
without using of namespace prefixes.
I am not so familiar with t
Miroslav Nachev wrote:
Do you know which class in JDK6 is the equivalent of **
"org.apache.xml.security.transforms.Transforms"?**
The JSR 105 API (which is in JDK 6 and is now also a part of XMLSec 1.4)
uses a java.util.List to hold Transform objects. You just need to pass
this List as a para
Dear Sean,
Because after writing the Document to the file using
"XMLUtils.outputDOMc14nWithComments(node, outStream)",
the document structure is correct. Is it possible to use some kind of
transformations/canonicalization to have the same correct structure
before to sign the data?
Best Re
Miroslav Nachev wrote:
Dear Sean,
Why during validation JSR 105 takes "xmlns:xsd" attribute in case that
this attribute is not set explicit to this element? This attribute is
set explicit to the parent of this element. And why this is not happen
during signing?
It could be a bug, but I can'
I'm sorry but I don't have the time to debug your problem. However,
looking at the log file, the validation failure occurs because of this:
> FINER: Pre-digested input:
> 2007-2-1 17:36:19 org.jcp.xml.dsig.internal.DigesterOutputStream write
> FINER: xmlns:dsig="http://www.w3.org/2000/09/xmldsig
Dear Sean,
Please find the attached log file. The problem reference is
"L1.S1-SignedProperties".
Do you have any suggestions how to solve this problem/bug?
Best Regards,
Miroslav Nachev
Sean Mullan wrote:
Miroslav Nachev wrote:
I will try your suggestions tomorrow, but I am not sure that t
It is very interesting how is solved this problem in the other XAdES
realizations? Maybe they use another XML Security library like BouncyCastle?
Are there some plans for JDK and Apache XML Security to provide all kind of
functionality which exists in BouncyCastle and similar libraries?
In this w
For XML Signature I use JDK6. For XML Encription I use Apache XML Security
1.4. If this will solve my problem I will use Apache XML Security for both.
On 1/31/07, Sean Mullan <[EMAIL PROTECTED]> wrote:
Miroslav Nachev wrote:
> I will try your suggestions tomorrow, but I am not sure that this i
Miroslav Nachev wrote:
I will try your suggestions tomorrow, but I am not sure that this is the
problem. Before to quit from the office I found that the digest value
for this reference is different calculated for Signing and Validation.
The stack trace from Exception is missing because any exc
I will try your suggestions tomorrow, but I am not sure that this is the
problem. Before to quit from the office I found that the digest value for
this reference is different calculated for Signing and Validation.
The stack trace from Exception is missing because any exception is not
thrown. The
Miroslav Nachev wrote:
Hi,
I need of help to find where is my mistake during signing process.
The case is:
I would like to sign some element which is part of "This element is located in "" as sub-element named
. During signing
process everything is OK, but when I try to verify the signature, t
12 matches
Mail list logo
