Re: Using jetty component for http producer : Weird behavior

2013-06-05 Thread Claus Ibsen
Hi Follow the advice on this page http://camel.apache.org/support On Wed, Jun 5, 2013 at 7:02 AM, anand_tech wrote: > Someone, any pointers over here ?? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Using-jetty-component-for-http-producer-Weird-behavior-tp5733

Re: Using jetty component for http producer : Weird behavior

2013-06-04 Thread anand_tech
Someone, any pointers over here ?? -- View this message in context: http://camel.465427.n5.nabble.com/Using-jetty-component-for-http-producer-Weird-behavior-tp5733303p5733833.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Using jetty component for http producer : Weird behavior

2013-05-28 Thread anand_tech
I think there is some issue with the internal jetty http producer classes. I changed the endpoint's name at jetty's end and gave an uri through processor using CamelHttpUri, but it still produced same behavior. Logs : [2013-05-28 11:24:18,366] org.apache.camel.processor.SendProcessor DEBUG - >>

Re: Using jetty component for http producer : Weird behavior

2013-05-28 Thread anand_tech
Camel is 2.9.0 and jetty is 7.5.3. Jetty jars are downloaded as part of camel-jetty dependencies through maven, so i guess jetty's version should not be a problem. -- View this message in context: http://camel.465427.n5.nabble.com/Using-jetty-component-for-http-producer-Weird-behavior-tp5733303

Re: Using jetty component for http producer : Weird behavior

2013-05-28 Thread Claus Ibsen
What version of Camel and Jetty are you using? On Tue, May 28, 2013 at 9:34 AM, anand_tech wrote: > i tried putting port also explicitly, but no luck .. Any pointers here ? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Using-jetty-component-for-http-producer-Weir

Re: Using jetty component for http producer : Weird behavior

2013-05-28 Thread anand_tech
i tried putting port also explicitly, but no luck .. Any pointers here ? -- View this message in context: http://camel.465427.n5.nabble.com/Using-jetty-component-for-http-producer-Weird-behavior-tp5733303p5733317.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Using jetty component for http producer : Weird behavior

2013-05-27 Thread anand_tech
Could it be that i haven't mentioned the port explicitly in the endpoint ?? "jetty://https://maps.googleapis.com{: is port needed here ?}/ -- View this message in context: http://camel.465427.n5.nabble.com/Using-jetty-component-for-http-producer-Weird-behavior-tp5733303p5733309.html Sent f

Re: Using jetty component for http producer : Weird behavior

2013-05-27 Thread anand_tech
Oh, i should have mentioned that too. I have already tried it with "jetty:https://maps.google -- View this message in context: http://camel.465427.n5.nabble.com/Using-jetty-component-for-http-producer-Weird-behavior-tp5733303p5733307.html Sent from the Camel - Users mailing list archive at

Re: Using jetty component for http producer : Weird behavior

2013-05-27 Thread Claus Ibsen
Try with jetty:https://x On Tue, May 28, 2013 at 8:01 AM, anand_tech wrote: > Hi, > > I have a route like this in Java DSL > > from("servlet://abc/?matchOnUriPrefix=true") > .process(new Processor() > { > > @Override > pu