her inefficient as the
> same DTD is used and one instance of entity resolver implementation
> is sufficient IMHO. Is this a feature or a bug?
You can use the same instance of your EntityResolver but it
sounds like you're caching the same instance of the returned
InputSource. Is this
ed
and one instance of entity resolver implementation is sufficient IMHO.
Is this a feature or a bug?
Bear in mind, that I don't construct the InputSource via a call
InputSource src = new InputSource(sysId);
but instead with the given routine, that equals a call to
InputSource src = new InputSource(InputStream(sysId));
src.setSystemId(sysId);
since I had to overcome the situation where the spe
Valley
[EMAIL PROTECTED]
"Armin Pfarr" <[EMAIL PROTECTED]> on 02/18/2000 02:14:19 PM
Please respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: Entity-Resolver
Hi,
I'm trying to implement an entity-resolver using Xerces 1.0.1. The routin
Hi,
I'm trying to implement an entity-resolver using Xerces 1.0.1. The routine
work fine if I use public identifiers for ALL entities and redirect ALL
calls through the Entity-resolver.
Now I have a DTD, whose location is resolved through a public identifier.
That DTD includes external ent
