I tried using ActiveMQ 5.2 XBean configs in ServiceMix kernel (compiled from trunk and 1.0.0) and I get the same error: unrecognized namespace mapping.

It works fine in plain Felix. I just have xbean-spring-3.5-SNAPSHOT loaded early in the process. I edited the startup.properties file in SM kernel to load the xbean-spring bundle right after the file monitor (so it would catch all the registration events), but no dice. I still get errors.

If I can figure out how to configure the logging in Felix, I'll be getting closer...

Thanks!

Jon Brisbin
http://jbrisbin.com

On Dec 3, 2008, at 8:37 AM, Guillaume Nodet wrote:

Each JBI component has the META-INF/spring.handlers file registering
the XBean namespace handler.
Spring-DM introspects all the bundles for such files, and simply call
the registered namespace handler which happen to be provided by XBean.
Then, XBean finds the meta data needed inside the component bundle
because the bundle takes care of exporting the needed package.
XBean has a dynamic import package on
META-INF.services.org.apache.xbean.spring.* which is the reason why it
can find the metdata.
Does it help a bit ?

On Wed, Dec 3, 2008 at 3:15 PM, Jon Brisbin <[EMAIL PROTECTED]> wrote:
I fashion myself a reasonably intelligent individual and I can't for the life of me understand how to make Spring DM use the ActiveMQ XBean mapping in either Felix or dm Server! I read every post or message on this topic I could find and the scattered information never fleshes out a full scenario.
They only give you bits and pieces.

How does ServiceMix get their custom NamespaceHandlers recognized? Does it
use a fragment? To what host does it attach in the Fragment-Host?

I've spent several days experimenting with different things and I just can't figure this out. Any help you could give would be greatly appreciated! :)

Thanks!

Jon Brisbin
http://jbrisbin.com





--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Reply via email to