On 24 Jul 2008, at 09:03, Nel Taurisson wrote: > I've encounter a strange problem with a bundle name. > > I had this bundle with seam bean in it (with the seam.properties in > the META-INF). The bundle had a "core" in its name > (org.skinsoft.platform.media.core). The problem was I couldn't acces > the seam beans declared in it.
You couldn't access the Seam beans, but was your bundle loaded at all? In other words, was it a Seam scanning problem or a bundle loading problem? > After a lot of time wondering if I was turning crazy, I made a > desperate crazy thing : I renamed the bundle replacing the "core" > with a "main" to org.skinsoft.platform.media.main (not touched > anaything else than the MANIFEST.MF, the pom.xml and the build.xml > files). Surprizingly, I could then acces the seam beans. > > Is "core" in bundle name is a kink of reserved key word ? No. It must be something in the Seam scanning mechanism. It faintly remember encoutering a bug similar to this, but it was in the unit test scaffolding to scan for bundles in the eclipse/maven classpath instead of those in a JBoss subdirectory, and it failed on the jar name because I had several and one was a prefix of another. It was resolved by switching to a OSGI-bundle-name-based loading of dependencies (deployBundle with dotted-name argument). Not this this'll help you though. Florent > If yes, are their any more reserverd key words in bundle names ? -- Florent Guillaume, Director of R&D, Nuxeo Open Source Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
