Custom Camel Component -- Some Deployment Problems

[mhuisking_michael.c.huisking]

Hi,

This is a "part two" to my question about packaging my custom component.  I now have the component complete and have written wrapper projects to generate OSGi bundles for the dependencies.  (I had tried to use install wrap:mvn:xxxxx first, but wasn't having success using those bundles)

Here's what I've got:

• My unit test for the component runs successfully, so I know my pom file and dependencies are all correct. (Runs great in routes in the IDE and command line)

• I successfully install and start all of the dependent bundles -- no errors

• I successfully install and start the component bundle -- no errors.

I have two test projects -- one blueprint based and one spring based (trying to create examples for each) consisting of a quartz component setting the body of a message and passing it to my custom component -- the same that I have in my unit test case.   When I deploy and start the spring based route, it throws a null pointer exception while it's trying to resolve my custom endpoint.  When I deploy and start the blueprint based route, it goes into "GracePeriod" and I see the message:

Bundle blueprint-test is waiting for dependencies (&(component=mycomp)(objectClass=org.apache.camel.spi.ComponentResolver))

The component isn't being resolved and this bundle times out and errors (probably the same thing that happens in the spring based one)

I have the auto-discovery metadata all defined for "mycomp" in META-INF/services/org/apache/camel/component/mycomponent and there doesn't seem to be any problem recognizing it in the routes running outside of the container.

So, I guess my question is this -- How can I increase the information in the log so that I can see exactly which dependency is screwing this up? (I have a hunch that it is in a bundle other than the "mycomp" bundle, even though an exception is not being thrown)  Or, am I just missing a step when I deploy the component bundle and not explicitly registering the URI scheme with the container?  Any good component debugging tips? (inside the container since it is well behaved outside the container)

Thanks in advance,

Mick

[ffang]

Hi,

The error indicates that your customer camel component didn't expose required OSGi serivce org.apache.camel.spi.ComponentResolver

Can you use

ls your_customer_camel_component_bundle_id

to see if it really expose that OSGi service?

And for the debug, yeah, remote debug is very useful if you try to figure out what's wrong in OSGi container, take a look at to get more details

Besically you need

export KARAF_DEBUG=true

before you start fuse esb, and you can remote debug from port 5005 in your favorite IDE.

http://karaf.apache.org/manual/latest-2.3.x/developers-guide/debugging.html

Freeman

[mhuisking_michael.c.huisking]

Thanks for the tips. I'm definitely not exposing ComponentResolver.  I started this component using the camel-component archetype and then modified the pom file as described in the esb_deploy_osgi document (http://fusesource.com/docs/esb/4.4/esb_deploy_osgi/index.html for others referring to this post in the future)

So, what is the additional step?  Should I write a class implementing the BundleActivator interface, or is there something easier to do since my component extends DefaultComponent?

I'm thinking that once I get this all fixed up and working, I'll take the example from Claus' book and put a concrete example of modifying that for OSGi deployment.

Once again, thanks for your help Feeman.

Mick

Edited by: mhuisking on Dec 17, 2012 3:58 PM

edit -- made the referred html a link

[mhuisking_michael.c.huisking]

I went back to the simple "HelloWorld" and tweaked it for OSGi deployment.  It exposes the spi.ComponentResolver interface by default.

So, I went back into my custom component project and explicitly added "org.apache.camel.*" (just to be sure that nothing was missed)  Rebuilt and redeployed.

Now, when I do a "ls" on the bundle I see

component:  myComp

objectClass = org.apache.camel.spi.ComponentResolver

Lesson learned here -- when modifying the "Export-Package" be sure to include the org.apache.camel classes so the component will automatically be recognized as an OSGi service.

Mick

Edited by: mhuisking on Dec 18, 2012 5:40 PM

[mhuisking_michael.c.huisking]

One final note for this thread:

Scott Cranton has already done the work making a nice Camel/OSGi bundle.

https://github.com/FuseByExample/HelloCamel

It exports everything (I had some things that I didn't want to expose in my case) so it works right after building and deploying it.

[ffang]

Hi,

Thanks for sharing your solution!

Freeman