Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of jeffrey.segal@gmail.com
 designates 209.85.210.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=A66bmNlz7ntteRRfKS5jR0PCTX7qshXfOdMaEECbMGA7nWVRwHgMaQVZLPv2J2FRTV
         94vj1Ikl6LhsFw8owufXOqFWpgjR7S5eEU6ZTwc0yjowtV7eiSyLLJyM6TryDIw3Wn2b
         DhJtTnWIhwzW4FPcv9+0PUjzoFjBewr21ORSA=
MIME-Version: 1.0
Date: Wed, 4 May 2011 16:18:27 -0400
Message-ID: <BANLkTi=nZaMUN5brJY255MvF_-_xmDmb6A@mail.gmail.com>
Subject: Camel - Jetty integration
From: Jeff Segal <jeffrey.segal@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=bcaec53aec82a2e0c904a278f5fe

--bcaec53aec82a2e0c904a278f5fe
Content-Type: text/plain; charset=ISO-8859-1

I have some general question about Camel and Jetty integration.

First, given that the jetty: Camel Component creates an embedded Jetty
server, is it assumed that this component would never be used within a web
app? Or am I missing something?

Second, I noticed that JettyHttpComponent manages a Map of Jetty Connectors.
However, CometdComponent does the same exact thing using its own Jetty
Connector Map. Is there any plan to consolidate the Jetty Connectors used
throughout Camel into one shared cache? For instance, it seems that one
would be unable to use a jetty: and cometd: Component on the same port in
the same app because only one Component would be able to successfully bind
to the port.

Thanks,
Jeff

--bcaec53aec82a2e0c904a278f5fe--