You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by mumbly <mc...@gmail.com> on 2009/12/04 17:29:08 UTC

Jersey No Longer Supported?

I'm a bit confused as to whether Jersey is currently supported for REST. I've
seen indications that it was supported at some point from searches I've
made, but it looks like there are only camel-cxf and camel-restlet
components currently in the lineup. Did Jersey support get deprecated? Was
it never really there?

Thanks.

--Tim
-- 
View this message in context: http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26635942.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Jersey No Longer Supported?

Posted by James Strachan <ja...@gmail.com>.
FWIW the aim of camel-web is to provide a REST front end to all of
Camel & its features (like endpoints, routes, components, languages,
type converters etc) and to allow things to be modified RESTfully from
any language (e.g. browsing messages on BrowsableEndpoints, sending
messages to endpoints, adding/editing/stopping/starting routes,
creating new endpoints etc.

camel-web also happens to come with a web console humans can use as
well as any http client in any programming language.

However camel-web doesn't create a camel Component or provide explicit
camel Endpoints.

2009/12/10 Tim McNerney <mu...@gmail.com>:
> Sure, but it would be silly to write if it already exists, so I just
> want to confirm that my understanding is correct. And I'm interested
> mainly in that we already use Jersey, not that I'm especially wedded
> to it.
>
> --Tim
>
> On Thu, Dec 10, 2009 at 1:55 AM, Claus Ibsen <cl...@gmail.com> wrote:
>> On Thu, Dec 10, 2009 at 12:16 AM, mumbly <mc...@gmail.com> wrote:
>>>
>>> So I finally took a look at web-console. It looks to me like it is not a
>>> component, per se, but a utility that happens to use Jersey. At least, I
>>> don't see it on the components page and the web-console.html page does not
>>> sound like a component. I haven't looked at the source code. Is there an
>>> undocumented component hidden away in there somewhere?
>>>
>>
>> Its not as if if a camel-jersey component is lacking its impossible to
>> use Camel with Jersey. Its both java code after all.
>> And using Camels ProducerTemplate its very easy to send a message from
>> java to a Camel route.
>>
>> We love contribution so if someone is up for the task to try create
>> such a component that would be cool.
>>
>>
>>
>>> --Tim
>>>
>>>
>>> cmoulliard wrote:
>>>>
>>>> The component http://camel.apache.org/web-console.html has been designed
>>>> around jersey implementation of JAX-RS
>>>>
>>>> As you mention camel-cxf is based on CXF and camel-restlet on RESTlet
>>>>
>>>> Regards,
>>>>
>>>> Charles Moulliard
>>>> Senior Enterprise Architect
>>>> Apache Camel Committer
>>>>
>>>> *****************************
>>>> blog : http://cmoulliard.blogspot.com
>>>> twitter : http://twitter.com/cmoulliard
>>>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>>>
>>>> Apache Camel Group :
>>>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>>>
>>>>
>>>> On Fri, Dec 4, 2009 at 5:29 PM, mumbly <mc...@gmail.com> wrote:
>>>>
>>>>>
>>>>> I'm a bit confused as to whether Jersey is currently supported for REST.
>>>>> I've
>>>>> seen indications that it was supported at some point from searches I've
>>>>> made, but it looks like there are only camel-cxf and camel-restlet
>>>>> components currently in the lineup. Did Jersey support get deprecated?
>>>>> Was
>>>>> it never really there?
>>>>>
>>>>> Thanks.
>>>>>
>>>>> --Tim
>>>>> --
>>>>> View this message in context:
>>>>> http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26635942.html
>>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>
>>>>
>>>> -----
>>>> Charles Moulliard
>>>> SOA Architect
>>>>
>>>> My Blog : http://cmoulliard.blogspot.com/
>>>>
>>>
>>> --
>>> View this message in context: http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26719470.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Author of Camel in Action: http://www.manning.com/ibsen/
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>>
>



-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://fusesource.com/

Re: Jersey No Longer Supported?

Posted by dspatel81 <ds...@gmail.com>.
Hello, 

The same case as Charles but my request is little business driven where I
have component already written in Jersey and I want to plug it in with
existing Camel routes of another application.

Can I use my Jersey impl with Camel as of now (i.e. Feb 13, 2015)??

Regards
Dharmesh




--
View this message in context: http://camel.465427.n5.nabble.com/Jersey-No-Longer-Supported-tp473402p5762710.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Jersey No Longer Supported?

Posted by Charles Moulliard <cm...@gmail.com>.
Hi Tim,

I think that it should be possible to use Jersey now in a Camel route. If I
have enough time time today, I will make a test but we could use Jersey like
this

<from uri="jetty:http://localhost:8181?matchOnUriPrefix=true"/> (a)
<bean ref="jerseyBean" method="fetch"/> (b)

a) It is a Jetty endpoint who will consume HTTP requests (let's say REST
requests - GET, POST, ...) and send in the body the request + headers to the
bean
b) The jerseyBean is a bean class annoted with javax.ws.rs.GET, ...
annotations
Using Spring, it should be easy to inject Jersey into jerseyBean

Maybe this sample project could be helpfull :
https://jersey.dev.java.net/svn/jersey/trunk/jersey/samples/spring-annotations

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard

Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm


On Thu, Dec 10, 2009 at 3:39 PM, Tim McNerney <mu...@gmail.com> wrote:

> Sure, but it would be silly to write if it already exists, so I just
> want to confirm that my understanding is correct. And I'm interested
> mainly in that we already use Jersey, not that I'm especially wedded
> to it.
>
> --Tim
>
> On Thu, Dec 10, 2009 at 1:55 AM, Claus Ibsen <cl...@gmail.com>
> wrote:
> > On Thu, Dec 10, 2009 at 12:16 AM, mumbly <mc...@gmail.com> wrote:
> >>
> >> So I finally took a look at web-console. It looks to me like it is not a
> >> component, per se, but a utility that happens to use Jersey. At least, I
> >> don't see it on the components page and the web-console.html page does
> not
> >> sound like a component. I haven't looked at the source code. Is there an
> >> undocumented component hidden away in there somewhere?
> >>
> >
> > Its not as if if a camel-jersey component is lacking its impossible to
> > use Camel with Jersey. Its both java code after all.
> > And using Camels ProducerTemplate its very easy to send a message from
> > java to a Camel route.
> >
> > We love contribution so if someone is up for the task to try create
> > such a component that would be cool.
> >
> >
> >
> >> --Tim
> >>
> >>
> >> cmoulliard wrote:
> >>>
> >>> The component http://camel.apache.org/web-console.html has been
> designed
> >>> around jersey implementation of JAX-RS
> >>>
> >>> As you mention camel-cxf is based on CXF and camel-restlet on RESTlet
> >>>
> >>> Regards,
> >>>
> >>> Charles Moulliard
> >>> Senior Enterprise Architect
> >>> Apache Camel Committer
> >>>
> >>> *****************************
> >>> blog : http://cmoulliard.blogspot.com
> >>> twitter : http://twitter.com/cmoulliard
> >>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> >>>
> >>> Apache Camel Group :
> >>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
> >>>
> >>>
> >>> On Fri, Dec 4, 2009 at 5:29 PM, mumbly <mc...@gmail.com> wrote:
> >>>
> >>>>
> >>>> I'm a bit confused as to whether Jersey is currently supported for
> REST.
> >>>> I've
> >>>> seen indications that it was supported at some point from searches
> I've
> >>>> made, but it looks like there are only camel-cxf and camel-restlet
> >>>> components currently in the lineup. Did Jersey support get deprecated?
> >>>> Was
> >>>> it never really there?
> >>>>
> >>>> Thanks.
> >>>>
> >>>> --Tim
> >>>> --
> >>>> View this message in context:
> >>>>
> http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26635942.html
> >>>> Sent from the Camel - Users mailing list archive at Nabble.com.
> >>>>
> >>>>
> >>>
> >>>
> >>> -----
> >>> Charles Moulliard
> >>> SOA Architect
> >>>
> >>> My Blog : http://cmoulliard.blogspot.com/
> >>>
> >>
> >> --
> >> View this message in context:
> http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26719470.html
> >> Sent from the Camel - Users mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> >
> > --
> > Claus Ibsen
> > Apache Camel Committer
> >
> > Author of Camel in Action: http://www.manning.com/ibsen/
> > Open Source Integration: http://fusesource.com
> > Blog: http://davsclaus.blogspot.com/
> > Twitter: http://twitter.com/davsclaus
> >
>

Re: Jersey No Longer Supported?

Posted by Tim McNerney <mu...@gmail.com>.
Sure, but it would be silly to write if it already exists, so I just
want to confirm that my understanding is correct. And I'm interested
mainly in that we already use Jersey, not that I'm especially wedded
to it.

--Tim

On Thu, Dec 10, 2009 at 1:55 AM, Claus Ibsen <cl...@gmail.com> wrote:
> On Thu, Dec 10, 2009 at 12:16 AM, mumbly <mc...@gmail.com> wrote:
>>
>> So I finally took a look at web-console. It looks to me like it is not a
>> component, per se, but a utility that happens to use Jersey. At least, I
>> don't see it on the components page and the web-console.html page does not
>> sound like a component. I haven't looked at the source code. Is there an
>> undocumented component hidden away in there somewhere?
>>
>
> Its not as if if a camel-jersey component is lacking its impossible to
> use Camel with Jersey. Its both java code after all.
> And using Camels ProducerTemplate its very easy to send a message from
> java to a Camel route.
>
> We love contribution so if someone is up for the task to try create
> such a component that would be cool.
>
>
>
>> --Tim
>>
>>
>> cmoulliard wrote:
>>>
>>> The component http://camel.apache.org/web-console.html has been designed
>>> around jersey implementation of JAX-RS
>>>
>>> As you mention camel-cxf is based on CXF and camel-restlet on RESTlet
>>>
>>> Regards,
>>>
>>> Charles Moulliard
>>> Senior Enterprise Architect
>>> Apache Camel Committer
>>>
>>> *****************************
>>> blog : http://cmoulliard.blogspot.com
>>> twitter : http://twitter.com/cmoulliard
>>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>>
>>> Apache Camel Group :
>>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>>
>>>
>>> On Fri, Dec 4, 2009 at 5:29 PM, mumbly <mc...@gmail.com> wrote:
>>>
>>>>
>>>> I'm a bit confused as to whether Jersey is currently supported for REST.
>>>> I've
>>>> seen indications that it was supported at some point from searches I've
>>>> made, but it looks like there are only camel-cxf and camel-restlet
>>>> components currently in the lineup. Did Jersey support get deprecated?
>>>> Was
>>>> it never really there?
>>>>
>>>> Thanks.
>>>>
>>>> --Tim
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26635942.html
>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>>>
>>> -----
>>> Charles Moulliard
>>> SOA Architect
>>>
>>> My Blog : http://cmoulliard.blogspot.com/
>>>
>>
>> --
>> View this message in context: http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26719470.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>

Re: Jersey No Longer Supported?

Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Dec 10, 2009 at 12:16 AM, mumbly <mc...@gmail.com> wrote:
>
> So I finally took a look at web-console. It looks to me like it is not a
> component, per se, but a utility that happens to use Jersey. At least, I
> don't see it on the components page and the web-console.html page does not
> sound like a component. I haven't looked at the source code. Is there an
> undocumented component hidden away in there somewhere?
>

Its not as if if a camel-jersey component is lacking its impossible to
use Camel with Jersey. Its both java code after all.
And using Camels ProducerTemplate its very easy to send a message from
java to a Camel route.

We love contribution so if someone is up for the task to try create
such a component that would be cool.



> --Tim
>
>
> cmoulliard wrote:
>>
>> The component http://camel.apache.org/web-console.html has been designed
>> around jersey implementation of JAX-RS
>>
>> As you mention camel-cxf is based on CXF and camel-restlet on RESTlet
>>
>> Regards,
>>
>> Charles Moulliard
>> Senior Enterprise Architect
>> Apache Camel Committer
>>
>> *****************************
>> blog : http://cmoulliard.blogspot.com
>> twitter : http://twitter.com/cmoulliard
>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>
>> Apache Camel Group :
>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>
>>
>> On Fri, Dec 4, 2009 at 5:29 PM, mumbly <mc...@gmail.com> wrote:
>>
>>>
>>> I'm a bit confused as to whether Jersey is currently supported for REST.
>>> I've
>>> seen indications that it was supported at some point from searches I've
>>> made, but it looks like there are only camel-cxf and camel-restlet
>>> components currently in the lineup. Did Jersey support get deprecated?
>>> Was
>>> it never really there?
>>>
>>> Thanks.
>>>
>>> --Tim
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26635942.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>> -----
>> Charles Moulliard
>> SOA Architect
>>
>> My Blog : http://cmoulliard.blogspot.com/
>>
>
> --
> View this message in context: http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26719470.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>



-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Re: Jersey No Longer Supported?

Posted by mumbly <mc...@gmail.com>.
So I finally took a look at web-console. It looks to me like it is not a
component, per se, but a utility that happens to use Jersey. At least, I
don't see it on the components page and the web-console.html page does not
sound like a component. I haven't looked at the source code. Is there an
undocumented component hidden away in there somewhere?

--Tim


cmoulliard wrote:
> 
> The component http://camel.apache.org/web-console.html has been designed
> around jersey implementation of JAX-RS
> 
> As you mention camel-cxf is based on CXF and camel-restlet on RESTlet
> 
> Regards,
> 
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
> 
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> 
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
> 
> 
> On Fri, Dec 4, 2009 at 5:29 PM, mumbly <mc...@gmail.com> wrote:
> 
>>
>> I'm a bit confused as to whether Jersey is currently supported for REST.
>> I've
>> seen indications that it was supported at some point from searches I've
>> made, but it looks like there are only camel-cxf and camel-restlet
>> components currently in the lineup. Did Jersey support get deprecated?
>> Was
>> it never really there?
>>
>> Thanks.
>>
>> --Tim
>> --
>> View this message in context:
>> http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26635942.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
> 
> 
> -----
> Charles Moulliard
> SOA Architect
> 
> My Blog : http://cmoulliard.blogspot.com/  
> 

-- 
View this message in context: http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26719470.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Jersey No Longer Supported?

Posted by Charles Moulliard <cm...@gmail.com>.
The component http://camel.apache.org/web-console.html has been designed
around jersey implementation of JAX-RS

As you mention camel-cxf is based on CXF and camel-restlet on RESTlet

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard

Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm


On Fri, Dec 4, 2009 at 5:29 PM, mumbly <mc...@gmail.com> wrote:

>
> I'm a bit confused as to whether Jersey is currently supported for REST.
> I've
> seen indications that it was supported at some point from searches I've
> made, but it looks like there are only camel-cxf and camel-restlet
> components currently in the lineup. Did Jersey support get deprecated? Was
> it never really there?
>
> Thanks.
>
> --Tim
> --
> View this message in context:
> http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26635942.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>