Hi Yes it looks odd. However camel-jetty is supposed to be used for exposing service (then it's the consumer that is used).
If you need to call external servers over the HTTP then camel-http should be used. But Jetty is a very powerful platform so I guess it should be possible to enable this again and fix why its unstable? This is the commit log when the change occured. So it's almost 1 year old. Revision: 576509 Author: chirino Date: 18:36:29, 17. september 2007 Message: disabled the jetty client since it seems to still be a little unstable. ---- Modified : /activemq/camel/trunk/components/camel-http/src/main/java/org/apache/camel/component/http/HttpProducer.java Modified : /activemq/camel/trunk/components/camel-jetty/src/main/java/org/apache/camel/component/jetty/JettyHttpEndpoint.java Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: tourist604 [mailto:[EMAIL PROTECTED] Sent: 8. august 2008 22:54 To: [email protected] Subject: JettyHttpEndpoint: bug? temporarily disabled? Hi, In Camel 1.4.0, in JettyHttpEndpoint, on line 45: public Producer<HttpExchange> createProducer() throws Exception { return super.createProducer(); // <----- this will delegate to HttpEndpoint // return new JettyHttpProducer(this); } Was this intended? Doesn't this effectively disable the whole endpoint? Cheers, --Bill -- View this message in context: http://www.nabble.com/JettyHttpEndpoint%3A-bug--temporarily-disabled--tp18898849s22882p18898849.html Sent from the Camel - Users mailing list archive at Nabble.com.
