synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajith Attapattu" <rajit...@gmail.com>
Subject Re: Camel Re: Content based routing
Date Tue, 12 Feb 2008 16:28:50 GMT
Asankha,

That is true, most of the features that James said were available in his
comments in my blog, were difficult to find.
I agree that examples and documentation are very important to a project
sucess.
I will make these comments when I carry out corrections.

Regards,

Rajith

On Feb 11, 2008 10:01 PM, Asankha C. Perera <asankha@wso2.com> wrote:

>  Rajith
>
> Nice article.. Another point of comparison would be how good the
> documentation & samples are, especially for someone starting on it from
> scratch.
>
> asankha
>
>
> Rajith Attapattu wrote:
>
> I attend Bruce Synders talk on ActiveMQ where he talked a bit about Camel.
> I wanted to reply to this thread, instead wrote blog post comparing Camel
> and Synapse.
> http://rajith.2rlabs.com/2008/02/11/synapse-vs-camel/
>
> Shout if anything is missing/wrong ..etc.
>
> Regards,
>
> Rajith.
>
> On Feb 8, 2008 1:42 PM, Hadrian Zbarcea <hzbarcea@gmail.com> wrote:
>
> > I really don't want to discuss Camel on this forum, but...
> >
> > 1. Camel uses a DSL, which today has implementations in Java *and* XML
> > (with Ruby and others to come).  So no embedding Java in xml.
> > 2. Camel mediator?  Well I guess one could do that but, as I said in
> > my post, it doesn't have much more than an academic value because
> > Camel itself is a router, so doing that is sort of similar to using
> > synapse instead of ProxyPass in a situation where the payload did not
> > need to be unmarshalled for routing (which was the original topic of
> > this thread).
> >
> > Treat Camel as a scripting language?  Nah.
> >
> > Cheers,
> > Hadrian
> >
> >
> > On Feb 8, 2008, at 11:32 AM, Sanjiva Weerawarana wrote:
> >
> > > Camel is Java code .. so if you embed Java code in synapse.xml then
> > > you have to start compiling Java code. Not hard but boring IMO.
> > >
> > > The better way to use Camel is via a "Camel mediator" ... one that
> > > would basically take our message context and convert it to the Camel
> > > format and then invoke the Java code the user gives and at the end
> > > take the final message and feed it back into Synapse. That is, treat
> > > Camel as a scripting language.
> > >
> > > Sanjiva.
> > >
> > > Hadrian Zbarcea wrote:
> > >> Hi Paul,
> > >> I am not sure, given the fact that there is some overlap (at least
> > >> at the intent level) between Apache Camel and Synapse.  As you
> > >> probably know Camel takes the message body type agnostic stance
> > >> from the get go, which was my position in the beginning.  There are
> > >> quite a few niceties in Camel i really love, but I won't get
> > >> there :).
> > >> In terms of integration, I don't think integration between camel
> > >> and synapse endpoints helps much, and in terms of interoperating
> > >> with axis2 endpoints, that should be possible via camel-cxf.
> > >> If you have any idea please let me know.  And yeah, if you didn't
> > >> look closely at Camel, I would suggest doing it.  At least for fun,
> > >> it's worth it :).
> > >> Cheers,
> > >> Hadrian
> > >> On Feb 7, 2008, at 5:57 AM, Paul Fremantle wrote:
> > >>> Hadrian
> > >>>
> > >>> I haven't looked closely at Camel, but I'd be interested in your
> > >>> views
> > >>> on Camel and Synapse. Do you think there are areas we can
> > >>> integrate or
> > >>> collaborate?
> > >>>
> > >>> Paul
> > >>>
> > >>> On Feb 5, 2008 5:34 PM, Hadrian Zbarcea <hzbarcea@gmail.com>
wrote:
> > >>>> Hi Paul,
> > >>>>
> > >>>> How's life?
> > >>>>
> > >>>> I am not qualifying things as right or wrong, but we certainly
> > >>>> viewed
> > >>>> things differently.  And thinking of it, Apache Camel didn't
> > >>>> exist at
> > >>>> the time :).  Btw, one notable change in my life: I am not in
> > >>>> Boston
> > >>>> anymore, but some 700 miles south, in NC.
> > >>>>
> > >>>> Cheers,
> > >>>> Hadrian
> > >>>>
> > >>>>
> > >>>>
> > >>>> On Feb 4, 2008, at 11:04 AM, Paul Fremantle wrote:
> > >>>>
> > >>>>> Hadrian
> > >>>>>
> > >>>>> Nice to see you!
> > >>>>>
> > >>>>> I'm glad you are still around.
> > >>>>>
> > >>>>> Take a look at this --- you get the credit for it, and I guess
I
> > >>>>> have
> > >>>>> to admit I was wrong :)
> > >>>>>
> > https://svn.apache.org/repos/asf/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/util/PayloadHelper.java
> > >>>>>
> > >>>>> Paul
> > >>>>>
> > >>>>> On Feb 4, 2008 2:57 PM, Hadrian Zbarcea <hzbarcea@gmail.com>
> > >>>>> wrote:
> > >>>>>> The easiest thing for this would be a simple two line
> > >>>>>> configuration
> > >>>>>> for
> > >>>>>> ProxyPass/ProxyPassReverse in an apache web server.  The
> > >>>>>> user@synapse.apache.org list is probably a better forum
also :).
> > >>>>>> Cheers,
> > >>>>>> hadrian
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> On Feb 4, 2008, at 3:37 AM, Venkatesan, Kumaran wrote:
> > >>>>>>
> > >>>>>>
> > >>>>>> Hi,
> > >>>>>>
> > >>>>>> We are facing issue in routing requests. The requirement
is to
> > >>>>>> route the hit
> > >>>>>> on synapse to the services deployed on different host.
> > >>>>>>
> > >>>>>> This could be achieved by content based routing, but the
case
> > >>>>>> is to
> > >>>>>> handle
> > >>>>>> hundreds of services like below.
> > >>>>>>
> > >>>>>> For example,
> > >>>>>>
> > >>>>>> https://tradeti.stdcom/services/updateUser (hit to synapse)
to
> > >>>>>> https://10.192.12.89/services/updateUser (backend internal
> > >>>>>> systems)
> > >>>>>> https://tradeti.std.com/services/addUser to
> > >>>>>> https://10.192.12.89/services/addUser
> > >>>>>> https://tradeti.std.com/services/deleteUser to
> > >>>>>> https://10.192.12.89/services/deleteUser etc.,
> > >>>>>>
> > >>>>>> This email and any attachments are confidential and may
also be
> > >>>>>> privileged.
> > >>>>>> If you are not the addressee, do not disclose, copy, circulate
or
> > >>>>>> in any
> > >>>>>> other way use or rely on the information contained in this
> > >>>>>> email or
> > >>>>>> any
> > >>>>>> attachments. If received in error, notify the sender immediately
> > >>>>>> and delete
> > >>>>>> this email and any attachments from your system. Emails
cannot be
> > >>>>>> guaranteed
> > >>>>>> to be secure or error free as the message and any attachments
> > >>>>>> could
> > >>>>>> be
> > >>>>>> intercepted, corrupted, lost, delayed, incomplete or amended.
> > >>>>>> Standard
> > >>>>>> Chartered PLC and its subsidiaries do not accept liability
for
> > >>>>>> damage caused
> > >>>>>> by this email or any attachments and may monitor email
traffic.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Standard Chartered PLC is incorporated in England with
limited
> > >>>>>> liability
> > >>>>>> under company number 966425 and has its registered office
at 1
> > >>>>>> Aldermanbury
> > >>>>>> Square, London, EC2V 7SB.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Standard Chartered Bank ("SCB") is incorporated in England
with
> > >>>>>> limited
> > >>>>>> liability by Royal Charter 1853, under reference ZC18.
The
> > >>>>>> Principal Office
> > >>>>>> of SCB is situated in England at 1 Aldermanbury Square,
London
> > >>>>>> EC2V
> > >>>>>> 7SB. In
> > >>>>>> the United Kingdom, SCB is authorised and regulated by
the
> > >>>>>> Financial
> > >>>>>> Services Authority under FSA register number 114276.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> If you are receiving this email from SCB outside the UK,
please
> > >>>>>> click
> > >>>>>> http://www.standardchartered.com/global/email_disclaimer.html
to
> > >>>>>> refer to
> > >>>>>> the information on other jurisdictions.
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> --
> > >>>>> Paul Fremantle
> > >>>>> Co-Founder and VP of Technical Sales, WSO2
> > >>>>> OASIS WS-RX TC Co-chair
> > >>>>>
> > >>>>> blog: http://pzf.fremantle.org
> > >>>>> paul@wso2.com
> > >>>>>
> > >>>>> "Oxygenating the Web Service Platform", www.wso2.com
> > >>>>>
> > >>>>
> > >>>>>
> > ---------------------------------------------------------------------
> > >>>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > >>>>> For additional commands, e-mail: dev-help@synapse.apache.org
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> > ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > >>>> For additional commands, e-mail: dev-help@synapse.apache.org
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>> --Paul Fremantle
> > >>> Co-Founder and VP of Technical Sales, WSO2
> > >>> OASIS WS-RX TC Co-chair
> > >>>
> > >>> blog: http://pzf.fremantle.org
> > >>> paul@wso2.com
> > >>>
> > >>> "Oxygenating the Web Service Platform", www.wso2.com
> > >>>
> > >>>
> > ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > >>> For additional commands, e-mail: dev-help@synapse.apache.org
> > >>>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > >> For additional commands, e-mail: dev-help@synapse.apache.org
> > >
> > > --
> > > Sanjiva Weerawarana, Ph.D.
> > > Founder & Director; Lanka Software Foundation;
> > http://www.opensource.lk/
> > > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> > > Member; Apache Software Foundation; http://www.apache.org/
> > > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > > For additional commands, e-mail: dev-help@synapse.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > For additional commands, e-mail: dev-help@synapse.apache.org
> >
> >
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> blog: http://rajith.2rlabs.com/
>
>


-- 
Regards,

Rajith Attapattu
Red Hat
blog: http://rajith.2rlabs.com/

Mime
View raw message