> > I remember the origin of the problem, and why the external subset > was not written in the XML by the supplier of the message : > because we then had problems with the real localisation of the > file, in the machine where the app using Xerces runs. > For example, the line for the DTD which was supplied : > <!DOCTYPE OrderProposalRequest SYSTEM "OrderProposalRequest.dtd"> > but the REAL place for the DTD file was in a directory such as > "dtd" and the parse was failing over and over. > > Maybe the solution choiced (to no longer write the DTD line in > the incoming message) was not the good one, indeed. >
We had a very similar problem and solved it by specifying our DTD in the generated document. We then created an EntityResolver that extracts the filename and extension of the specification in the document. If that matches a known DTD, we supply an InputSource that reads from the appropriate DTD. HTH, Evert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
