Kees Jongenburger <[EMAIL PROTECTED]> wrote: > I mean that probabely why there are SaxInputSources and such so that a stream still > knows where it comes from. > > java.lang.RuntimeException: error loading configfile > 'D:\Tomcat\webapps\mmbase.net\WEB-INF\config\databases\lookup.xml' > java.net.UnknownHostException: D > > or is this an other problem? > (D of course is not a protocol but a windows "disk")
That semicolon-notation of windows is indeed a source of eternal trouble. But I doubt if it is related to this. I think you can always give 'relative' SYSTEM id's for entities. So, if the including file's URI can be resolved, also the included file's URI should be resolvable withouth too much trouble. IIRC Resin complains that the included entity should be precisely one xml-entry (so it indeed seems to want that it be valid XML, which IMHO is silly because you cannot specify DOCTYPE, and can also specify complety other things in an entity (much used for 1 character and so on)). So, I don't know if it is right in this complaint, but I do know that my usual parser does not complain abou tit.. (xerces). Michiel -- mihxil' Michiel Meeuwissen Mediapark C101 Hilversum +31 (0)35 6772979 []()
