Hi Geert,
I don't think it's a good idea to remove the Spring support in SMX5 as
it's fully supported by Camel.
If an user want to deploy Camel routes defined using Spring DSL, it should.
Of course, we can focus the documentation about the blueprint usage (I
think it's a good idea), but the Spring support should be still there in
SMX5.
Regards
JB
On 06/29/2011 11:14 AM, Geert Schuring wrote:
I too have doubts about the Tomcat distribution. The software stack that
ServiceMix consists of is already very complex, and contains all kinds of
frameworks and components that can be used outside ServiceMix or OSGi asn
well. In my opinion ServiceMix should focus on providing a consistent, well
documented environment instead of trying to serve as much different ways of
implementation as possible. I think that's an important reason why the
documentation has been so slow and painful for SMX 3& 4.
I think starting new documenation from scratch for SMX 5 is a very good
idea. Combined with using scalate and storing the documentation in
subversion, we should be able to write version specific and accurate
documentation.
Would it be possible to drop spring entirely and switch to blueprint for SMX
5? That again would simplify the examples and documentation, and would make
SMX 5 more accessible to new users.
Geert Schuring.
2011/6/29 Ioannis Canellos<ioca...@gmail.com>
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
*
