So if I include the servicemix-shared component then this would automatically work? Is there a way that I would need invoke this feature then?
On 8/29/07, Nodet Guillaume <[EMAIL PROTECTED]> wrote: > > Maybe we should switch to servicemix mailing list... > And yes, 3.2 default classloaders for a service unit > includes all the jars in the lib dir, but this is a feature > inside servicemix-shared, not the core container. > > On Aug 29, 2007, at 4:29 PM, Ryan Moquin wrote: > > > Ok, so I can just change my servicemix-version property in my > > pom.xml and it > > should all be configured properly? Will 3.2 support the ability to > > have jar > > files in the lib directory of a service unit picked up > > automatically? I > > find that to be a big hassle trying to keep the jars in my > > xbean.xml in sync > > with changes to the pom.... > > > > On 8/28/07, Nodet Guillaume <[EMAIL PROTECTED]> wrote: > >> > >> ServiceMix 3.2 is quite stable and should be released soon. > >> So feel free to start using the snapshot versions and you will > >> be able to upgrade to the released version when it is out. > >> You should be able to use the two components with a 3.1 version > >> too, but you may have to use the 3.2 version of the servicemix-shared > >> shared library. > >> > >> Cheers, > >> Guillaume Nodet > >> > >> On Aug 28, 2007, at 6:59 PM, Ryan Moquin wrote: > >> > >>> Are these components stable enough for use? Can we use them with > >>> Servicemix > >>> 3.1 or would I need to move to 3.2 (I'm not sure how stable that is > >>> either). We really aren't using servicemix for anything other > >>> than a > >>> container to hold 3 webservices right now, so if it only supported > >>> basic > >>> functionality we'd most likely be fine. I was hoping to take > >>> advantage of > >>> some of the CXF features if possible at this point. > >>> > >>> On 8/28/07, Nodet Guillaume <[EMAIL PROTECTED]> wrote: > >>>> > >>>> We are working on a better integration between ServiceMix and > >>>> CXF. I > >>>> would encourage you to check the new ServiceMix components that we > >>>> are working on as they will leverage all CXF features. These are > >>>> servicemix-cxf-bc and servicemix-cxf-se. Unfortunately, they > >>>> are not > >>>> documented yet, so I would advise you to look at the junit tests to > >>>> see how it works. Basically, servicemix-cxf-se is a replacement of > >>>> servicemix-jsr181 using CXF, and servicemix-cxf-bc is a > >>>> replacement > >>>> of servicemix-http using CXF. > >>>> These components are available at: > >>>> http://people.apache.org/repo/m2-snapshot-repository/org/ > >>>> apache/ > >>>> servicemix/servicemix-cxf-bc/3.2-incubating-SNAPSHOT/ > >>>> http://people.apache.org/repo/m2-snapshot-repository/org/ > >>>> apache/ > >>>> servicemix/servicemix-cxf-se/3.2-incubating-SNAPSHOT/ > >>>> > >>>> Cheers, > >>>> Guillaume Nodet > >>>> > >>>> On Aug 28, 2007, at 4:27 PM, Ryan Moquin wrote: > >>>> > >>>>> Hi, I decided to give CFX a try and upgrade from our XFire > >>>>> codebase. I'm > >>>>> wondering though, is CFX compatible with Servicemix 3.1? If so, > >>>>> how do you > >>>>> integrate it? I thought I saw somewhere it was. I did attempt to > >>>>> use CFX > >>>>> from within Servicemix, but the Jetty server that normally would > >>>>> start > >>>>> doesn't start, so I'm missing something with CFX. Or is this more > >>>>> of a > >>>>> servicemix question? > >>>>> > >>>>> Thanks! > >>>> > >>>> > >> > >> > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > >
