Clearly Baz is a class. Strangely, if I move my spring config to the WEB-INF directory and set it up to be loaded by the servlet loader (using the web.xml stuff), the class is found and things come up just fine -- which leads me to believe the MANIFEST is correct and the actual class is getting included.
Why can't I initialize this class in the spring/ folder?
Supposing I can eventually initialize that bean with a config in the spring/ folder, can beans in servlet specific contexts reference items defined in those configs?
Chris Frost Messages: 230 Registered: January 2010 Location: Southampton, England
You can either put all your spring context information in the applicationContext.xml file under WEB-INF and no config will be required in the web.xml or keep it in META-INF/spring and specify that as the location with 'contextConfigLocation' context-param.
Yes, servlet specific contexts will have full access to beans in your spring/osgi context, it will be one of its parent contexts due to the config you have put in web.xml as shown in your post.
As a side note, all the Manifest should need is the bundle classpath being set to include WEB-INF/classes where Baz.class should be compiled to.
or keep it in META-INF/spring and specify that as the location with 'contextConfigLocation' context-param.
That would bring spring-dm extender into the picture. You want to keep spring context files out of META-INF/spring for web-apps and let org.eclipse.virgo.web.dm.ServerOsgiBundleXmlWebApplicationContext deploy them.