Hi,

Thank you very much for the quick answer. That was exactly the information I
was looking for.

Kind regards,
Michael Handler



Freeman Fang wrote:
> 
> Hi,
> 
> Ok, I understand your question more clearly now
> I will clarify more.
> For current servicemix bc/se component features which installed by  
> default when you start smx4, those components don't use JBI package   
> which means there's no jbi descriptor(jbi.xml) in it to specify the  
> sharedlib it depend, those components are just osgi packaged jars  
> (other than the JBI packaged zip we used for smx3.x) which use osgi  
> import package way to depend on servicemix-shared feature.
> 
> servicemix-shared feature looks like
> <feature name="servicemix-shared" version="2010.01">
>          <feature version="1.2.0">jbi</feature>
>          <bundle>mvn:org.apache.servicemix.bundles/ 
> org.apache.servicemix.bundles.wsdl4j/1.6.2_2</bundle>
>          <bundle>mvn:org.apache.xbean/xbean-spring/3.5</bundle>
>          <bundle>mvn:org.apache.servicemix/servicemix-utils/1.2.1</ 
> bundle>
>          <bundle>mvn:org.apache.servicemix/servicemix-common/2010.01</ 
> bundle>
>      </feature>
> it's just a set of bundle jars but not the JBI packaged JBI sharedlib
> 
> a servicemix bc component feature for example is
> <feature name="servicemix-file" version="2010.01">
>          <feature version="2010.01">servicemix-shared</feature>
>          <bundle>mvn:org.apache.servicemix/servicemix-file/2010.01</ 
> bundle>
>      </feature>
> 
> So if you install servicemix-file feature, container will install  
> servicemix-shared for you by default,  in this case, it's not listed  
> from "jbi:list" as it's not real JBI packaged sharedlib, it's just a  
> set of bundles.
> 
> However, we still support the JBI packaged component(zip file) for  
> backward compatibility, which explicitly have jbi.xml to define the  
> sharedlib it need(I believe this is your case), so in this case, you  
> need also deploy/install the sharedlib zip yourself  (install  
> servicemix-shared feature doesn't help here as it's not the JBI  
> packaged Sharedlib), so this time it will show up as "Shared  
> Libraries" when use "jbi:list".
> 
> Hope this helps
> 
> Freeman
> On 2010-4-22, at 下午2:23, mhandler wrote:
> 
>>
>> Hi,
>>
>> that was what I thought also, but when I try to install our  
>> components they
>> get not deployed and the log file states that servicemix-shared is  
>> missing
>> (see below). Further more when I manually install servicemix-shared  
>> (by
>> dropping into the deploy folder) the output from jbi:list looks like  
>> that:
>>
>> ka...@root> jbi:list
>> Shared Libraries
>> ----------------
>> openengsb-features-edb-core - 1.0.0-SNAPSHOT - openengsb-features- 
>> edb-core
>> servicemix-shared - 2010.01 - ServiceMix :: Shared
>>
>> Components
>> ----------
>>   State                  Name                  Description
>> [Started ] [openengsb-features-edb-se     ]     openengsb-features- 
>> edb-se
>> [Started ] [servicemix-vfs                ]
>> [Started ] [servicemix-cxf-bc             ]
>> [Started ] [servicemix-snmp               ]
>> [Started ] [servicemix-cxf-se             ]
>> [Started ] [servicemix-drools             ]
>> [Started ] [servicemix-saxon              ]
>> [Started ] [servicemix-mail               ]
>> [Started ] [servicemix-osworkflow         ]
>> [Started ] [servicemix-ftp                ]
>> [Started ] [servicemix-exec               ]
>> [Started ] [servicemix-smpp               ]
>> [Started ] [servicemix-jms                ]
>> [Started ] [servicemix-quartz             ]
>> [Started ] [servicemix-scripting          ]
>> [Started ] [servicemix-eip                ]
>> [Started ] [servicemix-camel              ]
>> [Started ] [servicemix-validation         ]
>> [Started ] [servicemix-bean               ]
>> [Started ] [servicemix-http               ]
>> [Started ] [servicemix-file               ]
>> [Started ] [servicemix-wsn2005            ]
>>
>> Service Assemblies
>> ------------------
>>   State                  Name                  Description
>> [Started ] [openengsb-package-all         ]     openengsb-package-all
>>
>> So shared libraries are explicitly listed. Why is that the case if  
>> they
>> should not show up in jbi:list?
>>
>> kind regards,
>> Michael Handler
>>
>> servicemix-log:
>>
>> 08:16:51,988 | WARN  | -SNAPSHOT/deploy |  
>> Deployer                         |
>> cemix.jbi.deployer.impl.Deployer  357 | Requirements not met for JBI
>> artifact in bundle null (openengsb-domains-report-plaintext-se).
>> Installation pending.
>> org.apache.servicemix.jbi.deployer.impl.PendingException:  
>> SharedLibrary not
>> installed: servicemix-shared
>>
>>
>>
>> Freeman Fang wrote:
>>>
>>> Hi,
>>>
>>> servicemix-shared feature is installed by default when you start  
>>> smx4,
>>> as it's a required dependency for other servicemix component  
>>> features.
>>> But servicemix-shared is only sharelib other than jbi component (You
>>> can find more about JBI component and SharedLib concept from JBI
>>> spec), so it shouldn't on the list when you run "jbi:list"
>>>
>>> Freeman
>>> On 2010-4-21, at 下午3:54, mhandler wrote:
>>>
>>>>
>>>> Hi!
>>>>
>>>> Is it possible to install servicemix-shared shared library, which
>>>> shows up
>>>> when I execute features:list as jbi shared library so that it shows
>>>> up in
>>>> jbi:list in ServiceMix 4.1?
>>>>
>>>> If I manually install servicemix-shared (by dropping the installer
>>>> zip into
>>>> the deploy folder) it shows up when I execute jbi:list. But because
>>>> it is
>>>> listed under features:list I think this is not the correct way to
>>>> install
>>>> servicemix-shared?
>>>>
>>>> kind regards,
>>>> Michael Handler
>>>>
>>>> Output features:list | grep servicemix-shared
>>>> [installed  ] [2010.01       ] servicemix-shared
>>>> repo-0
>>>>
>>>> ----------------------------------------------
>>>>
>>>> Output jbi:list
>>>> Components
>>>> ----------
>>>>  State                  Name                  Description
>>>> [Started ] [servicemix-ftp                ]
>>>> [Started ] [servicemix-vfs                ]
>>>> [Started ] [servicemix-bean               ]
>>>> [Started ] [servicemix-quartz             ]
>>>> [Started ] [servicemix-eip                ]
>>>> [Started ] [servicemix-http               ]
>>>> [Started ] [servicemix-osworkflow         ]
>>>> [Started ] [servicemix-cxf-bc             ]
>>>> [Started ] [servicemix-validation         ]
>>>> [Started ] [servicemix-saxon              ]
>>>> [Started ] [servicemix-cxf-se             ]
>>>> [Started ] [servicemix-jms                ]
>>>> [Started ] [servicemix-scripting          ]
>>>> [Started ] [servicemix-camel              ]
>>>> [Started ] [servicemix-smpp               ]
>>>> [Started ] [servicemix-exec               ]
>>>> [Started ] [servicemix-wsn2005            ]
>>>> [Started ] [servicemix-snmp               ]
>>>> [Started ] [servicemix-drools             ]
>>>> [Started ] [servicemix-mail               ]
>>>> -- 
>>>> View this message in context:
>>>> http://old.nabble.com/install-jbi-shared-library-from-features-tp28287968p28287968.html
>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>>
>>>
>>>
>>> -- 
>>> Freeman Fang
>>> ------------------------
>>> Open Source SOA: http://fusesource.com
>>>
>>>
>>>
>>
>> -- 
>> View this message in context:
>> http://old.nabble.com/install-jbi-shared-library-from-features-tp28287968p28324613.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
> 
> 
> -- 
> Freeman Fang
> ------------------------
> Open Source SOA: http://fusesource.com
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/install-jbi-shared-library-from-features-tp28287968p28325080.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to