Hi, Ensure your customer SeviceEngine also OSGi friendly. What works in SMX 3.x doesn't mean it also works in SMX 4.x. Firstly, your customer SeviceEngine should also be a OSGi bundle, it should use blueprint(or spring-dm) to expose an OSGi service which implements the javax.jbi.component.Component interface, so it could be wired dynamically. Please take a look at servicemix-camel SE[1] or other SE shipped with Servicemix as an example.
[1]https://svn.apache.org/repos/asf/servicemix/components/trunk/engines/servicemix-camel/ Freeman －－－－－－－－－－－－－ Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: http://weibo.com/u/1473905042 On 2012-11-13, at 下午6:47, djtom wrote: > yes I did it. It was just example, my bean.xml file is as following: > > > <beans > xmlns:dsdsComponent="http://dsds.iaas.uni-stuttgart.de/dsds-component/1.0"; > xmlns:dsds="http://jbimulti2.iaas.uni-stuttgart.de/dsds"; > xmlns="http://www.springframework.org/schema/beans"; > xmlns:xsi="http://http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://servicemix.apache.org/http/1.0 > http://servicemix.apache.org/schema/servicemix-http-3.2.3.xsd > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-2.0.xsd";> > > <dsdsComponent:endpoint service="dsds:dsdsService" > endpoint="dsdsEndpoint"/> > > <classpath> > <library>osgi:jbi.servicemix.registry</library> > </classpath> > > </beans> > > where, "http://dsds.iaas.uni-stuttgart.de/dsds-component/1.0"; is name space > of my newly created SE. > "jbi.servicemix.registry" is symbolic name of my OSGi bundle. > > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/slf4j-library-of-OSGi-bundle-cannot-found-in-a-SE-JBI-Component-tp5714899p5714907.html > Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
