You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@santuario.apache.org by Greg Pagendam-Turner <gr...@liftyourgame.com> on 2011/08/31 00:51:35 UTC
XMLSEC 2.0
Hi,
I'm hoping you can help me. We are having a problem with
canonicalisation in our Java application. It appears to be mangling
unicode characters in a UTF-8 when run on a Windows PC using it's
default charset of cp1252.
We have XMLSEC in our Java endorsed directory.
When we call the canonicalisation transform:
Transform transform = XML_SIGNATURE_FACTORY.newTransform(
CanonicalizationMethod.EXCLUSIVE, (TransformParameterSpec) null);
It seems to trigger some reserialisation of the XML document using the
default charset instead of using the charset defined for the XML
document to be signed.
Regards,
Greg.
Re: XMLSEC 2.0
Posted by Colm O hEigeartaigh <co...@apache.org>.
I fixed some bugs relating to this in the 1.4.5 release - could you
try using this and see if it works?
Colm.
On Tue, Aug 30, 2011 at 11:51 PM, Greg Pagendam-Turner
<gr...@liftyourgame.com> wrote:
> Hi,
>
> I'm hoping you can help me. We are having a problem with canonicalisation in
> our Java application. It appears to be mangling unicode characters in a
> UTF-8 when run on a Windows PC using it's default charset of cp1252.
>
> We have XMLSEC in our Java endorsed directory.
>
> When we call the canonicalisation transform:
> Transform transform = XML_SIGNATURE_FACTORY.newTransform(
> CanonicalizationMethod.EXCLUSIVE, (TransformParameterSpec) null);
>
> It seems to trigger some reserialisation of the XML document using the
> default charset instead of using the charset defined for the XML document to
> be signed.
>
> Regards,
>
> Greg.
>
>
--
Colm O hEigeartaigh
http://coheigea.blogspot.com/
Talend - http://www.talend.com
Re: XMLSEC 2.0
Posted by "Cantor, Scott" <ca...@osu.edu>.
On 8/30/11 6:51 PM, "Greg Pagendam-Turner" <gr...@liftyourgame.com> wrote:
>
>It seems to trigger some reserialisation of the XML document using the
>default charset instead of using the charset defined for the XML
>document to be signed.
C14N results in XML serialization into UTF-8, period, that's part of the
specification(s). What it starts as is up to the XML DOM being processed,
but the resulting octets are UTF-8.
-- Scott