L.S., Those warnings indicate that a XBean namespace handler is unavailable, probably due to problems in the OSGi metadata and/or the startup order on the bundles that hold the namespace handlers. They're harmless unless you're planning on using those specific namespaces, but could you raise a JIRA to get those issues addressed anyway (because it looks a lot better if the container starts without any alarming warnings, obviously)?
Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Tue, Jun 14, 2011 at 11:58 AM, mahrob <[email protected]> wrote: > Hi JB, > > Thanks for your response. Also, I am getting below classnotfound exceptions > at startup: > > ============================ > 22:04:02,464 | WARN | rint Extender: 3 | XBeanNamespaceHandler | > 52 - org.apache.xbean.blueprint - 3.7 | Could not load class: > org.apache.activemq.store.journal.JournalPersistenceAdapter due to > org/apache/activeio/journal/JournalEventListener > .. > 22:04:02,712 | WARN | rint Extender: 3 | XBeanNamespaceHandler | > 52 - org.apache.xbean.blueprint - 3.7 | Could not load class: > org.apache.activemq.store.journal.JournalPersistenceAdapterFactory due to > org/apache/activeio/journal/active/JournalLockedException > ============================ > > Any idea how can I resolve these? > > Thanks > Noman A. > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/osgi-install-Bundles-persistence-tp4484932p4487349.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. >
