I did a search on the forum, but did not see anything addressing this issue (though it is a bit of an awkward search to make, so I may have missed something).
I'm new to Camel (evaluating it, Spring Integration and Mule for a project) and have been spending a little time trying to get a few different scenarios working. My project doesn't currently use Spring and I'd prefer to avoid additional dependencies if they aren't necessary. That said, I feel like I'm walking upstream trying to use Camel without Spring. It seems like most of the examples use Spring, even those that do routing using the Java DSL. I found it rather ironic that one of the first Spring Integration examples I ran across did not use the Spring framework, yet all of the Camel examples (other than the simple getting started) do. I'm not anti-Spring (I was typing in the code from the Wrox book before there was a download for the Interface21 code) and I don't want to cut off my nose to spite my face. If Spring + Camel gives me the preferred method of using Camel and it is more functional to use the combination, I'm fine with that. Just want feedback from the users/developers on whether it is worth trying to keep Spring out. Thanks. --Tim -- View this message in context: http://old.nabble.com/Camel-without-Spring-tp26225350p26225350.html Sent from the Camel - Users mailing list archive at Nabble.com.
