: Re: customizing the HTTP transport factory
Hi Benson,
You're very close to getting it to work :-) If you look at the
cxf-extension-http-jetty.xml file you'll see that we associate several
transport IDs with that transport:
bean class
Hi Benson,
I think we could add some spring configuration support for the Jetty
server.That could make you life easier.
I filled a JIRA[1] for it.
In this way, we can get the benefits of the easy start of standalone
server and flexible of the configuration.
[1]
Hi Benson,
You're very close to getting it to work :-) If you look at the
cxf-extension-http-jetty.xml file you'll see that we associate several
transport IDs with that transport:
bean class=
org.apache.cxf.transport.http_jetty.JettyHTTPTransportFactory
lazy-init=true
property
Dan,
The most interesting thing that dawned on me is that a JettyHTTPHandler
\is a/ Jetty \Handler/. Thus, I can instantiate Jetty's standard static
content handler and call it from a subclass of JettyHTTPHandler, since
the same arguments that come into JettyHTTPHandler can be delegated to
the
