Totally agree, but even if originating XML is corrected, there are clients with wrong style XML that will use my application to import XML and in such a case there is little I can do. So, is there a way to correct this problem during the import?
Thanks for your help, Alex On Mon, Mar 2, 2009 at 12:21 PM, <kesh...@us.ibm.com> wrote: > The purpose of an XML parser is to read correct XML. Get whoever's > generating that file to produce XML that expresses their intent correctly, > or throw in a filtering stage that corrects their error. Personally, I > would apply a clue-by-four to the author of whatever's generating that > document rather than trying to tolerate it, since they're just going to > get themselves in deeper trouble later... but I understand that this isn't > always possible. > > "The customer isn't always right. Unfortunately, the customer is always > the one with the money." > > ______________________________________ > "... Three things see no end: A loop with exit code done wrong, > A semaphore untested, And the change that comes along. ..." > -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish ( > http://www.ovff.org/pegasus/songs/threes-rev-11.html) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org > For additional commands, e-mail: j-users-h...@xerces.apache.org > >
