On Mon, 2002-10-07 at 12:21, [EMAIL PROTECTED] wrote: > This makes sense since the dtd's are tightly coupled to code, so they can > be put in the package hierarchy in a meaningful manner. > I realize there was opportunity to discuss this preceding the call for > vote, but I just returned from vacation today and I still would like to > suggest this as an alternative. As far as i see it, moving the dtd's to the jar is step one of the sollution you describe. I think that the approach you describe an good sollution (altrough i cant overview how to keep it backwards compatible), but i think we should keep the changes maintainable.
- Can you give some pointers to entity-resolvers, how to use them in the situation your describing? - Do you want to change the dtd system identifier? - Do you want to give the working class as a parameter for the resolver? -- Eduard Witteveen Systeem Ontwikkelaar Publieke Omroep, Gateway C Kamer 101 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
