This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

Eclipse 3.5 + STS Bundle Classpath Container

Feb 11th, 2010, 09:43 AM

I ran into issues with an Eclipse 3.5 SpringDM project where the Bundle Dependencies were not being resolved. Eclipse error log indicated a problem with "Provider com.bea.xml.stream.XMLOutputFactoryBase not found". Thinking maybe my environment was to blame I decided to load a new instance of Eclipse 3.5 and following the e3.5+STS install procedures located on the SpringSource blog I was able to *finally* get STS plugin to install in e3.5. Note this required updating mylyn via the nightly build site instead of the normal mylyn, mylyn extras sites.

When I again tried to create a very simple SpringDM based project using this fresh e3.5+STS install the Bundle Dependencies still do not resolve. When I try to SpringTools->Refresh Bundle Classpath Container I receive the XMLOutputFactoryBase related exception. <bangs head>

From what I've gathered, the com.bea....XMLOutputFactoryBase is the default impl so it seems the desired provider is not being loaded. Any help would be greatly appreciated. Below you will find the stacktrace and details of my e3.5 install.