You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Andrea Zoppello <zo...@tiscali.it> on 2008/11/25 12:12:28 UTC
ServiceMixBean does not support classpath bean deployment
Hi,
The old lightweight container let you to develop your own pojo packet as
a jar
and put in servicemix classpath, and all was very simple and working
very well.
I'm now porting my old lw-components to servicemix-bean, and i want to
use the same
deployment style ( package my pojo exetending TransformBeanSupport as
jars ) and put in classpath.
Unfortunately this cause classloading problems because some class
packaged in servicemix-common.jar and servicemix-bean.jar are needed (
BeanSupport, TransformBeanSupport and so URIResolver, ExchangeTarget.. )
and so on.
To enable classptah deployment i finally created two jars and put in
servicemix classpath:
- smx-bean-support.jar ( with BeanSupport, ExcahngeTarget, and
TransformBeanSupport )
- smx-bean-common-utils ( wil all classes from
org.apache.servicemix.common.util )
This will solve all the problems, and let me to work as i've done in
past with lw-contakiner.
Any plan to support this in servicemix next release??
Andrea
Re: ServiceMixBean does not support classpath bean deployment
Posted by Andrea Zoppello <zo...@tiscali.it>.
Hi Guillaume,
I've tried to extract whole servicemix-common.jar and
servicemix-bean.jar but if
i extract the whole two packages this cause conflict installing other
components.
BTW i agree with you, hope to quicly move to smx4 and in general to osgi
deployments.
The classloading architecture is one of the main problems when you need
to deal with jbi.
Andrea
Guillaume Nodet ha scritto:
> An easier way would be to extract servicemix-common and
> servicemix-bean jars into the lib folder.
> Also note that such problems does not happen with smx4, which is one
> the benefit.
>
> On Tue, Nov 25, 2008 at 12:12 PM, Andrea Zoppello <zo...@tiscali.it> wrote:
>
>> Hi,
>>
>> The old lightweight container let you to develop your own pojo packet as a
>> jar
>> and put in servicemix classpath, and all was very simple and working very
>> well.
>>
>> I'm now porting my old lw-components to servicemix-bean, and i want to use
>> the same
>> deployment style ( package my pojo exetending TransformBeanSupport as jars )
>> and put in classpath.
>>
>> Unfortunately this cause classloading problems because some class packaged
>> in servicemix-common.jar and servicemix-bean.jar are needed ( BeanSupport,
>> TransformBeanSupport and so URIResolver, ExchangeTarget.. ) and so on.
>>
>> To enable classptah deployment i finally created two jars and put in
>> servicemix classpath:
>> - smx-bean-support.jar ( with BeanSupport, ExcahngeTarget, and
>> TransformBeanSupport )
>> - smx-bean-common-utils ( wil all classes from
>> org.apache.servicemix.common.util )
>>
>> This will solve all the problems, and let me to work as i've done in past
>> with lw-contakiner.
>>
>> Any plan to support this in servicemix next release??
>>
>> Andrea
>>
>>
>
>
>
>
Re: ServiceMixBean does not support classpath bean deployment
Posted by Guillaume Nodet <gn...@gmail.com>.
An easier way would be to extract servicemix-common and
servicemix-bean jars into the lib folder.
Also note that such problems does not happen with smx4, which is one
the benefit.
On Tue, Nov 25, 2008 at 12:12 PM, Andrea Zoppello <zo...@tiscali.it> wrote:
> Hi,
>
> The old lightweight container let you to develop your own pojo packet as a
> jar
> and put in servicemix classpath, and all was very simple and working very
> well.
>
> I'm now porting my old lw-components to servicemix-bean, and i want to use
> the same
> deployment style ( package my pojo exetending TransformBeanSupport as jars )
> and put in classpath.
>
> Unfortunately this cause classloading problems because some class packaged
> in servicemix-common.jar and servicemix-bean.jar are needed ( BeanSupport,
> TransformBeanSupport and so URIResolver, ExchangeTarget.. ) and so on.
>
> To enable classptah deployment i finally created two jars and put in
> servicemix classpath:
> - smx-bean-support.jar ( with BeanSupport, ExcahngeTarget, and
> TransformBeanSupport )
> - smx-bean-common-utils ( wil all classes from
> org.apache.servicemix.common.util )
>
> This will solve all the problems, and let me to work as i've done in past
> with lw-contakiner.
>
> Any plan to support this in servicemix next release??
>
> Andrea
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com