-------------
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:26, djtom wrote:

> Hi,
> 
> Thanks for the reply.
> 
> I configured my SE with a SU as shown in tutorial of servicemix (I use
> servicemix 4.3.0), which is packaged in a different SA. It means, the SE and
> SA are different deployment zip files. The SU simply exposes endpoint and
> service of the SE. I have doubt that if I put the following snippet in
> bean.xml, first of all it does not work, of the SU:
> 
> <beans xmlns:ds=".."
>          xmlns:se="name space of my service engine">
> 
>   <se:endpoint service="ds:service" endpoint="dsEndpoint"/>
> 
>   <classpath>
>        <library>osgi:Bundle-SymbolicName</library>

You need replace the "Bundle-SymbolicName" with the actual bundle SymbolicName 
of each bundle you wanna refer
>   </classpath>                                                         
> 
> </beans>
> 
> 
> After putting the classpath like above bean.xml, I got the following
> exception (but it works if I put the class path in xbean.xml which use
> servicemix build-in component, such as servicemix-http):
> 
> 10:13:24,194 | ERROR | l Console Thread | ServiceAssemblyInstaller         |
> ?                                   ? | 125 -
> org.apache.servicemix.jbi.deployer - 1.4.0 | Error deploying SU dsds-su
> javax.jbi.management.DeploymentException: <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message";>
>       <component-name>servicemix-dsds</component-name>
>       <component-task-result-details>
>               <task-result-details>
>                       <task-id>deploy</task-id>
>                       <task-result>FAILED</task-result>
>                       <message-type>ERROR</message-type>
>                       
> <task-status-msg><msg-loc-info><loc-token/><loc-message>Could not deploy
> xbean service unit</loc-message></msg-loc-info></task-status-msg>
>                       <exception-info>
>                               <nesting-level>1</nesting-level>
>                               <msg-loc-info>
>                                       <loc-token />
>                                       <loc-message>Unexpected exception 
> parsing XML document from file
> [/home/ubuntu/TaxiScenarioMultiTenant/apache-servicemix-4.3.0/data/jbi/dsds-http-sa/sus/dsds-su/xbean.xml];
> nested exception is java.lang.UnsupportedOperationException: Can not access
> shared libraries</loc-message>
>                               
> <stack-trace><![CDATA[org.springframework.beans.factory.BeanDefinitionStoreException:
> Unexpected exception parsing XML document from file
> [/home/ubuntu/TaxiScenarioMultiTenant/apache-servicemix-4.3.0/data/jbi/dsds-http-sa/sus/dsds-su/xbean.xml];
> nested exception is java.lang.UnsupportedOperationException: Can not access
> shared libraries
>       at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:412)
>       at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
>       at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
>       at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
>       at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
>       at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
>       at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:212)
>       at
> org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:126)
>       at
> org.apache.xbean.spring.context.FileSystemXmlApplicationContext.loadBeanDefinitions(FileSystemXmlApplicationContext.java:168)
>       at
> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
>       at
> org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:467)
>       at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:397)
>       at
> org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:88)
>       at
> org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
>       at
> org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69)
>       at
> org.apache.servicemix.jbi.deployer.artifacts.ServiceUnitImpl.deploy(ServiceUnitImpl.java:104)
>       at
> org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.deploySUs(ServiceAssemblyInstaller.java:207)
>       at
> org.apache.servicemix.jbi.deployer.impl.ServiceAssemblyInstaller.install(ServiceAssemblyInstaller.java:85)
>       at
> org.apache.servicemix.jbi.deployer.impl.Deployer.onBundleStarted(Deployer.java:334)
>       at
> org.apache.servicemix.jbi.deployer.impl.Deployer.bundleChanged(Deployer.java:264)
>       at
> org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:807)
>       at
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:729)
>       at
> org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:610)
> ...
> 
> 
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://servicemix.396122.n5.nabble.com/slf4j-library-of-OSGi-bundle-cannot-found-in-a-SE-JBI-Component-tp5714899p5714904.html
> Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Reply via email to