On 09/02/2012 14:23, Antonio Goncalves wrote:
> Any thoughts ?
The Servlet specification deliberately places container configuration
outside of the specification scope. I'm thinking of things like: IP
address and port to bind to; host name(s) for HTTP virtual hosting;
configuration of SSL certificates; provision of required JNDI resources;
credential stores to authenticate against etc.
While defaults are available for these which might be good enough for
unit testing there are far more use cases where some form of
configuration would be required. Any such configuration currently uses a
container specific API.
That appears to leave the following options:
a) Use the existing container specific APIs to create and a configure a
container.
b) Add the API along the lines you suggest and use this to create the
container followed by container specific API to configure it.
c) Expand the proposed API and scope of the Servlet spec to include
container configuration and then use the new API to create and configure
the container.
I am strongly against c).
I don't really see the point of b) since one needs to use a container
specific API anyway.
That leaves a), the current position.
Mark