L.S.,
You can probably deploy the same SA into ServiceMix 4, which does have a JBI compatibility layer that should support a lot of the 3.x use cases and components. We do not have an auditing feature in ServiceMix 4 any more, but everything else is implemented by the NMR layer (that's why you don't find any of the old JAR names). For the JBI API itself (DeliveryChannel, InOnly, ...), you can use the JBI API specs bundle as a project dependency. In 4.5.1, we use version 1.9.0 of that JAR (though the version should not make a difference here) , cfr. http://search.maven.org/#artifactdetails%7Corg.apache.servicemix.specs%7Corg.apache.servicemix.specs.jbi-api-1.0%7C1.9.0%7Cbundle Regards, Gert Vanthienen On Thu, Jul 18, 2013 at 9:39 AM, risen <[email protected]> wrote: > Hi! > The old system was using servicemix3.2.3 and jbi. > Spring DSL looks up the folder.If there are xml files, > JavaBean analyzes the file and sends message by Jbi. > > Just like: > InOnly exchange = getExchangeFactory().createInOnlyExchange(); > NormalizedMessage message = exchange.createMessage(); > ...... > exchange.setInMessage(message); > DeliveryChannel channel = getDeliveryChannel(); > if (channel != null) channel.sendSync(exchange); > > The old one uses the following jars. > servicemix-components-3.2.3.jar > servicemix-audit-3.2.3.jar > servicemix-core-3.2.3.jar > servicemix-jbi-3.2.3.jar > > Now i want to upgrade the old system to servicemix4.5.1,and use camel as > rooter. > But the servicemix4.5.1 doesn't have these jars.So i don't know how to use > camel-jbi to > upgrade the old source. > > Could you give me some help or advice? > > Thank you very much! > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/servicemix3-2-3-upgrade-to-servicemix4-5-1-tp5717318.html > Sent from the ServiceMix - User mailing list archive at Nabble.com.
