Hi,
Without being too flippant, everything in web.xml
is "standard" and everything in server.xml is
Tomcat specific.
You can rely on most J2EE/Servlet containers to
be able to provide access to connection pools, and
potentially JNDI resources and things that Tomcat
provides in server.xml, however the manner for
configuration is generally different (not much)
between the various vendors.
The only "code specific" things have generally
been:
. getting an InitialContext
. getting a database connection
However, if you're really fired up about it, you
can abstract a lot of that out, or parameterise it.
We've found that the 3 or 4 lines of code that need
to be changed generally haven't been worth the effort.
However, YMMV.
Cheers,
-- jon
Pierre-Laurent Ribault wrote:
> Hi,
>
> I'm in the process of developping a Web application using Tomcat as the
> development testbed. However, I'd like to be able later to deploy the
> application on another servlet engine with the same specs level.
> I know that Tomcat is the reference implementation of the servlet/JSP
> spec, but is there an easy way (i.e. without reading the whole spec) to
> know what is part of the spec and what is implementation specific in
> Tomcat? For example, among the server settings (datasource, realms, etc).
>
> ―――――――――――――――――――――――
> Pierre-Laurent Ribault
> Fujitsu Info Software Technologies Ltd.
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
--
Jon Eaves <[EMAIL PROTECTED]>
http://www.eaves.org/jon/
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
