On 29 June 2011 10:14, Geert Schuring <[email protected]> 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 as > 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.
An ESB is all about integration; so dropping support for things people use is generally bad; though for sure we should recommend on OSGi folks use blueprint as its simpler & smaller; though we should still support folks using Spring. -- James ------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: jstrachan, fusenews Blog: http://macstrac.blogspot.com/ Open Source Integration and Messaging
