L.S.,
You should be able to migrate any existing components you have by: - changing the packaging to bundle - adding a Blueprint XML file to register the component in the OSGi Service Registry (you can use e.g. http://svn.apache.org/repos/asf/servicemix/components/trunk/bindings/servicemix-file/src/main/resources/OSGI-INF/blueprint/servicemix-file.xmlas an example) Most of the times however, it's a lot easier to avoid writing new components alltogether and just use POJOs to implement custom stuff and use those from your Camel routes. Camel supports using those POJOs in lots of different ways (cfr. http://camel.apache.org/bean-integration.html) so you're bound to find a suitable solution that takes away the need for a custom component. If you do think you need a new component, I would recommend you to write a Camel component instead of a JBI component. Those tend to be a lot easier to code and maintain - also, the Camel API is a bit easier to work with than the JBI API. Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Wed, Aug 10, 2011 at 7:38 AM, raakula <[email protected]> wrote: > Hi Jon, > Thanks for the response. I will go through it. > By the way do we have some examples on how to build custom components in > SMX4.3 and more importantly deploy them. > > regards, > Ramu > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/Migration-from-SMX3-3-2-to-SMX-4-3-tp4653956p4684686.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. >
