that looks interesting :)
I'm restricted to using features available in our current code base
(+libs) though, so I'm back to investigating this..
I've got as far as registering an EntityResolver on an XMLReader but
with an xml instance document that starts:
<!DOCTYPE QUERYELEMENT SYSTEM '
http://www.happyhacking.com/mydtd.dtd' [
<!ENTITY sqltest_external SYSTEM 'SQL EXPRESSION'>
<!ENTITY sqltest_internal "SQL EXPRESSION">
]>
none of the locally declared entities are reported via the interface -
only the DOCTYPE dtd url is reported.. :(
I don't get why the external entity is not reported - the javadoc for
EntityResolver says "The XML reader will then allow the application to
intercept any external entities (including the external DTD subset and
external parameter entities, if any) before including them" which sounds
like the exact thing that its not doing?
thanks,
Andrew
-----Original Message-----
From: Jochen Wiedmann [mailto:jochen.wiedmann_at_softwareag.com]
Sent: 02 September 2004 07:06
To: users_at_jaxb.dev.java.net
Subject: Re: ENTITY resolving and (separate) problems with Xerces?
Andrew Ferguson wrote:
> I've been asked to investigate the possiblity of using something like
>
> <!ENTITY name "SQL EXPRESSION">
>
> to allow people to have SQL expressions evaluated while the xml is
> being parsed and substituted into appropriate places (which are then
> executed by the application)
Stop investigating, start using Cocoon. See
http://cocoon.apache.org
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net