> > What benefit would you gain from Camel in this case? If your only goal
> is
> > to
> > expose a POJO service through a Restful interface a simple JAX-RS or
> > Spring
> > MVC/REST service would suffice. Or does the implementation of e.g.
> > findPerson(id) involve the use of Camel?
I forgot to
> What benefit would you gain from Camel in this case? If your only goal is
> to
> expose a POJO service through a Restful interface a simple JAX-RS or
> Spring
> MVC/REST service would suffice. Or does the implementation of e.g.
> findPerson(id) involve the use of Camel?
Fair question. I want to
o I specify the routes so that I can write my beans the way I
> described? I would rather map each method to the correct verb in my Java
> code, not in the route specification.
>
> Thanks in advance and best regards.
>
> --
> DCV
> Gonzalo Diethelm
> Gerente Desarrollo de Sistemas / CDO
>
3-9073
gdieth...@dcv.cl / www.dcv.cl
> -Original Message-
> From: gonzalo diethelm [mailto:gdieth...@dcv.cl]
> Sent: Monday, 16 May, 2011 18:46
> To: users@camel.apache.org
> Subject: RE: Service architecture
>
> > So, my question is: is it possible to magically g
> So, my question is: is it possible to magically go from the Camel from("")
> route definition to a Spring MVC implementation of the business logic?
Let me clarify my question a bit: I would love to be able to do this:
from("INPUT:http://localhost:9080/account";)
.to("PROCESS://magic");
T
I am still here, working out the way I will handle REST services with Camel.
I had to take a detour from the integration business and dive into web
applications. I ended up landing on Spring zone, and came to the decision that
all our projects will use Spring MVC Web and Spring MVC Portlets. But
Hi Gonzalo
Nice to meet you at TSSJS, and signing your copy of the Camel in
Action book. Now you gotta go to Canada to have Jon sign it as well :)
Or stop by DC next month for the Camel One conference.
Anyway I can see this thread has picked up and a lot of good feedback.
The one item I would ob
I wasn't advocating it at all - just making the distinction between the
function the 2 things performed
On 29 Mar 2011, at 22:10, Christian Schneider wrote:
> For me the decision was between JEE without camel and the typical Apache +
> Spring stack CXF, Camel, Spring, eventually Karaf
>
> Usi
For me the decision was between JEE without camel and the typical Apache
+ Spring stack CXF, Camel, Spring, eventually Karaf
Using Camel together with JEE would be interesting. I have not tried it
though.
Christian
Am 29.03.2011 18:56, schrieb John McDonald:
One doesnt have to be an apolog
On 29.03.2011 15:15, gonzalo diethelm wrote:
Great, this works. And I guess you meant that you would create one
endpoint for each operation, right?
For me it's more transparent - but you can do this like you want ;)
Something like this would work as well
from("restlet:http://localhost:9080/acco
> Hi Gonzalo,
Hi Christian, thanks for chiming in.
> I am a big fan of camel so don´t understand me wrong.
>
> If you are using JEE all over the place then you should at least think
> about migrating to JEE6 I am regularly reading the blog prosts of Adam
> Bien and from what he writes the modern
> > Great, this works. And I guess you meant that you would create one
> endpoint for each operation, right?
> For me it's more transparent - but you can do this like you want ;)
> Something like this would work as well
>
> from("restlet:http://localhost:9080/account/{id}?restletMethod=get,delete"
On 29.03.2011 13:59, gonzalo diethelm wrote:
One thing I have not been able to figure out is how to expose all these
CRUD services over jetty. Just as an example, let's say I will handle
account objects and will want to support three actions on them:
GET /account/{id} => retrieve that account
> > One thing I have not been able to figure out is how to expose all these
> CRUD services over jetty. Just as an example, let's say I will handle
> account objects and will want to support three actions on them:
> >
> > GET /account/{id} => retrieve that account
> > PUT /account/{id}/balance/{ba
Hi Mike,
you are certainly right 2 instances on the same server are better than
none, even though if your hardware breaks those 2 instances don't help
really ;)
Regards, Achim
2011/3/29 Michael Dewitte :
> Yes and no, I would say. You're right that it's better to have 2 different
> machines. But
Hi Gonzalo,
regarding NRM, sorry no documentation besides the one provided by ServiceMix :)
Regarding multiple instances of Karaf, you can administer those via
shell commands and start / stop them through your first instance.
regards, Achim
2011/3/29 gonzalo diethelm :
>> Makes sense, besides
Yes and no, I would say. You're right that it's better to have 2 different
machines. But IMHO, it's better to have failover between 2 instances on the
same machine than no fail over at all...
2011/3/29 Achim Nierbeck
> Hi Mike,
>
> but this only makes sense when you use multiple instances on dif
> nice thread, thanks for the sharing... to me, multiple instances makes
> sense
> for fail-over. Just configure it through the ActiveMQ...
That too.
--
Gonzalo Diethelm
> Makes sense, besides one point, why do you expect you need multiple
> Karaf instances?
> Regarding Camel or Spring there is no need to deploy those in extra
> Servers, because you only got
> one CamelContext/SpringContext per bundle. Therefore I'm sure you can
> use one Karaf instance with all yo
Hi Mike,
but this only makes sense when you use multiple instances on different
machines.
Doing Failover on the same machine I would rather not recommend.
Regards, Achim
2011/3/29 Michael Dewitte :
> Hi,
>
> nice thread, thanks for the sharing... to me, multiple instances makes sense
> for fail-
On 29.03.2011 12:58, gonzalo diethelm wrote:
Hi Gonzalo.
Hi Claus, thanks for your insight.
0. First off, does it really make sense to turn my back to J(2)EE? I
know I would be giving up a significant amount of "baseline", but I am
really hungry for some lean and mean architecture. Opinions
On 29 March 2011 11:58, gonzalo diethelm wrote:
>> Hi Gonzalo.
>
> Hi Claus, thanks for your insight.
>
>> > 0. First off, does it really make sense to turn my back to J(2)EE? I
>> know I would be giving up a significant amount of "baseline", but I am
>> really hungry for some lean and mean archi
Hi,
nice thread, thanks for the sharing... to me, multiple instances makes sense
for fail-over. Just configure it through the ActiveMQ...
Mike
2011/3/29 Achim Nierbeck
> Hi Gonzalo,
>
> Makes sense, besides one point, why do you expect you need multiple
> Karaf instances?
> Regarding Camel or
Hi Gonzalo,
Makes sense, besides one point, why do you expect you need multiple
Karaf instances?
Regarding Camel or Spring there is no need to deploy those in extra
Servers, because you only got
one CamelContext/SpringContext per bundle. Therefore I'm sure you can
use one Karaf instance with all y
> Hi,
Hi Achim, thanks for answering.
> just my 0.02$ on a container/runtime.
> My best experience as runtime for Camel is to use Karaf.
> If you need more out of the box components like ActiveMQ and so forth
> you might also consider to use Servicemix.
OK, my incipient plan so far is to use Kar
On 03/29/2011 12:48 PM, gonzalo diethelm wrote:
> Hi John, great insights (and confirmations) of my guesses...
>
>> I too want some kind of container support for my java apps that are run
>> from jars. The use of initd and all works but it doesnt feel right -
>> whereas a container like tomcat doe
In terms of the expansion - i assume its the Grails v Spring thing - so here
goes
The annotations in Spring look great - you can specify what method they should
match, mapping variables and paths onto the pojo methods and parameters. Very
sexy. My concern is that when you are trying to get a
> Hi Gonzalo.
Hi Claus, thanks for your insight.
> > 0. First off, does it really make sense to turn my back to J(2)EE? I
> know I would be giving up a significant amount of "baseline", but I am
> really hungry for some lean and mean architecture. Opinions?
>
> If you feel hungry - do it. I thi
Hi John, great insights (and confirmations) of my guesses...
> I too want some kind of container support for my java apps that are run
> from jars. The use of initd and all works but it doesnt feel right -
> whereas a container like tomcat does. I am considering OSGI containers -
> but lack any
Hi,
just my 0.02$ on a container/runtime.
My best experience as runtime for Camel is to use Karaf.
If you need more out of the box components like ActiveMQ and so forth
you might also consider to use Servicemix.
regards, Achim
2011/3/29 John McDonald :
> I was hoping people with more insight int
Hi Gonzalo.
1. Each service is a bundle running on an OSGi container; there could be one or
more containers running on one or more JVMs, on one or more servers.
2. Each service could export its entry points on several endpoint types; at
least one type for RPC (SOAP, REST, etc.) and one type fo
I was hoping people with more insight into this would contribute - its a good
set of questions and this forum is pretty good so I would have appreciated
their thoughts and musings. So to ignite things I will chip in.
I too want some kind of container support for my java apps that are run from
32 matches
Mail list logo
