Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 46C7F18F91 for ; Thu, 10 Dec 2015 21:45:41 +0000 (UTC) Received: (qmail 58624 invoked by uid 500); 10 Dec 2015 21:45:40 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 58573 invoked by uid 500); 10 Dec 2015 21:45:40 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 58551 invoked by uid 99); 10 Dec 2015 21:45:40 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Dec 2015 21:45:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id C6D24C0F42 for ; Thu, 10 Dec 2015 21:45:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.314 X-Spam-Level: ** X-Spam-Status: No, score=2.314 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id o2tUEnCiP3Zy for ; Thu, 10 Dec 2015 21:45:28 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTP id 2140824D8F for ; Thu, 10 Dec 2015 21:45:28 +0000 (UTC) Received: from msam.nabble.com (unknown [162.253.133.85]) by mbob.nabble.com (Postfix) with ESMTP id 871021C0A198 for ; Thu, 10 Dec 2015 13:45:27 -0800 (PST) Date: Thu, 10 Dec 2015 14:45:27 -0700 (MST) From: rwoolf To: users@camel.apache.org Message-ID: <1449783927112-5774970.post@n5.nabble.com> Subject: Jetty in route not working as expected MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have created a very simple route that uses Jetty to try to learn how to use it. I am trying this in servicemix 6.0.1 My camel context is defined in blueprint. The jetty server instance starts, but I always get 404 error when trying to call anything. In my browser I make a make a request to: http://localhost/test?id=2. I would expect to get my ID of 2 to be output to the logs, and then the response to the browser be the text "Hello World" But nothing happens in Camel, the route is never called. What I get back in the browser is: HTTP ERROR: 404 Problem accessing /test. Reason: Not Found Powered by Jetty:// Am I missing something simple? Do I not understand the use of Jetty correctly? Any help appreciated. Here is my simple blueprint/camel context Hello World -- View this message in context: http://camel.465427.n5.nabble.com/Jetty-in-route-not-working-as-expected-tp5774970.html Sent from the Camel - Users mailing list archive at Nabble.com.