Re: Quartz clustering in camel spring DSL - JIRA CAMEL-8076

[selva]

Sorry Willem ,  its typo error I could not copy the row from DB so manually
formed the table format.
*quartZ*  -> small 'z' i.e quartz 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Quartz-clustering-in-camel-spring-DSL-JIRA-CAMEL-8076-tp5759589p5759639.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Multicast with multiple timeouts

[Willem Jiang]

I can reproduce the error, the patch is on the way.

--  
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 November 26, 2014 at 12:19:05 AM, gquintana (gerald.quint...@gmail.com) 
wrote:
> Clean and simple test case:
>  
>  
>  
>  
>  
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Multicast-with-multiple-timeouts-tp5759576p5759596.html
>   
> Sent from the Camel - Users mailing list archive at Nabble.com.
>  

Re: FTP2 consumer (SFTP), using "localWorkDirectory" option - local file not deleted

[fidoedidoe]

Hi Claus

Just to confirm the failure to remove the file from the /tmp/ folder *was*
related to the removal of the file name headers (). To work around this I change my pseudo
configuration that shown below. In summary I just encapsulated the
, smtp, etc into an 
block within the multicast route definition.  I now get a completion email
(without header metadata), while still maintaining the tmp file
(localWorkDirectory=/tmp) is removed when the route / exchange has
completed. 

Many thanks for taking the time and guiding me back onto the right path. 





--
View this message in context: 
http://camel.465427.n5.nabble.com/FTP2-consumer-SFTP-using-localWorkDirectory-option-local-file-not-deleted-tp5759581p5759643.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Multicast with multiple timeouts

[gquintana]

Is there an issue I can follow or should I create one?
Gérald



--
View this message in context: 
http://camel.465427.n5.nabble.com/Multicast-with-multiple-timeouts-tp5759576p5759646.html
Sent from the Camel - Users mailing list archive at Nabble.com.

[Rest DSL] Automatic convertion of body to java.util.Map . How to fix it ?

[Vaïsse-Lesteven Arthur]

Hi every one!

I'm trying to create a RESTful API using the Rest DSL capacity of the
release 2.14.0 of Camel.

My problem currently come from the fact that the body of the Exchange is
automatically casted into a java Map object.

Here come a reduced example (I tried to make it as small as possible...) : 

This is my XML camel context file. It defines a rest API that accept
conection on http://localhost:5117/rest/speakers/{speaker_id} and that
expect HTTP put with a Json object that is serializable into a SpeakerPojo
object.


The java classes that backed this endpoint are:
The SpeakerPojo object:

And the bean used as endpoint :


Finally I use this code to call the restAPI :


These call make the following error to occur:


The message body have automatically transformed into a HashMap. So I tried
to add before the unmarshaller call 
I then got this :

And a parsing error as double quote are now absent due to the double
conversion from string to map and from map to string.

Am I doing something wrong ? Can I dis-activate the auto-casting of the
payload to HashMap ?

Thank in advance!



--
View this message in context: 
http://camel.465427.n5.nabble.com/Rest-DSL-Automatic-convertion-of-body-to-java-util-Map-How-to-fix-it-tp5759648.html
Sent from the Camel - Users mailing list archive at Nabble.com.

How to stop a route from processing get requests continously

[daninovac]

I have the next scenario:

I need to implement something like this:
I have a file.txt with id's
I have splitted those id's by \n and I need to do:
>From file.txt ->
 split-> 
 for each id make a GET request on a url (www.example.com). This url
send to me some JSON ->
 Unmarshal JSON to xml.
That's all.
My ideas & implementation:
   1. route from url to some output (let's say I will put the JSON's in
a folder).
 
 
 
 
  2. route from file.txt to seda
 
 
  
 
 
  3. route from seda:ids to myProcessor
 
 
  
 
  myProcessor just starts the route from where I GET the JSONs

*The problem is*: I need a JSON for each id. One id will have a JSON file.
But the GET is making requests continuously to the url. And I end with a lot
of JSONs instead of the same nr of JSONs as the number of id's.
*How can I stop the 1st route from making requests continously??*
I tought seda will solve it and the nr of requests will be the same number
as the id's from my file, but I'm wrong somehow.

Thanks, guys!



--
View this message in context: 
http://camel.465427.n5.nabble.com/How-to-stop-a-route-from-processing-get-requests-continously-tp5759649.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-netty: no response received from remote server.

[bwest]

Hello, 

I've made some progress with the original question.  I appears that I am
receiving a response as expected.  However, the response isn't in the body. 
So when i do a .log("Message: ${body}) in the route, it comes back blank.  

Although in my unit tests the following statement returns the response in
the String as expected. 

String response = (String) template.requestBody("direct:accessAuth", new
String(Files.readAllBytes(Paths.get(getClass().getResource("/requests/raw.txt").toURI();


What am I missing?  I've started to look into the stream caching, tho i'm
not sure if this is the right direction.  

ANY ideas are appreciated!

Thanks!



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-netty-no-response-received-from-remote-server-tp5759592p5759650.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: How to stop a route from processing get requests continously

[Claus Ibsen]

Hi

See the timer or quartz component for a scheduler and make it run 1 time etc


On Wed, Nov 26, 2014 at 4:44 PM, daninovac  wrote:
> I have the next scenario:
>
> I need to implement something like this:
> I have a file.txt with id's
> I have splitted those id's by \n and I need to do:
> From file.txt ->
>  split->
>  for each id make a GET request on a url (www.example.com). This url
> send to me some JSON ->
>  Unmarshal JSON to xml.
> That's all.
> My ideas & implementation:
>1. route from url to some output (let's say I will put the JSON's in
> a folder).
>  
>  
>  
>  
>   2. route from file.txt to seda
>  
>  
>   
>  
>  
>   3. route from seda:ids to myProcessor
>  
>  
>   
>  
>   myProcessor just starts the route from where I GET the JSONs
>
> *The problem is*: I need a JSON for each id. One id will have a JSON file.
> But the GET is making requests continuously to the url. And I end with a lot
> of JSONs instead of the same nr of JSONs as the number of id's.
> *How can I stop the 1st route from making requests continously??*
> I tought seda will solve it and the nr of requests will be the same number
> as the id's from my file, but I'm wrong somehow.
>
> Thanks, guys!
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/How-to-stop-a-route-from-processing-get-requests-continously-tp5759649.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: camel-netty: no response received from remote server.

[Claus Ibsen]

Hi

It depends on the codec you use for netty. I think it may for some odd
reason be a java seriazlization codec as that was the default with the
mina component, and we wanted netty to be similar.

If you use textline=true then its a text based message etc.

On Wed, Nov 26, 2014 at 4:50 PM, bwest  wrote:
> Hello,
>
> I've made some progress with the original question.  I appears that I am
> receiving a response as expected.  However, the response isn't in the body.
> So when i do a .log("Message: ${body}) in the route, it comes back blank.
>
> Although in my unit tests the following statement returns the response in
> the String as expected.
>
> String response = (String) template.requestBody("direct:accessAuth", new
> String(Files.readAllBytes(Paths.get(getClass().getResource("/requests/raw.txt").toURI();
>
>
> What am I missing?  I've started to look into the stream caching, tho i'm
> not sure if this is the right direction.
>
> ANY ideas are appreciated!
>
> Thanks!
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/camel-netty-no-response-received-from-remote-server-tp5759592p5759650.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: camel-netty: no response received from remote server.

[bwest]

Hi Claus, 

This is the what my route currently looks like:  

from("direct:sendAuthMessage")
.log("Logging Incoming message -->" + "${body}")
.setBody(simple("${body}", String.class))

.to("netty:tcp://10.98.1.41:1100?clientPipelineFactory=#cpf&sync=true&textline=true&autoAppendDelimiter=false").delay(3000)
.to("log:Socket response??showAll=true") // <-- 
This show the body as
blank.
//.to("file:/tmp/output/")
.to("mock:authorization");

My Logging statement is showing the following:  
Headers: {breadcrumbId=ID-BWEST-52331-1417019441385-0-1}, BodyType: String,
Body: , Out: null: ]


I am using the textline codec.  I'm also using a custom pipeline in order to
implement a custom delimiterbasedframedecoder, not sure if that would have
something to do with this.


I'm not sure why the Unit test can trap this value as a String but the route
can't seem to get at it.  I'm new with camel, so am I not doing something
correctly in the route?  
 



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-netty-no-response-received-from-remote-server-tp5759592p5759660.html
Sent from the Camel - Users mailing list archive at Nabble.com.

transacted() after from()

[geppo]

I ready in the Camel In Action book:

“NOTE: When using transacted() in the Java DSL, you must add it right
after from() to ensure that the route is properly configured to use transac-
tions. This isn’t enforced in the DSL because the DSL is loosely defined to
make it easy to maintain and develop Camel. There are a few tradeoffs such
as this.”

The book was for Camel 2.5, so I wonder if this has changed in newer
versions of Camel.
Any idea?



--
View this message in context: 
http://camel.465427.n5.nabble.com/transacted-after-from-tp5759661.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: transacted() after from()

[Claus Ibsen]

Hi

No you should still add it to the top of the route.

On Wed, Nov 26, 2014 at 5:47 PM, geppo  wrote:
> I ready in the Camel In Action book:
>
> “NOTE: When using transacted() in the Java DSL, you must add it right
> after from() to ensure that the route is properly configured to use transac-
> tions. This isn’t enforced in the DSL because the DSL is loosely defined to
> make it easy to maintain and develop Camel. There are a few tradeoffs such
> as this.”
>
> The book was for Camel 2.5, so I wonder if this has changed in newer
> versions of Camel.
> Any idea?
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/transacted-after-from-tp5759661.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: transacted() after from()

[geppo]

Thank you!



--
View this message in context: 
http://camel.465427.n5.nabble.com/transacted-after-from-tp5759661p5759663.html
Sent from the Camel - Users mailing list archive at Nabble.com.

CxfRs producer: connection not closed

[Thibaut Robert]

Hi,

When using cxfRs to send a rest message in InOnly mode, Camel do not close
the javax.ws.rs.core.Response object. As we are InOnly, the reponse object
is not passed through the exchange, so the caller can not close it either.

Not calling close on the response maintain the input stream open (and the
associated tcp connection) until it times out (or gc'ed), which is not
desirable.

As a workaround I always use InOut mode and close the response, even if I'm
not interested in the result.

Example (scala code):

val camel = new DefaultCamelContext().createProducerTemplate()
val destination = "http://localhost:1234";
val body = """{"key":"value"}"""
// Leave an open connection
//camel.sendBody("cxfrs:" + destination, body)
// use instead:
camel.requestBody("cxfrs:" + destination,
body).asInstanceOf[Response].close()


Is it possible to change this behaviour in Camel ?

Thanks

--
Thibaut

Re: Servlet component matchOnUriPrefix is not working as documented

[Amit]

We are using Apache Camel 2.11.4. 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Servlet-component-matchOnUriPrefix-is-not-working-as-documented-tp5759604p5759665.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: [Rest DSL] Automatic convertion of body to java.util.Map . How to fix it ?

[Taariq Levack]

Hi
You need to set the type as SpeakerPojo.class
I don't see a spring example here setting type but it should work the same as 
java so adjust accordingly.
http://camel.apache.org/rest-dsl.html

Taariq

> On 26 Nov 2014, at 17:40, Vaïsse-Lesteven Arthur  
> wrote:
> 
> Hi every one!
> 
> I'm trying to create a RESTful API using the Rest DSL capacity of the
> release 2.14.0 of Camel.
> 
> My problem currently come from the fact that the body of the Exchange is
> automatically casted into a java Map object.
> 
> Here come a reduced example (I tried to make it as small as possible...) : 
> 
> This is my XML camel context file. It defines a rest API that accept
> conection on http://localhost:5117/rest/speakers/{speaker_id} and that
> expect HTTP put with a Json object that is serializable into a SpeakerPojo
> object.
> 
> 
> The java classes that backed this endpoint are:
> The SpeakerPojo object:
> 
> And the bean used as endpoint :
> 
> 
> Finally I use this code to call the restAPI :
> 
> 
> These call make the following error to occur:
> 
> 
> The message body have automatically transformed into a HashMap. So I tried
> to add before the unmarshaller call 
> I then got this :
> 
> And a parsing error as double quote are now absent due to the double
> conversion from string to map and from map to string.
> 
> Am I doing something wrong ? Can I dis-activate the auto-casting of the
> payload to HashMap ?
> 
> Thank in advance!
> 
> 
> 
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Rest-DSL-Automatic-convertion-of-body-to-java-util-Map-How-to-fix-it-tp5759648.html
> Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-netty: no response received from remote server.

[Claus Ibsen]

You can add an explicit conversion to your route

to("netty...")
convertBodyTo(String.class)
to("log:...")

On Wed, Nov 26, 2014 at 5:37 PM, bwest  wrote:
> Hi Claus,
>
> This is the what my route currently looks like:
>
> from("direct:sendAuthMessage")
> .log("Logging Incoming message -->" + "${body}")
> .setBody(simple("${body}", String.class))
>
> .to("netty:tcp://10.98.1.41:1100?clientPipelineFactory=#cpf&sync=true&textline=true&autoAppendDelimiter=false").delay(3000)
> .to("log:Socket response??showAll=true") // <-- 
> This show the body as
> blank.
> //.to("file:/tmp/output/")
> .to("mock:authorization");
>
> My Logging statement is showing the following:
> Headers: {breadcrumbId=ID-BWEST-52331-1417019441385-0-1}, BodyType: String,
> Body: , Out: null: ]
>
>
> I am using the textline codec.  I'm also using a custom pipeline in order to
> implement a custom delimiterbasedframedecoder, not sure if that would have
> something to do with this.
>
>
> I'm not sure why the Unit test can trap this value as a String but the route
> can't seem to get at it.  I'm new with camel, so am I not doing something
> correctly in the route?
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/camel-netty-no-response-received-from-remote-server-tp5759592p5759660.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/

Camel 2.14.0 Matrix Params are missing

[Kumaran]

Hi 

This is my first post in the forum, We are using camel 2.14.0 version and
need to proxy the web service. i have posted to configurations below
followed from the camel-proxy-example.
 

  
  
   


 
http://localhost:29090/MyServer/"; 
loggingFeatureEnabled="true" loggingSizeLimit="20" skipFaultLogging="true">  



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

 
 
 


But we can see that the Matrix Parameters are completely stripped away in
the CxfRsProducer.  I know that if we use SimpleConsumer as the binding
style the matrix param will be sent as header params.  But shouldn't the
matrix params part of the URL.


ID: 15
Address:
http://localhost:8001/test/services/proxyServer/boxing;state=Current
Http-Method: GET
Content-Type: 
Headers: {Accept=[application/xml], accept-encoding=[gzip, deflate],
accept-language=[en-us], Authorization=[], connection=[keep-alive],
Content-Length=[0], Content-Type=[null], host=[localhost:8001]}
-- 

---
ID: 16
Address: http://localhost:29090/MyServer/boxing
Http-Method: GET
Content-Type: */*
Headers: {Accept=[application/xml], *state=[Current]*,  user-agent=[xx],
accept-encoding=[gzip, deflate], Content-Length=[0], Authorization=[Bearer
fff8ed5e-5509-4116-8fde-6523b0e60144],
org.apache.cxf.request.uri=[/services/proxyServer/boxing;state=Current],
host=[localhost:8001], connection=[keep-alive], accept-language=[en-us],
org.apache.cxf.message.Message.PATH_INFO=[/boxing],
org.apache.cxf.request.method=[GET], Content-Type=[*/*]}
 
 
I have came across similar issue posted in the past.   CAMEL-5405 CXF
Transport loses HTTP Matrix parameters

   
But we are using camel 2.14.0 version.

Can somebody help us on resolving this issue ?


Thanks in Advance.
-Kumaran




--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-2-14-0-Matrix-Params-are-missing-tp5759668.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel 2.14.0 Matrix Params are missing

[Sergey Beryozkin]

Hi

I agree it is a CXFRS producer bug that matrix parameters are lost.
CAMEL-5405 was addressing a server side issue.
I'll have a look.

In meantime - please consider using an alternative Camel HTTP centric 
component - may be REST DSL ? or if it is feasible then pass the options 
as path or query parameters


Thanks, Sergey

On 26/11/14 20:09, Kumaran wrote:

Hi

This is my first post in the forum, We are using camel 2.14.0 version and
need to proxy the web service. i have posted to configurations below
followed from the camel-proxy-example.



   
   
 


http://localhost:29090/MyServer/";
loggingFeatureEnabled="true" loggingSizeLimit="20" skipFaultLogging="true">




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






But we can see that the Matrix Parameters are completely stripped away in
the CxfRsProducer.  I know that if we use SimpleConsumer as the binding
style the matrix param will be sent as header params.  But shouldn't the
matrix params part of the URL.


ID: 15
Address:
http://localhost:8001/test/services/proxyServer/boxing;state=Current
Http-Method: GET
Content-Type:
Headers: {Accept=[application/xml], accept-encoding=[gzip, deflate],
accept-language=[en-us], Authorization=[], connection=[keep-alive],
Content-Length=[0], Content-Type=[null], host=[localhost:8001]}
--

---
ID: 16
Address: http://localhost:29090/MyServer/boxing
Http-Method: GET
Content-Type: */*
Headers: {Accept=[application/xml], *state=[Current]*,  user-agent=[xx],
accept-encoding=[gzip, deflate], Content-Length=[0], Authorization=[Bearer
fff8ed5e-5509-4116-8fde-6523b0e60144],
org.apache.cxf.request.uri=[/services/proxyServer/boxing;state=Current],
host=[localhost:8001], connection=[keep-alive], accept-language=[en-us],
org.apache.cxf.message.Message.PATH_INFO=[/boxing],
org.apache.cxf.request.method=[GET], Content-Type=[*/*]}


I have came across similar issue posted in the past.   CAMEL-5405 CXF
Transport loses HTTP Matrix parameters

But we are using camel 2.14.0 version.

Can somebody help us on resolving this issue ?


Thanks in Advance.
-Kumaran




--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-2-14-0-Matrix-Params-are-missing-tp5759668.html
Sent from the Camel - Users mailing list archive at Nabble.com.




--
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Blog: http://sberyozkin.blogspot.com

Async processing for

[figc]

I have a spring-mvc / ext-js application which currently executes as such:

1) User enters data in a form which gets submitted as json to an mvc
controller. 
The mvc controller invokes a web service, retrieves a file, does some
ETL/database stuff and sends an email if there are problems...then it sends
back a JSON response to the user who submitted the form. This is all
synchronous so the user has to wait till the whole thing is done, which can
take some time.

I'd like to run this asynchronously using camel where all the user does is
submit the form. The only difference to the user is the time of the
response...which should be considerably less.

The parts I'd like to put in a camel route are the following:

1) Invoke web service
2) do some ETL
3) do some database stuff
4) send an email

I was looking at the camel servlet component to kick off a route but from
what I gathered, this is still synchronous.

What are my options for running the above process asynchronously? 
Send a jms message for camel to pick up and to the processing?

Any direction is appreciated.






--
View this message in context: 
http://camel.465427.n5.nabble.com/Async-processing-for-tp5759673.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: xmljson component failing to do json>xml conversion

[clinton]

I had tried converting to a string.  Just didn't work for some reason.  
I just wrote a bean to handle it.
thx



--
View this message in context: 
http://camel.465427.n5.nabble.com/xmljson-component-failing-to-do-json-xml-conversion-tp5759488p5759674.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel 2.14.0 Matrix Params are missing

[Kumaran]

Hi  Sergey  

Thanks for the quick reply and taking a look at this issue. I will not be
able to change the real REST service signature.

Meanwhile i was going through REST DSL option suggestion.  The
camel-netty-http, camel-jetty, camel-restlet, camel-servlet,
camel-spark-rest   components documentation doesn't talked about
MatrixParam, i can see some docs related to query param.  i really doubts
even if i start using any of these components i will sendup in the same
Matrix param issue.

Any pointer or samples related to REST producer with Matrix param in camel
2.14  will be great helpful.

Just thinking like headerfilter  can we customize the URL also ?





--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-2-14-0-Matrix-Params-are-missing-tp5759668p5759675.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Sending a Request to camel rout from rx java observable

[Litom]

 How can I call a camel rout from rx java observable, and get a reply?
I wish the call to be non blocking, when the component   supports
asynchronous processing.
I tried to use producerTemplate.asyncRequest and noticed that It's thread is
blocked,  waiting on latch for a response.




--
View this message in context: 
http://camel.465427.n5.nabble.com/Sending-a-Request-to-camel-rout-from-rx-java-observable-tp5759677.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel 2.14.0 Matrix Params are missing

[Kumaran]

Hi Sergey

I had a fix for this issue to support Matrix Parameter Could you validate.

CxfRsProducer.java
  

Added new methods like setupClientMatrix,getMatrixParametersFromMatrixString

Thanks
Kumaran



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-2-14-0-Matrix-Params-are-missing-tp5759668p5759678.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel 2.14.0 Matrix Params are missing

[Willem Jiang]

Hi Kumaran,

Thanks for your contribution.
Could you create a JIRA[1] and submit the diff patch to it?
It could be more easy for us to track the issue and apply the patch.

--  
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 November 27, 2014 at 9:47:05 AM, Kumaran (mail2dkuma...@gmail.com) wrote:
> Hi Sergey
>  
> I had a fix for this issue to support Matrix Parameter Could you validate.
>  
> CxfRsProducer.java
>  
>  
> Added new methods like setupClientMatrix,getMatrixParametersFromMatrixString  
>  
> Thanks
> Kumaran
>  
>  
>  
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Camel-2-14-0-Matrix-Params-are-missing-tp5759668p5759678.html
>   
> Sent from the Camel - Users mailing list archive at Nabble.com.
>  

Re: Multicast with multiple timeouts

[Willem Jiang]

I just created a JIRA[1] for it.

[1]https://issues.apache.org/jira/browse/CAMEL-8081

--  
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 November 26, 2014 at 9:44:27 PM, gquintana (gerald.quint...@gmail.com) wrote:
> Is there an issue I can follow or should I create one?
> Gérald
>  
>  
>  
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Multicast-with-multiple-timeouts-tp5759576p5759646.html
>   
> Sent from the Camel - Users mailing list archive at Nabble.com.
>  

Re: CxfRs producer: connection not closed

[Willem Jiang]

Thanks for pointing that out, I just created a JIRA[1] for it.

[1]https://issues.apache.org/jira/browse/CAMEL-8082

--  
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 November 27, 2014 at 1:26:44 AM, Thibaut Robert (thibaut.rob...@gmail.com) 
wrote:
> Hi,
>  
> When using cxfRs to send a rest message in InOnly mode, Camel do not close
> the javax.ws.rs.core.Response object. As we are InOnly, the reponse object
> is not passed through the exchange, so the caller can not close it either.
>  
> Not calling close on the response maintain the input stream open (and the
> associated tcp connection) until it times out (or gc'ed), which is not
> desirable.
>  
> As a workaround I always use InOut mode and close the response, even if I'm
> not interested in the result.
>  
> Example (scala code):
>  
> val camel = new DefaultCamelContext().createProducerTemplate()
> val destination = "http://localhost:1234";
> val body = """{"key":"value"}"""
> // Leave an open connection
> //camel.sendBody("cxfrs:" + destination, body)
> // use instead:
> camel.requestBody("cxfrs:" + destination,
> body).asInstanceOf[Response].close()
>  
>  
> Is it possible to change this behaviour in Camel ?
>  
> Thanks
>  
> --
> Thibaut
>  

Re: Async processing for

[Claus Ibsen]

There is also the wire tap eip

On Wed, Nov 26, 2014 at 10:54 PM, figc  wrote:
> I have a spring-mvc / ext-js application which currently executes as such:
>
> 1) User enters data in a form which gets submitted as json to an mvc
> controller.
> The mvc controller invokes a web service, retrieves a file, does some
> ETL/database stuff and sends an email if there are problems...then it sends
> back a JSON response to the user who submitted the form. This is all
> synchronous so the user has to wait till the whole thing is done, which can
> take some time.
>
> I'd like to run this asynchronously using camel where all the user does is
> submit the form. The only difference to the user is the time of the
> response...which should be considerably less.
>
> The parts I'd like to put in a camel route are the following:
>
> 1) Invoke web service
> 2) do some ETL
> 3) do some database stuff
> 4) send an email
>
> I was looking at the camel servlet component to kick off a route but from
> what I gathered, this is still synchronous.
>
> What are my options for running the above process asynchronously?
> Send a jms message for camel to pick up and to the processing?
>
> Any direction is appreciated.
>
>
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Async-processing-for-tp5759673.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/