k to a servlet which will try to sign it.
But we are unable to find any problems, i.e, the signatures created with both
1.4.1 and 1.4.0 are the same.
Could anyone give us some indication?
Regards,
Rafael
at testing.TestXMLSig.main(TestXMLSig.java:246)
==
Quia natura mutari non potest idcirco
verae amicitiae sempiternae sunt - (Horace)
RAFAEL J. DEITOS
Automação - UFSC - Florianópolis - SC - Brazil
http://www.das.ufsc.br/~deitos
==
ovides anything else???
==
Quia natura mutari non potest idcirco
verae amicitiae sempiternae sunt - (Horace)
RAFAEL J. DEITOS
Automação - UFSC - Florianópolis - SC
http://www.das.ufsc.br/~deitos
==
iae sempiternae sunt - (Horace)
RAFAEL J. DEITOS
Automação - UFSC - Florianópolis - SC
http://www.das.ufsc.br/~deitos
==
> So I think what you were doing in your original commented out code was
> correct.
Great!
Thanks a lot to all of you guys!
Regards,
-R
>
> All in All it seems is easier if you put all namespace definitions you
> need in the signature element.
>
> Regards,
>
> Raul
>
The problem is that it isn't either a good solution as, that way, we can't
develop an automatic process for arbitrary xml documents.
Regards,
-R
Berin Lautenbach wingsofhermes.org> writes:
>
> Rafael wrote:
>
> > I have been examining the source code around the 'Transforms' implementation
and
> > it seems like only ns declarations in the context node(s) are used. That
would
> > mean that o
What version of the xml-sec-library are
> you using?
> ItÂs the 1.1 or the CVS HEAD one?
>
> Raul
I am using 1_1_0 (april 2004).
The problem is easy to reproduce with the code at my first mail and with a
"intersect" with value "//bla:ToBeSigned".
You get:
org.apache.xml.security.transforms.Tra
> Yes, it does, but I'm guessing (but could be wrong) the canonicalizer may be
> stripping your prefix definition out because it isn't used within the
> Signature element outside of the Qname in the element value. The solution to
> that is the element parameter inside the to
> force the inclusion
Hi,
What I actually wanted to know was whether the XMLSec implementation of
Transforms in general and Filter2 in particular, by default, supports locating
elements that have a namespace prefix.
If not, am I supposed to provide the prefix mappings myself to a container like
XPath2FilterContainer
Hi!
I am currently working with Filter2 transforms and XPath transforms. And I have
problems when namespace prefixes are used in some element that is present in a
filter2-xpath value.
I provide the code that I am using to calculate transformation output at the end
of the mail.
Example: suppos
11 matches
Mail list logo