I see that Mule has said no to OSGI and there are some Camel OSGI projects 
(https://github.com/szhem/camel-osgi). We never considered this is a parameter. 
Maybe we should update our paper with this.

-----Original Message-----
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: Monday, October 29, 2012 7:01 PM
To: users@camel.apache.org
Subject: Re: Our paper on Apache Camel

Hi Ramkumar

On page 2, section I, you have literature review.
Did you not look at published books for the various projects? Both
Camel, Mule and Spring Integration have books on the matter.
IMHO this is a quality sign of a project when books have been
published, or are in the works.
http://camel.apache.org/books

Also this blog post by Kai Waheler has been popular read, where he
gives some thoughts about Camel, Mule and SI as well
http://www.kai-waehner.de/blog/2012/01/10/spoilt-for-choice-which-integration-framework-to-use-spring-integration-mule-esb-or-apache-camel/

And the Camel editor Fuse IDE is being open sourced and free for
everyone to use. The project will be hosted at gibhub, when the
transition is done later this year.




On Sat, Oct 27, 2012 at 8:04 PM,  <ramkumar.i...@cognizant.com> wrote:
> Sorry, Thanks. Please note it is more focused on case study on adoption. We 
> are now in development phase and now digging more into Camel internals. The 
> real problem we foresee is one of meeting our non functional requirements 
> since Camel is very rich enough functionally to support our limited needs.
>
> https://docs.google.com/open?id=0BwrNg-893yAJaDlJcUtSUE5Welk
>
>
> -----Original Message-----
> From: Raul Kripalani [mailto:r...@evosent.com]
> Sent: Saturday, October 27, 2012 10:13 PM
> To: users@camel.apache.org
> Subject: Re: Our paper on Apache Camel
>
> Hi Ramkumar,
>
> Could you upload it somewhere and send a link to it? It looks like it got
> stripped away from the email.
>
> Looking forward to reading it.
>
> Thanks!
>
> *Raúl Kripalani*
> Apache Camel Committer
> Enterprise Architect, Program Manager, Open Source Integration specialist
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk <http://twitter.com/raulvk>
>
> On Sat, Oct 27, 2012 at 5:39 PM, <ramkumar.i...@cognizant.com> wrote:
>
>> I hope it benefits people who are looking to move away from proprietary
>> solutions. Would  be good to receive feedback.
>> This e-mail and any files transmitted with it are for the sole use of the
>> intended recipient(s) and may contain confidential and privileged
>> information. If you are not the intended recipient(s), please reply to the
>> sender and destroy all copies of the original message. Any unauthorized
>> review, use, disclosure, dissemination, forwarding, printing or copying of
>> this email, and/or any action taken in reliance on the contents of this
>> e-mail is strictly prohibited and may be unlawful.
>>
> This e-mail and any files transmitted with it are for the sole use of the 
> intended recipient(s) and may contain confidential and privileged 
> information. If you are not the intended recipient(s), please reply to the 
> sender and destroy all copies of the original message. Any unauthorized 
> review, use, disclosure, dissemination, forwarding, printing or copying of 
> this email, and/or any action taken in reliance on the contents of this 
> e-mail is strictly prohibited and may be unlawful.



--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
This e-mail and any files transmitted with it are for the sole use of the 
intended recipient(s) and may contain confidential and privileged information. 
If you are not the intended recipient(s), please reply to the sender and 
destroy all copies of the original message. Any unauthorized review, use, 
disclosure, dissemination, forwarding, printing or copying of this email, 
and/or any action taken in reliance on the contents of this e-mail is strictly 
prohibited and may be unlawful.

Reply via email to