|
From: Rob M. <Rob...@pe...> - 2004-04-19 15:45:49
|
Hi, Torsten, Thanks for looking into this. I'm unable to determine where the XMLParserConfiguration is being set. It is not in the command line (as you suggested). I'm thinking that another plug-in may be setting it (I'm using a trial of oXygen xml editor, so perhaps that's the culprit. Rob Torsten Juergeleit wrote: > Rob, > > in your system summary the JVM system property > "org.apache.xerces.xni.parser.XMLParserConfiguration" > is defined. This property overrides the same property > defined in xercesImpl.jar (META-INF/services/) which > references the (correct) class > "org.apache.xerces.parsers.StandardParserConfiguration". > The class referenced in your (manually set) system > property references the class > "org.apache.xerces.parsers.XIncludeParserConfiguration" > which is not available in Eclipse's Xerces > implementation. > > I have successfully reproduced your error by adding > this invalid system property to the launch > configuration of an Eclipse workbench (first tab "(x) > Arguments", input field "VM Arguments"). > > > You have to get rid of this invalid system property > (listed in Eclipse's system summary) to run Spring IDE > Beans UI. Maybe it's defined in your Eclipse shortcut > on the windows desktop (as commandline parameter > "-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration". > > Cheers, > Torsten |