Hi, good that it works with Spring 3 :), at least this can be the basis of some Discussion and or development and might take some pressure of this part of the project ;)
regarding the camel part, for simplification (and again to reduce the spring-dependencies) I'd switch that part over to Blueprint. Just one thing to get of the list and less to worry about. regards, Achim 2014-05-19 14:27 GMT+02:00 constv <[email protected]>: > Achim and Tim, thank you for your help! > > > Achim Nierbeck wrote > > yes this setup looks good to me, > > just one "note", don't know if you're already doing it, for the camel > part > > make sure it is all blueprint / JavaDSL for the Camel route :) > > Yes, I always use JavaDSL to define Camel routes. In Spring configuration, > I > simply define camelContext <package> to enable package scanning for route > builders. > > Achim, > I will investigate/try some of the options you are suggesting. Everything > seems to work with Spring 3, and if I can use that, it seems to be the > easiest option. But if I have to use Spring 4 (which may be the client's > requirement) I'd have to find ways to work around it as you have suggested. > Thanks again for taking the time to help!! > > > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Spring-4-0-2-and-spring-dm-tp4033093p4033179.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Software Architect / Project Manager / Scrum Master
