thanks heaps for that - will take a look.
On Wed, Jan 19, 2011 at 10:09 AM, Sven Zethelius <[email protected]> wrote: > I've had the recent fun of diving through this code so I'll save you some > time... I also saw your post on Jetty-users which better qualifies what you > are asking about. > > The "sharing" you are looking for occurs if the endpoints are different paths > on the same OS port. CXF creates a Jetty Server per OS port. That Server > owns a distinct Connector that is used for that port. So if your endpoints > are all using the same port (443 for example), but with different contexts > (https://localhost:443/serviceA, https://localhost:443/serviceB, etc) then > you'll get a common Connector in use by all the endpoint. If the endpoints > are for different ports, they'll create distinct Server and Connector > instances. > > Starting point for all this is > org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine.addServant(URL, > JettyHTTPHandler), which is called when CXF creates an HTTPDestination for > your endpoint. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Jason > Pell > Sent: Tuesday, January 18, 2011 2:44 PM > To: [email protected] > Subject: Jetty cxf architecture > > Hi, > > I am trying to get a handle on how the jetty connectors and cxf > interact. I obviously can take a more detailed pass at the code, but > I was hoping one of you might be able to stear me in the correct > direction. Specifically what I am trying to get my head around is the > relationship between CXFJettySslSocketConnector and > SslSelectChannelEndPoint. > > I would like to understand how these connectors are instantiated by > cxf so that I can then extrapolate how this applies to jetty. > > Where might I start with the docos or code to try and understand the > jetty to jaxws interactions >
