Mailing-List: contact security-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: security-dev@xml.apache.org
Received-SPF: pass (asf.osuosl.org: domain of mikemci@us.ibm.com designates
 32.97.182.142 as permitted sender)
In-Reply-To: <449FEA9B.3020309@Sun.COM>
To: security-dev@xml.apache.org
Cc: Sean.Mullan@Sun.COM, security-dev@xml.apache.org
Subject: Re: CanonicalizerSpi
MIME-Version: 1.0
From: Michael McIntosh <mikemci@us.ibm.com>
Message-ID: 
 <OF5F62EEB7.218E74FD-ON85257199.004FCCEC-85257199.0050ACD9@us.ibm.com>
Date: Mon, 26 Jun 2006 10:41:51 -0400
Content-Type: text/plain; charset="US-ASCII"

Sean.Mullan@Sun.COM wrote on 06/26/2006 10:09:31 AM:

> Can you be more specific about what the problem is?

The problem is that there is no equivalent to _transformObject in the 
CanonicalizerSpi. An implementation of a Transform can include the 
following code in order to access any parameter values encapsulated in the 
Transform element:

protected XMLSignatureInput enginePerformTransform
        (XMLSignatureInput input)
{
        org.w3c.dom.Element elemTransform = 
this._transformObject.getElement();
        ...
}

there is no way to access the current CanonicalizationMethod element from 
within the implementation.

> Also, the next release of Apache XML Security (1.4) will include JSR 105 

> (Java XML DSig API). The JSR 105 API allows you to implement your own 
> Canonicalization (or Transform) algorithms (with support for input 
> parameters) by subclassing the javax.xml.crypto.dsig.TransformService 
> class. An initial beta of XMLSec 1.4 is now available for testing: 
> http://xml.apache.org/security/dist/java-library/xmlsec-1.4.Beta0.jar

How different is code written for 1.4 vs. 1.3? Are there easy to 
understand porting guidelines available?

Thanks,
Mike

> --Sean