>> I've got no idea what is going on here... but it sure aint in Jmol's CML >> handler... > > Mmm.... still a bad XML parser... but it *is* a CML handler bug :(
Really? > After about 15 semi-randomly changing the CML file source, I traced it > down to a bug in the handler... > But, I think the parser *could* do with some better error handling! I have been looking at the Parser2 source code. In the process of throwing an exception they are using a variable called 'locator'. It looks like to me that variable is null. Locator is a DocLocator. So ... what was the bug in the CML Handler? Miguel ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Jmol-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-developers
