Hi, The situation is more complex than that. The following sentence has been written like that "Apache Camel is a powerful Spring based Integration Framework." to focus the attention of the user that Camel uses Spring for one of its DSL language and can be easily integrated into Spring based projects. Removing completely every reference to Spring is a bit dangerous as it will give the impression to end users that we don't use it anymore. So I propose the following text -->
"Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful Bean Integration. It has been designed to be easily integrated with Java standards like J2EE or Spring and can be deployed in several runtime platforms : Apache Tomcat, J2EE Servers, OSGI (Apache Felix, Apache Karaf), ESB (Apache ServiceMix), Cloud (FuseSource Fabric) or can be run in standalone." Regards, Charles Moulliard Apache Committer Blog : http://cmoulliard.blogspot.com Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard Skype: cmoulliard On Mon, Aug 15, 2011 at 4:12 AM, Willem Jiang <willem.ji...@gmail.com> wrote: > +1 to remove the descriptions of the Spring based. > > On 8/13/11 7:14 PM, Claus Ibsen wrote: >> >> Hi >> >> I noticed the README.txt file in the distribution kit starts as follows: >> Apache Camel is a powerful Spring based Integration Framework. >> >> And our website starts as follows: >> Apache Camel is a powerful open source integration framework based on >> known Enterprise Integration Patterns with powerful Bean Integration. >> >> >> I think we should align the product descriptions on the web site and >> the README.txt file. >> There may be other places the product description is present, and >> could use a bit upgrade. >> >> >> For example I think the README.txt file is a bit outdated as it gives >> the impression that Camel requires Spring and is Spring based. >> As we all know Camel is more than that and we try to be neutral and >> let people use and run Camel in any kind of environment. >> Whether its Spring, OSGi, Karaf, ServiceMix, WebSphere, Cloud, Scala, >> Standalone etc. >> >> >> So anyone got suggestions/feedback to have the product description >> updated a bit to reflect where we are today with Apache Camel? >> >> For example we may want to mention Apache Karaf on the front page as a >> product that Camel runs with out of the box. etc. >> >> >> > > > -- > Willem > ---------------------------------- > FuseSource > Web: http://www.fusesource.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.javaeye.com (Chinese) > Twitter: willemjiang > Weibo: willemjiang >
