What I really mean when talking about a Tomcat based deployement is really to bring the value we'll work on (i.e. message analysis, auditing, console and such) which are completely unrelated to OSGi, to people that want to deploy camel routes using web apps in Tomcat. If you look at the Camel survey (http://camel.apache.org/camel-30-roadmap.data/camel-survey-2010.pdf) a lot of Camel users don't really use OSGi, and there's no reason why not trying to help those people when using Camel to build an ESB.
I'm not sure how it can be done technically, and I don't really want to focus on this area specifically, but if it can be done without too much pain, I think it would help. That said, I think Gert's points are fully in line with my mindset in which Karaf is a much better container, but not everybody is ready to pay the initial cost of learning OSGi. On Wed, Jun 29, 2011 at 10:45, Ioannis Canellos <ioca...@gmail.com> wrote: > I am really happy to see the rebooting of Service Mix 5. > > I agree with most of the points mentioned but I am skeptic about the tomcat > deployment. > > I will skip talking about the advantages of such deployment option, since I > consider them obvious to all. I am worried on what it will mean to the pure > OSGi deployments (e.g. restrict the usage of OSGi APIs? Use of a framework > like pojosr?). > > Any thoughts? > > -- > *Ioannis Canellos* > * > http://iocanel.blogspot.com > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > Apache ServiceMix <http://servicemix.apache.org/> Committer > * > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
