Re: Handling error per endpoint

[Christian Müller]

Why will onException per route not work for you?

Best,
Christian
Am 29.09.2014 15:04 schrieb "Aryan" :

> Hi All,
>
> We have a camel route and we want to handle exceptions per endpoint. For
> example, if the exception is thrown from processor A, we want A number of
> retries, if thrown from processor B, we want B number of retries and so on.
>
> We can handle the exception using doTry and throw our customized exception
> per endpoint and then apply different number or retries using OnException.
> Not sure if it is the best approach though. Camel allows exceptions
> policies
> to be applied per route and per context, is it possible to configure it per
> endpoint? Please advice. Or is there any other clean way to do it.
>
> Thanks!
> Aryan
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Handling-error-per-endpoint-tp5757191.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Re: Camel 2.14.0 XSD

[Willem Jiang]

Hi,
You can find the camel-2.14.0 xsd here[1], there some new added REST DSL 
definitions.
[1]http://camel.apache.org/schema/spring/camel-spring-2.14.0.xsd


--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On September 30, 2014 at 4:26:31 AM, Max Bridgewater 
(max.bridgewa...@gmail.com) wrote:
> Hi,
>  
> Could it be that the Camel XSD has not been updated to support Camel
> 2.14.0? I am not sure if I can see REST DSL constructs in the XSD yet.
>  
> Regards,
> Max.
>  

Camel Restlet with Swagger

[Max Bridgewater]

HI,

Has anybody used camel-restlet component with camel-swagger? How would the
web.xml look?

Alternately, is there a way to use the Restlet Swagger extension with Camel?

Thanks,
Max.

Re: RestBindingProcessor JSON Data Format Config

[sohrab]

Raised https://issues.apache.org/jira/browse/CAMEL-7880

BTW would the above fix work when there are multiple HTTP resources,
each with their own distinct unmarshalType? i.e. we don't want the one
resource configuration be blown away by the next one. Is this starting
to sound like a VerbDefinition-level config for jsonDataFormat?

On Tue, Sep 30, 2014 at 1:52 AM, Babak Vahdat [via Camel]
 wrote:
>
>> Am 29.09.2014 um 17:39 schrieb Claus Ibsen <[hidden email]>:
>>
>> Hi
>>
>> Yeah we should likely improve the code to cater for when people use
>> custom data formats. Surely most needed for json, as jaxb is well just
>> jaxb using camel-jaxb.
>>
>> The naming should likely just be
>>
>> "json"
>> "json-out"
>> "xml"
>> "xml-out"
>>
>> so in is implied, eg so you only use -out if you really need to
>> configure it differently.
>>
>
> Yeah that naming of yours makes definitley much more sense, thanks!
>
> Sohrab, please go ahead and raise a JIRA ticket pointing to this thread in
> Nabble.
>
> Babak
>
> Sent from my iPhone...
>
>> On Mon, Sep 29, 2014 at 4:36 PM, Babak Vahdat
>> <[hidden email]> wrote:
>>> Yeah I see your point. BTW the same shortcoming is also given for the
>>> case
>>> where binding is XML and not Json, which's the JAXB dataformat being
>>> currently supported. So I guess in cases likes yours we need to
>>> differentiate the DataFormats for the incomming/outgoing playloads, let’s
>>> say something like:
>>>
>>> "json-in"
>>> "json-out"
>>> "xml-in"
>>> "xml-out"
>>>
>>> @Claus how to you see this? Does this make sense to you?
>>>
>>> Babak
>>>
>>> sohrab wrote
 Thanks for the explanation, Babak.

 I think I see a flaw with this which will break anytime someone uses a
 custom DataFormat in REST DSL.

 Say I define a custom JacksonDataFormat in the registry (quite a
 common thing to do especially if you want to enable/disable config on
 ObjectMapper) and point to it in RestConfiguration.jsonDataFormat.

 As you said if it's not the default "json-jackson", those two lines
 will return the same object which will then get configured twice, with
 "outJson" config blowing away any config "json" made previously.

 I just replicated this with a small example where REST DSL will reject
 incoming request if it doesn't have the response structure(!). Should
 I raise this in JIRA?

 On Mon, Sep 29, 2014 at 8:33 PM, Babak Vahdat [via Camel]
 <
>>>
 ml-node+s465427n5757186h47@.nabble
>>>
 > wrote:
> Hi,
>
> The "json" and "outJson" variables you mentioned will *not* resolve to
> the
> same Java object (because of Camel Injector being invoked here behind
> the
> scenes while resolving), well almost always ... depending if e.g. an
> object
> under the name "json-jackson" is already bound to the Camel registery
> which
> isn't really typical. The following code snippet should make both cases
> clear to you:
>
>CamelContext context = new DefaultCamelContext();
>
>DataFormat first = context.resolveDataFormat("json-jackson");
>DataFormat second = context.resolveDataFormat("json-jackson");
>
>System.out.println(first != second); // true
>
>JndiRegistry registry = new JndiRegistry();
>registry.bind("json-jackson", new
> org.apache.camel.component.jackson.JacksonDataFormat());
>((DefaultCamelContext) context).setRegistry(registry);
>
>DataFormat third = context.resolveDataFormat("json-jackson");
>DataFormat fourth = context.resolveDataFormat("json-jackson");
>
>System.out.println(third == fourth); // true
>
>System.out.println(third != first); // true
>System.out.println(fourth != first); // true
>
> If interested, looking into the different implementations of Camel’s
> DataFormatResolver should clarify this to you, specially the
> DefaultDataFormatResolver one.
>
> Babak
>
> sohrab wrote
> I was just looking through the latest code for
> org.apache.camel.model.rest.RestBindingDefinition and I am not quite
> sure
> how this works so I'd appreciate if someone can explain it to me.
>
> createProcessor() method looks up both JSON data formats using the same
> name:
>
> DataFormat json = context.resolveDataFormat(name);
> DataFormat outJson = context.resolveDataFormat(name);
>
> And further down, it sets the properties for "json" and then "outJson".
> Now
> I am wondering if that name resolves to the same DataFormat object
> (especially when you have RestConfiguration.jsonDataFormat set), what
> stops
> setting "outJson" properties, such as unmarshalType, not overriding the
> properties we just set for "json"?
>
>
>
> 
> If you reply to this email, your message will

Camel 2.14.0 XSD

[Max Bridgewater]

Hi,

Could it be that the Camel XSD has not been updated to support Camel
2.14.0? I am not sure if I can see REST DSL constructs in the XSD yet.

Regards,
Max.

Using file URI's correctly

[condreynl]

I have a simple route for doing file normalization tasks. I have a working
version that goes something like:

myRoute extends RouteBuilder(){
configure(){
from("direct:normalize").process().to("file:filePath?fileName=theFileName");
}}

I have a class that has a CamelContext variable. The implementation looks
just like what I found in the documentation:

CamelContext context = new DefaultCamelContext();
context.addRoutes(new myRoute());
File myFile = new File("filepath");

context.start();
context.createProducerTemplate("direct:normalize",myFile)

Whenever I replace direct:normalize with a file URI, nothing happens. The
console tells me that the route has begun consuming from the file endpoint,
but then immediately disconnects without running the route. For example, my
configure method looks like:
 
from(file URI).process().to(file URI)

and my context class looks like

//initialize context to default 
context.addRoutes(new myRoute);
context.start();

Have I used the file URI's correctly? Here is an example of one:
from(file:/home/usrName/Documents?fileName=theFileName.txt&fileExist=Append




--
View this message in context: 
http://camel.465427.n5.nabble.com/Using-file-URI-s-correctly-tp5757208.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel CXF Jaxrs service implementation class's methods are not executing

[Sergey Beryozkin]

Hi,
a CXF RS Blueprint extension is available (resourceClass attribute) that 
can be used to have only the interface supporting the endpoint, I did 
not use it but Yuhan showed it to me and it looked very cool


Cheers, Sergey
On 29/09/14 08:15, vrahul wrote:

Thanks Jiang,
I understand why control should not go to service impl. But now my concern
is why we need to write the impl class at all. As in below example I have
create a web service called FeatureService, and in cxf:rsServer tag's
serviceClass attribute we need to pass the above FeatureService's
implementation.

http://{{esb.feature.service.host}}:{{esb.feature.service.port}}/featureService";
serviceClass="com.test.esb.service.flm.FeatureServiceImpl"
loggingSizeLimit="30" >
   
   
  


Where FeatureServiceImpl implements the FeatureSerivce(Rest service)
interface. Is it possible to omit the need of FeatureServiceImpl when we use
cxf with camel. Please share your thoughts on this.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-CXF-Jaxrs-service-implementation-class-s-methods-are-not-executing-tp5749733p5757174.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Camel JMS XA Transaction with Bitronix - Problem/Question

[mattmadhavan]

Hello,
I have configured JTA transactions using  Bitronix and I have used this
configurations for many years for testing my applications outside the  J2EE
container.

Now I am trying to test a simple JMS route using "transacted" attribute as
follows!



I am getting the following error!

*bitronix.tm.internal.BitronixSystemException: resource 'activemq' cannot be
used outside XA transaction scope. Set allowLocalTransactions to true if you
want to allow this and you know your resource supports this.*

I am forced to use the following property in my AMQ connection factory
configuration to get rid of the exception.

**

Questions are:
1) Does Camel by default start a Non XA Transaction when there is only one
Resource (JMS) in the route?
2) If so, how do I force Camel to always start XA Transaction?

I appreciate in advance!

Thanks
Matt'M








-
Thanks
Matt G. Madhavan
--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-JMS-XA-Transaction-with-Bitronix-Problem-Question-tp5757206.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: RestBindingProcessor JSON Data Format Config

[Babak Vahdat]

> Am 29.09.2014 um 17:39 schrieb Claus Ibsen :
> 
> Hi
> 
> Yeah we should likely improve the code to cater for when people use
> custom data formats. Surely most needed for json, as jaxb is well just
> jaxb using camel-jaxb.
> 
> The naming should likely just be
> 
> "json"
> "json-out"
> "xml"
> "xml-out"
> 
> so in is implied, eg so you only use -out if you really need to
> configure it differently.
> 

Yeah that naming of yours makes definitley much more sense, thanks!

Sohrab, please go ahead and raise a JIRA ticket pointing to this thread in 
Nabble.

Babak

Sent from my iPhone...

> On Mon, Sep 29, 2014 at 4:36 PM, Babak Vahdat
>  wrote:
>> Yeah I see your point. BTW the same shortcoming is also given for the case
>> where binding is XML and not Json, which's the JAXB dataformat being
>> currently supported. So I guess in cases likes yours we need to
>> differentiate the DataFormats for the incomming/outgoing playloads, let’s
>> say something like:
>> 
>> "json-in"
>> "json-out"
>> "xml-in"
>> "xml-out"
>> 
>> @Claus how to you see this? Does this make sense to you?
>> 
>> Babak
>> 
>> sohrab wrote
>>> Thanks for the explanation, Babak.
>>> 
>>> I think I see a flaw with this which will break anytime someone uses a
>>> custom DataFormat in REST DSL.
>>> 
>>> Say I define a custom JacksonDataFormat in the registry (quite a
>>> common thing to do especially if you want to enable/disable config on
>>> ObjectMapper) and point to it in RestConfiguration.jsonDataFormat.
>>> 
>>> As you said if it's not the default "json-jackson", those two lines
>>> will return the same object which will then get configured twice, with
>>> "outJson" config blowing away any config "json" made previously.
>>> 
>>> I just replicated this with a small example where REST DSL will reject
>>> incoming request if it doesn't have the response structure(!). Should
>>> I raise this in JIRA?
>>> 
>>> On Mon, Sep 29, 2014 at 8:33 PM, Babak Vahdat [via Camel]
>>> <
>> 
>>> ml-node+s465427n5757186h47@.nabble
>> 
>>> > wrote:
 Hi,
 
 The "json" and "outJson" variables you mentioned will *not* resolve to
 the
 same Java object (because of Camel Injector being invoked here behind the
 scenes while resolving), well almost always ... depending if e.g. an
 object
 under the name "json-jackson" is already bound to the Camel registery
 which
 isn't really typical. The following code snippet should make both cases
 clear to you:
 
CamelContext context = new DefaultCamelContext();
 
DataFormat first = context.resolveDataFormat("json-jackson");
DataFormat second = context.resolveDataFormat("json-jackson");
 
System.out.println(first != second); // true
 
JndiRegistry registry = new JndiRegistry();
registry.bind("json-jackson", new
 org.apache.camel.component.jackson.JacksonDataFormat());
((DefaultCamelContext) context).setRegistry(registry);
 
DataFormat third = context.resolveDataFormat("json-jackson");
DataFormat fourth = context.resolveDataFormat("json-jackson");
 
System.out.println(third == fourth); // true
 
System.out.println(third != first); // true
System.out.println(fourth != first); // true
 
 If interested, looking into the different implementations of Camel’s
 DataFormatResolver should clarify this to you, specially the
 DefaultDataFormatResolver one.
 
 Babak
 
 sohrab wrote
 I was just looking through the latest code for
 org.apache.camel.model.rest.RestBindingDefinition and I am not quite sure
 how this works so I'd appreciate if someone can explain it to me.
 
 createProcessor() method looks up both JSON data formats using the same
 name:
 
 DataFormat json = context.resolveDataFormat(name);
 DataFormat outJson = context.resolveDataFormat(name);
 
 And further down, it sets the properties for "json" and then "outJson".
 Now
 I am wondering if that name resolves to the same DataFormat object
 (especially when you have RestConfiguration.jsonDataFormat set), what
 stops
 setting "outJson" properties, such as unmarshalType, not overriding the
 properties we just set for "json"?
 
 
 
 
 If you reply to this email, your message will be added to the discussion
 below:
 http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103p5757186.html
 To unsubscribe from RestBindingProcessor JSON Data Format Config, click
 here.
 NAML
>> 
>> 
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103p5757201.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
> 
> 
> 
> -- 
> Claus Ibsen
> -
> Red Hat, Inc.
> Emai

Re: RestBindingProcessor JSON Data Format Config

[Claus Ibsen]

Hi

Yeah we should likely improve the code to cater for when people use
custom data formats. Surely most needed for json, as jaxb is well just
jaxb using camel-jaxb.

The naming should likely just be

"json"
"json-out"
"xml"
"xml-out"

so in is implied, eg so you only use -out if you really need to
configure it differently.

On Mon, Sep 29, 2014 at 4:36 PM, Babak Vahdat
 wrote:
> Yeah I see your point. BTW the same shortcoming is also given for the case
> where binding is XML and not Json, which's the JAXB dataformat being
> currently supported. So I guess in cases likes yours we need to
> differentiate the DataFormats for the incomming/outgoing playloads, let’s
> say something like:
>
> "json-in"
> "json-out"
> "xml-in"
> "xml-out"
>
> @Claus how to you see this? Does this make sense to you?
>
> Babak
>
> sohrab wrote
>> Thanks for the explanation, Babak.
>>
>> I think I see a flaw with this which will break anytime someone uses a
>> custom DataFormat in REST DSL.
>>
>> Say I define a custom JacksonDataFormat in the registry (quite a
>> common thing to do especially if you want to enable/disable config on
>> ObjectMapper) and point to it in RestConfiguration.jsonDataFormat.
>>
>> As you said if it's not the default "json-jackson", those two lines
>> will return the same object which will then get configured twice, with
>> "outJson" config blowing away any config "json" made previously.
>>
>> I just replicated this with a small example where REST DSL will reject
>> incoming request if it doesn't have the response structure(!). Should
>> I raise this in JIRA?
>>
>> On Mon, Sep 29, 2014 at 8:33 PM, Babak Vahdat [via Camel]
>> <
>
>> ml-node+s465427n5757186h47@.nabble
>
>> > wrote:
>>> Hi,
>>>
>>> The "json" and "outJson" variables you mentioned will *not* resolve to
>>> the
>>> same Java object (because of Camel Injector being invoked here behind the
>>> scenes while resolving), well almost always ... depending if e.g. an
>>> object
>>> under the name "json-jackson" is already bound to the Camel registery
>>> which
>>> isn't really typical. The following code snippet should make both cases
>>> clear to you:
>>>
>>> CamelContext context = new DefaultCamelContext();
>>>
>>> DataFormat first = context.resolveDataFormat("json-jackson");
>>> DataFormat second = context.resolveDataFormat("json-jackson");
>>>
>>> System.out.println(first != second); // true
>>>
>>> JndiRegistry registry = new JndiRegistry();
>>> registry.bind("json-jackson", new
>>> org.apache.camel.component.jackson.JacksonDataFormat());
>>> ((DefaultCamelContext) context).setRegistry(registry);
>>>
>>> DataFormat third = context.resolveDataFormat("json-jackson");
>>> DataFormat fourth = context.resolveDataFormat("json-jackson");
>>>
>>> System.out.println(third == fourth); // true
>>>
>>> System.out.println(third != first); // true
>>> System.out.println(fourth != first); // true
>>>
>>> If interested, looking into the different implementations of Camel’s
>>> DataFormatResolver should clarify this to you, specially the
>>> DefaultDataFormatResolver one.
>>>
>>> Babak
>>>
>>> sohrab wrote
>>> I was just looking through the latest code for
>>> org.apache.camel.model.rest.RestBindingDefinition and I am not quite sure
>>> how this works so I'd appreciate if someone can explain it to me.
>>>
>>> createProcessor() method looks up both JSON data formats using the same
>>> name:
>>>
>>> DataFormat json = context.resolveDataFormat(name);
>>> DataFormat outJson = context.resolveDataFormat(name);
>>>
>>> And further down, it sets the properties for "json" and then "outJson".
>>> Now
>>> I am wondering if that name resolves to the same DataFormat object
>>> (especially when you have RestConfiguration.jsonDataFormat set), what
>>> stops
>>> setting "outJson" properties, such as unmarshalType, not overriding the
>>> properties we just set for "json"?
>>>
>>>
>>>
>>> 
>>> If you reply to this email, your message will be added to the discussion
>>> below:
>>> http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103p5757186.html
>>> To unsubscribe from RestBindingProcessor JSON Data Format Config, click
>>> here.
>>> NAML
>
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103p5757201.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Re: No component found with schema: jms

[Claus Ibsen]

On Mon, Sep 29, 2014 at 11:56 AM, Anjenson  wrote:
> Hi
>
> I have tried to switch to ActiveMQ just as shown in camel spring-jms
> example. However, it didn't help.
> Can this be due to the fact that I didn't use features.xml?

features.xml is when you use OSGi such as Apache Karaf / ServiceMix /
JBoss Fuse etc.

You can run Camel in a standalone ActiveMQ also.



>
> 2014-09-29 11:33 GMT+03:00 Claus Ibsen-2 [via Camel] <
> ml-node+s465427n5757182...@n5.nabble.com>:
>
>> When you use Spring, eg define  in a spring xml file,
>> then you define it the usual spring way - whatever ways you can do in
>> Spring.
>>
>> Camel just lookup in the spring application context to find the beans.
>> - in this case lookup by name, to fine a bean with name "jms" etc.
>>
>>
>> On Mon, Sep 29, 2014 at 10:17 AM, Anjenson <[hidden email]
>> > wrote:
>>
>> > Hi
>> >
>> > I have went through many examples but they usually are the same. But I
>> have
>> > noticed that when initializing  connection in code we also need to add a
>> > component to context.
>> > Could you, please, explain how to do that in xml file?
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://camel.465427.n5.nabble.com/No-component-found-with-schema-jms-tp5757069p5757181.html
>> > Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> Red Hat, Inc.
>> Email: [hidden email]
>> 
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>> hawtio: http://hawt.io/
>> fabric8: http://fabric8.io/
>>
>>
>> --
>>  If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://camel.465427.n5.nabble.com/No-component-found-with-schema-jms-tp5757069p5757182.html
>>  To unsubscribe from No component found with schema: jms, click here
>> 
>> .
>> NAML
>> 
>>
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/No-component-found-with-schema-jms-tp5757069p5757185.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Re: How catch exception from endpoint which was created in code

[ReDiya]

dariusz.skrudlik, 

Did you find a way to return the Exception back to the bean ? Please share
the same. 

regards
ReDiya



--
View this message in context: 
http://camel.465427.n5.nabble.com/How-catch-exception-from-endpoint-which-was-created-in-code-tp5737037p5757202.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: RestBindingProcessor JSON Data Format Config

[Babak Vahdat]

Yeah I see your point. BTW the same shortcoming is also given for the case
where binding is XML and not Json, which's the JAXB dataformat being
currently supported. So I guess in cases likes yours we need to
differentiate the DataFormats for the incomming/outgoing playloads, let’s
say something like:

"json-in" 
"json-out"
"xml-in"
"xml-out"

@Claus how to you see this? Does this make sense to you?

Babak

sohrab wrote
> Thanks for the explanation, Babak.
> 
> I think I see a flaw with this which will break anytime someone uses a
> custom DataFormat in REST DSL.
> 
> Say I define a custom JacksonDataFormat in the registry (quite a
> common thing to do especially if you want to enable/disable config on
> ObjectMapper) and point to it in RestConfiguration.jsonDataFormat.
> 
> As you said if it's not the default "json-jackson", those two lines
> will return the same object which will then get configured twice, with
> "outJson" config blowing away any config "json" made previously.
> 
> I just replicated this with a small example where REST DSL will reject
> incoming request if it doesn't have the response structure(!). Should
> I raise this in JIRA?
> 
> On Mon, Sep 29, 2014 at 8:33 PM, Babak Vahdat [via Camel]
> <

> ml-node+s465427n5757186h47@.nabble

> > wrote:
>> Hi,
>>
>> The "json" and "outJson" variables you mentioned will *not* resolve to
>> the
>> same Java object (because of Camel Injector being invoked here behind the
>> scenes while resolving), well almost always ... depending if e.g. an
>> object
>> under the name "json-jackson" is already bound to the Camel registery
>> which
>> isn't really typical. The following code snippet should make both cases
>> clear to you:
>>
>> CamelContext context = new DefaultCamelContext();
>>
>> DataFormat first = context.resolveDataFormat("json-jackson");
>> DataFormat second = context.resolveDataFormat("json-jackson");
>>
>> System.out.println(first != second); // true
>>
>> JndiRegistry registry = new JndiRegistry();
>> registry.bind("json-jackson", new
>> org.apache.camel.component.jackson.JacksonDataFormat());
>> ((DefaultCamelContext) context).setRegistry(registry);
>>
>> DataFormat third = context.resolveDataFormat("json-jackson");
>> DataFormat fourth = context.resolveDataFormat("json-jackson");
>>
>> System.out.println(third == fourth); // true
>>
>> System.out.println(third != first); // true
>> System.out.println(fourth != first); // true
>>
>> If interested, looking into the different implementations of Camel’s
>> DataFormatResolver should clarify this to you, specially the
>> DefaultDataFormatResolver one.
>>
>> Babak
>>
>> sohrab wrote
>> I was just looking through the latest code for
>> org.apache.camel.model.rest.RestBindingDefinition and I am not quite sure
>> how this works so I'd appreciate if someone can explain it to me.
>>
>> createProcessor() method looks up both JSON data formats using the same
>> name:
>>
>> DataFormat json = context.resolveDataFormat(name);
>> DataFormat outJson = context.resolveDataFormat(name);
>>
>> And further down, it sets the properties for "json" and then "outJson".
>> Now
>> I am wondering if that name resolves to the same DataFormat object
>> (especially when you have RestConfiguration.jsonDataFormat set), what
>> stops
>> setting "outJson" properties, such as unmarshalType, not overriding the
>> properties we just set for "json"?
>>
>>
>>
>> 
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103p5757186.html
>> To unsubscribe from RestBindingProcessor JSON Data Format Config, click
>> here.
>> NAML





--
View this message in context: 
http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103p5757201.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel's Swagger vs. Spring MVC Swagger

[Claus Ibsen]

On Sun, Sep 28, 2014 at 6:40 PM, Matt Raible  wrote:
> On Fri, Sep 26, 2014 at 1:48 AM, Claus Ibsen  wrote:
>
>> Hi
>>
>> On Thu, Sep 25, 2014 at 11:23 PM, Matt Raible 
>> wrote:
>> > Hey all,
>> >
>> > I'm starting to develop a new application and I'm researching using
>> Camel's REST DSL vs. Spring Boot and it's REST support. The last
>> application I wrote used Apache Camel + Spring Boot, but I only used the
>> external properties support from Boot. For this new application, I have a
>> skeleton of the previous project. The new project needs to do REST
>> (XML-based). Looking at a HelloWorld example in Spring MVC vs. Camel, I'm
>> leaning towards using Spring MVC.
>> >
>> > Camel
>> > 
>> > @Component
>> > public class HelloWorldRoute extends RouteBuilder {
>> > @Override
>> > public void configure() throws Exception {
>> > // servlet is configured in Application.java
>> >
>>  restConfiguration().component("servlet").bindingMode(RestBindingMode.json);
>> >
>> > rest("/say")
>> > .get("/hello")
>> > .to("direct:talk");
>> > from("direct:talk")
>> > .process(exchange -> {
>> > HelloWorld hw =
>> HelloWorld.builder().message("Howdy World!").build();
>> > exchange.getIn().setBody(hw);
>> > });
>> > }
>> > }
>> >
>>
>> Now its only a hello world, but you can embed the route in the rest
>> dsl directly, if you want, so its shorter
>>
>>
>>  rest("/say")
>>  .get("/hello")
>>  .route().transform(constant("Hello
>> World"));
>>
>
> Good to know. Is it possible to return an object with the REST DSL or only
> constants?
>

Yeah you can return anything you want. A constant refers to a java
instance, so it can be anything really, in the example above its a
String, eg "xxx".

If the rest component of choice support the type, then you can just
use that, eg a JAX-RS Response instance etc.

As when you use .route() you can do all the Camel routing you want,
you can also call java beans, content based routing, recipient list,
or whatever.



>
>>
>> >
>> > Spring MVC
>> > 
>> > @RestController
>> > @Api("Hello")
>> > public class HelloWorldController {
>> >
>> > @RequestMapping(value = "/api/hello", method = RequestMethod.GET)
>> > public HelloWorld sayHello() {
>> > return HelloWorld.builder().message("Hello
>> World").build();
>> > }
>> > }
>> >
>> >
>> > I was able to get Swagger working for both services, albeit with
>> different endpoints. One issue I found is that the "base.path" has to be
>> configured or calling the methods by clicking on buttons in Swagger UI
>> doesn't work. With Spring Boot, I'm able to configure Swagger with the
>> following:
>> >
>> > @Configuration
>> > @EnableSwagger
>> > public class SwaggerConfig implements EnvironmentAware {
>> > public static final String DEFAULT_INCLUDE_PATTERN = "/api/.*";
>> >
>> > private RelaxedPropertyResolver propertyResolver;
>> >
>> > @Override
>> > public void setEnvironment(Environment environment) {
>> > this.propertyResolver = new
>> RelaxedPropertyResolver(environment, "swagger.");
>> > }
>> >
>> > /**
>> >  * Swagger Spring MVC configuration
>> >  */
>> > @Bean
>> > public SwaggerSpringMvcPlugin
>> swaggerSpringMvcPlugin(SpringSwaggerConfig springSwaggerConfig) {
>> > return new SwaggerSpringMvcPlugin(springSwaggerConfig)
>> > .apiInfo(apiInfo())
>> >
>>  .genericModelSubstitutes(ResponseEntity.class)
>> >
>>  .includePatterns(DEFAULT_INCLUDE_PATTERN);
>> > }
>> >
>> > /**
>> >  * API Info as it appears on the swagger-ui page
>> >  */
>> > private ApiInfo apiInfo() {
>> > return new ApiInfo(
>> > propertyResolver.getProperty("title"),
>> >
>>  propertyResolver.getProperty("description"),
>> >
>>  propertyResolver.getProperty("termsOfServiceUrl"),
>> > propertyResolver.getProperty("contact"),
>> > propertyResolver.getProperty("license"),
>> >
>>  propertyResolver.getProperty("licenseUrl"));
>> > }
>> > }
>> >
>> > With Camel, it's a bit less code, but if I don't override the
>> "base.path", it defaults to localhost:8080. The Spring MVC Swagger
>> implementation figures out the correct base path on its own.
>> >
>> > /**
>> >  * Swagger Camel Configuration
>> >  */
>> > @Bean
>> > public ServletRegistrationBean swaggerServlet() {
>> > ServletRegistrationBean swagger = new
>> ServletRegistrationBean(new

Handling error per endpoint

[Aryan]

Hi All,

We have a camel route and we want to handle exceptions per endpoint. For
example, if the exception is thrown from processor A, we want A number of
retries, if thrown from processor B, we want B number of retries and so on.

We can handle the exception using doTry and throw our customized exception
per endpoint and then apply different number or retries using OnException.
Not sure if it is the best approach though. Camel allows exceptions policies
to be applied per route and per context, is it possible to configure it per
endpoint? Please advice. Or is there any other clean way to do it.

Thanks!
Aryan



--
View this message in context: 
http://camel.465427.n5.nabble.com/Handling-error-per-endpoint-tp5757191.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: RestBindingProcessor JSON Data Format Config

[sohrab]

Thanks for the explanation, Babak.

I think I see a flaw with this which will break anytime someone uses a
custom DataFormat in REST DSL.

Say I define a custom JacksonDataFormat in the registry (quite a
common thing to do especially if you want to enable/disable config on
ObjectMapper) and point to it in RestConfiguration.jsonDataFormat.

As you said if it's not the default "json-jackson", those two lines
will return the same object which will then get configured twice, with
"outJson" config blowing away any config "json" made previously.

I just replicated this with a small example where REST DSL will reject
incoming request if it doesn't have the response structure(!). Should
I raise this in JIRA?

On Mon, Sep 29, 2014 at 8:33 PM, Babak Vahdat [via Camel]
 wrote:
> Hi,
>
> The "json" and "outJson" variables you mentioned will *not* resolve to the
> same Java object (because of Camel Injector being invoked here behind the
> scenes while resolving), well almost always ... depending if e.g. an object
> under the name "json-jackson" is already bound to the Camel registery which
> isn't really typical. The following code snippet should make both cases
> clear to you:
>
> CamelContext context = new DefaultCamelContext();
>
> DataFormat first = context.resolveDataFormat("json-jackson");
> DataFormat second = context.resolveDataFormat("json-jackson");
>
> System.out.println(first != second); // true
>
> JndiRegistry registry = new JndiRegistry();
> registry.bind("json-jackson", new
> org.apache.camel.component.jackson.JacksonDataFormat());
> ((DefaultCamelContext) context).setRegistry(registry);
>
> DataFormat third = context.resolveDataFormat("json-jackson");
> DataFormat fourth = context.resolveDataFormat("json-jackson");
>
> System.out.println(third == fourth); // true
>
> System.out.println(third != first); // true
> System.out.println(fourth != first); // true
>
> If interested, looking into the different implementations of Camel’s
> DataFormatResolver should clarify this to you, specially the
> DefaultDataFormatResolver one.
>
> Babak
>
> sohrab wrote
> I was just looking through the latest code for
> org.apache.camel.model.rest.RestBindingDefinition and I am not quite sure
> how this works so I'd appreciate if someone can explain it to me.
>
> createProcessor() method looks up both JSON data formats using the same
> name:
>
> DataFormat json = context.resolveDataFormat(name);
> DataFormat outJson = context.resolveDataFormat(name);
>
> And further down, it sets the properties for "json" and then "outJson". Now
> I am wondering if that name resolves to the same DataFormat object
> (especially when you have RestConfiguration.jsonDataFormat set), what stops
> setting "outJson" properties, such as unmarshalType, not overriding the
> properties we just set for "json"?
>
>
>
> 
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103p5757186.html
> To unsubscribe from RestBindingProcessor JSON Data Format Config, click
> here.
> NAML




--
View this message in context: 
http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103p5757190.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Unable to fetch Email attachments or Multipart content using Camel-Mail in FuseESB / OSGI

[thigales]

I have created an osgi bundle with a pop3 camel route for reading mails. When
deployed in servicemix 5.1, the attachments are getting read properly as
expected.

However, the same bundle gives problem in FuseEsb-7.1.0.fuse-047-1_2013. The
contents of message available from within camel exchange(in the code snippet
below, the variable contentObject) are appearing as of type
'SharedByteArrayInputStream' rather than 'javax.mail.Multipart'.

I Have googled a lot and found posts mentioning a related problem which is
caused by javax.activation being loaded by different classloader than
javax.mail. Seems like javax.activation needs to read META-INF/mailcap from
the javamail artifact but it can't see it. Recent versions of javax.mail
seems to have fixed the MAINFEST to include mailcap, but it still seems to
occur with FuseESB.

ServiceMix configuration :

Servicemix version=5.1
Camel-mail=2.13.2
Camel-core=2.13.2
javax.mail=Java7
Javax.activation=Java7
FuseEsb configuration :

FuseESB version=7.1.0
Camel.mail=2.10.0.fuse-71-047
Camel-core=2.10.0.fuse-71-047
Javax.mail=Java7
javax.activation=Java7
Can anyone please help me to resolve this issue ? Below are the code snippet
to read the mail and the camel route. Please let me know if any further
information is required to debug the problem. Thanks.

Code snippet:

package test.mail.attachment;

import javax.mail.BodyPart;
import javax.mail.Multipart;
import javax.mail.Part;
import javax.mail.internet.MimeMessage;

import org.apache.camel.Exchange;
import org.apache.camel.Processor;

public class MyProcessor implements Processor {

 public void process(Exchange exchange) throws Exception {

  String result = null;
  javax.mail.Message message = exchange.getIn().getBody(
javax.mail.Message.class);

  if (message instanceof MimeMessage) {

   MimeMessage m = (MimeMessage) message;
   Object contentObject = m.getContent();

   if (contentObject instanceof Multipart) {

Multipart content = (Multipart) contentObject;
int count = content.getCount();

for (int i = 0; i < count; i++) {

 BodyPart part = content.getBodyPart(i);
 System.out.println(part.getContentType());

 if (part.isMimeType("text/plain")) {
  result = (String) part.getContent();
  break;
 } 
 else 
 if (part.isMimeType("text/html")) {
  result = (String) part.getContent();

 } 
 else
 if (part.isMimeType("multipart/alternative")) {

  Multipart mp = (Multipart) part.getContent();
  String text = null;

  for (int i1 = 0; i1 < mp.getCount(); i1++) {

   Part bp = mp.getBodyPart(i);
   if (bp.isMimeType("text/plain")) {

if (text == null) {
 result = (String) bp.getContent();
 break;
}

   } else if (bp.isMimeType("text/html")) {
result = (String) bp.getContent();
   }
  }
 }
}
   }
   else
   if(contentObject instanceof String)  {// a simple text message
result = (String) contentObject;
   } 
   else { 
// not a mime message
// logger.log(Level.WARNING,"notme part or multipart
{0}",message.toString());
result = null;
   }

   System.out.println(result);
  }
 }
}
Camel Route Code


http://www.springframework.org/schema/beans";
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:osgi="http://www.springframework.org/schema/osgi";
 xmlns:tx="http://www.springframework.org/schema/tx";
xmlns:context="http://www.springframework.org/schema/context";
 xmlns:camel="http://camel.apache.org/schema/spring";
xmlns:util="http://www.springframework.org/schema/util";
 xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
 http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
 http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx-3.0.xsd 
  http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
  http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
  http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
  http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd";>

 http://camel.apache.org/schema/spring";>

  


   
   
   
  

 

 




--
View this message in context: 
http://camel.465427.n5.nabble.com/Unable-to-fetch-Email-attachments-or-Multipart-content-using-Camel-Mail-in-FuseESB-OSGI-tp5757189.html
Sent from the Camel - Users mailing list archive at Nabble.com.

sending nearly same message multiple times to same endpoint

[dermoritz]

i have to create a route that sends a message (SOAP) multiple times to same
endpoint. The only difference in message is that one attribute (xml, set) is
different.

At the moment i am using multicast for this:

MulticastDefinition multicast = rtdmProcess.multicast();
// loop over event names to use same data for every target
event
// and send it to rtdm
for (String eventName : rtdmTargetEvents) {
   
multicast.process(rtdmSetNameFactory.get(eventName)).to(rtdmEndpoint);
}
So the endpoint receives the same message multiple times but with different
event names. This seems to work fine with cxf endpoint.
But things get odd if i add "parallelprocessing()" or if i test it with a
MockEndpoint. 
In case of parallelprocessing the mapping of messages and names seem to be
shuffled: if i send 2 messages m1 and m2 and want them to be multicasted to
event name N1 and N2 then m1 will be sent twice to N1 and m2 will be sent
twice to N2.
In case of using MockEndpoint without parallel processing all messages will
only be sent to the second last name set. In this case the set name seems to
be called on the same exchange again and again and not on copies. The second
(and all after) call of set name receives an exchange with the name already
set.
Is this working as intended?
Is there probably a better pattern to be used in this case?



--
View this message in context: 
http://camel.465427.n5.nabble.com/sending-nearly-same-message-multiple-times-to-same-endpoint-tp5757187.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: RestBindingProcessor JSON Data Format Config

[Babak Vahdat]

Hi,

The "json" and "outJson" variables you mentioned will *not* resolve to the
same Java object (because of Camel Injector being invoked here behind the
scenes while resolving), well almost always ... depending if e.g. an object
under the name "json-jackson" is already bound to the Camel registery which
isn't really typical. The following code snippet should make both cases
clear to you:

CamelContext context = new DefaultCamelContext();

DataFormat first = context.resolveDataFormat("json-jackson");
DataFormat second = context.resolveDataFormat("json-jackson");

System.out.println(first != second); // true

JndiRegistry registry = new JndiRegistry();
registry.bind("json-jackson", new
org.apache.camel.component.jackson.JacksonDataFormat());
((DefaultCamelContext) context).setRegistry(registry);

DataFormat third = context.resolveDataFormat("json-jackson");
DataFormat fourth = context.resolveDataFormat("json-jackson");

System.out.println(third == fourth); // true

System.out.println(third != first); // true
System.out.println(fourth != first); // true

If interested, looking into the different implementations of Camel’s
DataFormatResolver should clarify this to you, specially the
DefaultDataFormatResolver one.

Babak 

sohrab wrote
> I was just looking through the latest code for
> org.apache.camel.model.rest.RestBindingDefinition and I am not quite sure
> how this works so I'd appreciate if someone can explain it to me. 
> 
> createProcessor() method looks up both JSON data formats using the same
> name:
> 
> DataFormat json = context.resolveDataFormat(name);
> DataFormat outJson = context.resolveDataFormat(name);
> 
> And further down, it sets the properties for "json" and then "outJson".
> Now I am wondering if that name resolves to the same DataFormat object
> (especially when you have RestConfiguration.jsonDataFormat set), what
> stops setting "outJson" properties, such as unmarshalType, not overriding
> the properties we just set for "json"?





--
View this message in context: 
http://camel.465427.n5.nabble.com/RestBindingProcessor-JSON-Data-Format-Config-tp5757103p5757186.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: No component found with schema: jms

[Anjenson]

Hi

I have tried to switch to ActiveMQ just as shown in camel spring-jms
example. However, it didn't help.
Can this be due to the fact that I didn't use features.xml?

2014-09-29 11:33 GMT+03:00 Claus Ibsen-2 [via Camel] <
ml-node+s465427n5757182...@n5.nabble.com>:

> When you use Spring, eg define  in a spring xml file,
> then you define it the usual spring way - whatever ways you can do in
> Spring.
>
> Camel just lookup in the spring application context to find the beans.
> - in this case lookup by name, to fine a bean with name "jms" etc.
>
>
> On Mon, Sep 29, 2014 at 10:17 AM, Anjenson <[hidden email]
> > wrote:
>
> > Hi
> >
> > I have went through many examples but they usually are the same. But I
> have
> > noticed that when initializing  connection in code we also need to add a
> > component to context.
> > Could you, please, explain how to do that in xml file?
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/No-component-found-with-schema-jms-tp5757069p5757181.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -
> Red Hat, Inc.
> Email: [hidden email]
> 
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> hawtio: http://hawt.io/
> fabric8: http://fabric8.io/
>
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/No-component-found-with-schema-jms-tp5757069p5757182.html
>  To unsubscribe from No component found with schema: jms, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://camel.465427.n5.nabble.com/No-component-found-with-schema-jms-tp5757069p5757185.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Hazelcast queue consumers

[Benoît Liessens]

Hi,

On our project we have been using Hazelcast for a couple of months now and
we are looking to increase usage of Hazelcast with distributed queues. I
was hoping to use Apache Camel to retrieve and process the messages in our
hazelcast cluster. (The camel route would be deployed together with the
hazelcast instance, and you would have as many camel route instances as
hazelcast cluster instances)

I had a closer look at the camel-hazelcast component. When diving into the
source code of the camel-hazelcast module I was very surprised to read the
sources of class HazelcastQueueConsumer: it is implemented as an
ItemListener.

For our clustered environment this would imply that each message would be
processed on each cluster member. Which defeats the point-to-point
messaging model. And even if the messages are processed, they remain on the
queue too.

So basically I wonder what the camel-hazelcast is meant to be used for? Can
anybody explain this implementation?

Also, is it possible to implement our scenario with camel-hazelcast?

Thanks for your help,
Benoit

Re: No component found with schema: jms

[Claus Ibsen]

When you use Spring, eg define  in a spring xml file,
then you define it the usual spring way - whatever ways you can do in
Spring.

Camel just lookup in the spring application context to find the beans.
- in this case lookup by name, to fine a bean with name "jms" etc.


On Mon, Sep 29, 2014 at 10:17 AM, Anjenson  wrote:
> Hi
>
> I have went through many examples but they usually are the same. But I have
> noticed that when initializing  connection in code we also need to add a
> component to context.
> Could you, please, explain how to do that in xml file?
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/No-component-found-with-schema-jms-tp5757069p5757181.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Re: No component found with schema: jms

[Anjenson]

Hi

I have went through many examples but they usually are the same. But I have
noticed that when initializing  connection in code we also need to add a
component to context.
Could you, please, explain how to do that in xml file?



--
View this message in context: 
http://camel.465427.n5.nabble.com/No-component-found-with-schema-jms-tp5757069p5757181.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: No component found with schema: jms

[Claus Ibsen]

Hi

Yeah check the examples and documentation how to work with Camel and spring.


On Mon, Sep 29, 2014 at 9:38 AM, Anjenson  wrote:
> Hi
>
> I have added the following lines inside  in order to initialize camel
> context in xml file (I renamed the file to spring.xml):
>
>  xmlns="http://camel.apache.org/schema/spring";>
> 
> 
>
> I am not sure whether this makes any difference to disable jmxAgent but it
> is done in one of the examples.
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/No-component-found-with-schema-jms-tp5757069p5757177.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Re: No component found with schema: jms

[Anjenson]

Hi

I have added the following lines inside  in order to initialize camel
context in xml file (I renamed the file to spring.xml):

http://camel.apache.org/schema/spring";>

   

I am not sure whether this makes any difference to disable jmxAgent but it
is done in one of the examples.



--
View this message in context: 
http://camel.465427.n5.nabble.com/No-component-found-with-schema-jms-tp5757069p5757177.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel CXF Jaxrs service implementation class's methods are not executing

[vrahul]

Thanks Jiang,
I understand why control should not go to service impl. But now my concern
is why we need to write the impl class at all. As in below example I have
create a web service called FeatureService, and in cxf:rsServer tag's
serviceClass attribute we need to pass the above FeatureService's
implementation. 

http://{{esb.feature.service.host}}:{{esb.feature.service.port}}/featureService";
serviceClass="com.test.esb.service.flm.FeatureServiceImpl"
loggingSizeLimit="30" >
  
 



Where FeatureServiceImpl implements the FeatureSerivce(Rest service)
interface. Is it possible to omit the need of FeatureServiceImpl when we use
cxf with camel. Please share your thoughts on this. 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-CXF-Jaxrs-service-implementation-class-s-methods-are-not-executing-tp5749733p5757174.html
Sent from the Camel - Users mailing list archive at Nabble.com.