On Mar 7, 2007, at 9:04 AM, Ignacio Silva-Lepe wrote:
I have a couple of questions about the http.jetty service.
First, I am assuming that this service is intended to be kept
around and
not deprecated, but let me know if this is not the case.
If that is the case, then I wonder what the intended usage pattern is
supposed to be. I do see a JettyService interface but (1) it only
exposes
a getServer operation but other operations, like registerMapping,
are not
exposed, and (2) this interface is not exposed as an sca service
the way
the Store service is, for instance.
If there's interest, I would like to volunteer to upgrade
http.jetty service
and
make it a @Service that exposes a few more of the implemented
operations,
assuming that this an agreeable direction to take it in.
Thanks
+1 We definitely need it for the standalone runtime. The idea was to
have transport bindings be able to interact with a ServletHost which
would act as a facade for the actual servlet engine. This could be
Jetty in a standalone environment or the servlet engine of an app
server or OSGi container. The ServletHost API would provide the
common abstraction mechanism. It may also be worth upgrading to a
later version of Jetty as well.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
