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-tp26646562p26665436.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
