Freeman, We did it that way because we have several cxf-bc endpoints that are spread across multiple SA's and all run on the same port, this is the workaround we figured from you post in april 2009.
http://cwiki.apache.org/SM/discussion-forums.html#nabble-td23066349 Has this been fixed in SMX3.3.1, where we can set busCfg=cxf.xml for multiple cxf-bc endpoints in xbean.xml of the SA? thanks -gopal Freeman Fang wrote: > > Hi, > > Even you use SMX3 with JBI package SAs/SUs, you should put busConfig > files(cxf.xml in your case) in SAs/SUs, but not put it in SMX_HOME/ > conf. > > Freeman > On 2009-12-7, at 上午2:22, GNarra wrote: > >> >> Lukasz, >> >> We have a installation of SMX3.3.1 with CXF BC, CXF SE, SA's, We >> want to >> move to SMX 4 by deploying these existing SA's in SMX4 and then move >> the >> SA's to OSGi Bundles, If we start migrating to OSGi bundles as our >> starting >> step, it is going to take significant time before our system is >> ready to >> test. >> >> So I am looking to how to migrate quickly and then move to OSGi >> bundles. I >> looked at SMX 4 documentation for migrating but all that says is >> deploy the >> SA's in deploy directory. We have stand alone jars that are not part >> of SA's >> and deployed in the lib folder. I am wondering how do I move all this >> configuration(servicemix.conf) to SMX 4. >> >> cxf.xml was used by the CXF BC and CXF SE to initiliaze the port for >> the >> whole bus(CXFBusImp)l, I see that CXF BC is still on 2009.01 version >> in SMX >> 4, so where do I deploy the cxf.xml bus configuration. >> >> thanks for your help >> -gopal >> >> >> Lukasz Dywicki wrote: >>> >>> Hello, >>> Changes that ServiceMix team made in SMX 4 is really big. >>> 1) It depends, because SMX 4 is built on OSGi. In OSGi world class >>> loading >>> are very strict. In SMX 3 the conf directory was classpath element. >>> In >>> SMX4 configuration is no longer classpath element so you have to >>> enable it >>> in own bundle. >>> 2) In SMX 4 the JBI is only one feature from set of provided. If >>> you had >>> defined beans in servicemix.xml you should enable it as services in >>> OSGi >>> bundle. SMX4 offers support for JBI 1.0 but preffered programming >>> is based >>> on OSGi bundles. First of all it allows you to define many different >>> endpoints in one bundle (Maven project) - CXF BC, CXF SE or event >>> embedded >>> Camel. >>> 3) The default broker is on deploy directory. >>> 4) You can add own keystore using -Djavax.net.ssl.keyStore parameter. >>> >>> Best regards, >>> Lukasz Dywicki >>> >>> >>> GNarra wrote: >>>> >>>> Hi All, >>>> >>>> We are evaluating on making the move from SMX3.3.1 to SMX4 and >>>> have a few >>>> questions. >>>> >>>> 1) In SMX 3.3.1, we deployed servicemix/conf/cxf.xml which has the >>>> <httpj:engine-factory><httpj:engine port="0000">, where do you >>>> deploy >>>> cxf.xml in SMX4 configuration? >>>> 2) what is the equivalent of servicemix.xml "jbi" container >>>> configuration? >>>> 3) Where is the DefaultBroker class in smx4? >>>> 4) In SMX4 there is no keystore.jks file, >>>> >>>> any help is greatly appreciated >>>> >>>> thanks >>>> -gopal >>>> >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/Migrating-from-SMX3-to-SMX4-tp26646562p26667505.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/Migrating-from-SMX3-to-SMX4-tp26646562p26697084.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
