ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rosenberg" <>
Subject Re: Expanding ${} constructs for all attributes
Date Wed, 13 Dec 2000 18:52:33 GMT
Forgive me.  Perhaps at this point I am not yet ready to
participate on ant-dev, and should limit myself to ant-user...

But, I am not clear on what I should look into exactly
based on your suggestions there.  Is this something
I alternately configure with respect to the sax parser
jars I am using?

Where is the ProjectHelper.RootHandler code located,
and are you suggesting that this would be code that I
should modify?  Are you talking about modifying Ant
itself, or are you talking about modifying my use of Ant
on a configuration level?


----- Original Message ----- 
From: "Stefan Bodewig" <>
To: <>
Sent: Wednesday, December 13, 2000 7:31 AM
Subject: Re: Expanding ${} constructs for all attributes

> Jason Rosenberg <> wrote:
> > Can you describe this EntityResolver.  At the very least,
> > I'd like to know if this is something I can use....
> An EntityResolver is responsible for finding an external entity based
> on the public or system ID the user has specified - see the SAX API.
> ProjectHelper.RootHandler implements an EntityResolver that resolves
> relative file:// URLs as being relative to the project's basedir
> instead of the current working directory of the JVM (which is the
> parser's default).
> One could plug property expansion in there, basically by invoking
> replaceProperties on the systemId before using it.
> > In general, it would be good if the entity would just be
> > inserted as CDATA, and then it would parse the inserted
> > data as if it were there initially.
> This is what the parser does, all Ant does is pointing the parser to
> the right file. Ant doesn't know the difference between XML data from
> the original document and data coming from an external entity.
> Stefan

View raw message