Mailing-List: contact batik-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: batik-dev@xml.apache.org
Received-SPF: pass (hermes.apache.org: domain of Thomas.DeWeese@kodak.com
 designates 192.232.121.200 as permitted sender)
Message-ID: <42193E9C.4080900@Kodak.com>
Date: Sun, 20 Feb 2005 20:51:24 -0500
From: Thomas DeWeese <Thomas.DeWeese@Kodak.com>
Organization: Eastman Kodak Company
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: batik-dev@xml.apache.org
Subject: Re: DOM 3
References: <20050219003245.GA12529@port.mcc.id.au>
 <20050219142936.GA1303@port.mcc.id.au> <4219084C.3070108@Kodak.com>
 <20050221002250.GB22163@port.mcc.id.au>
In-Reply-To: <20050221002250.GB22163@port.mcc.id.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Cameron McCormack wrote:
> Yeah, the strange thing was that I didn't have to change the 'compile'
> target at all.  Just having the DOM 3 interfaces in the classes
> directory allowed me to compile the main sources.

    What are you compiling with? JDK 1.3?  That doesn't have
xml-apis at all (they were added in 1.4 as DOM 2).  In which
case my point about the xalan might still be valid.

>>One thing that occurs to me is that the test build
>>includes the 'libs-build-classpath' - which I think includes
>>xalan - which probably has xml-apis in it (although why they
>>would override your 'bootclasspath' stuff I don't know).
> 
> If I take the extended DOM interfaces approach this should become a
> non-problem.

    If it works as I think it will ;)

---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-dev-help@xml.apache.org