Fixed for the 3.3 release. The problem was that parts of the Eclipse infrastructure tolerated uppercase extensions, while TBC did not. This is now better aligned.
Thanks for the report Holger On Dec 30, 2009, at 2:37 PM, Scott Henninger wrote: > Arthur; Yes, there does seem to be an issue here. In the meantime, > just make sure the files are named with lowercase .xml. Sorry for the > inconvenience. > > -- Scott > > On Dec 30, 3:51 pm, Arthur Keen <[email protected]> wrote: >> On OS-X 10.6.2 TBCME 3.2.2 >> >> I tested the Semantic XML on a set of XML data files of the same schema that >> I received from a third party (right click on xml file in project, Open >> With>>TopBraid (Semantic XML Document)). >> TopBraid Semantic XML threw a null pointer exception on the some of the >> files and correctly loaded others, then I noticed that some of the vendor >> files had a '.XML' (uppercase) extension and others had a '.xml' >> (lowercase) extension, and that the null pointer exceptions where being >> thrown on the those with '.XML' (uppercase) extensions. On renaming the >> '.XML' file extension to '.xml' Open WIth TopBraid Semantic XML loads the >> files correctly. I replicated this behavior on XP as well. >> >> regards >> Arthur > > -- > > You received this message because you are subscribed to the Google Groups > "TopBraid Composer Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/topbraid-composer-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en.
