XOM API for Processing XML with Java

[Wolfgang Hoschek <whoschek AT lbl.gov>]

On Jan 6, 2005, at 2:59 PM, Elliotte Harold wrote:

> John Cowan wrote:
>
> > A better tactic, I think, is to add a method 
> > getSealedInternalDTDSubset()
> > which returns a SealedInternalDTDSubset.  This is a trivial class with
> > no public constructor and only toString, hashCode, and equals methods.
> > Then setSealedInternalDTDSubset(SealedInternalDTDSubset s) can be
> > made public.
>
>
> I don't think this solves Wolfgang's problem. He's got an internal DTD 
> subset stored off in a non-XML format and he needs to get it into XOM. 
> He can't just parse it through the Builder because it may point to 
> unavailable files. Am I missing something? Is there a way he could use 
> SealedInternalDTDSubset?
>
> Currently for some uses you can create a Document with your internal 
> DTD subset in a String, build a Document from that, and then detach or 
> clone the DocType you get there to put it in a new document. The 
> problem is this doesn't quite work when the entities point at 
> unavailable URIs.

Right :-(

Wolfgang.