On Mon, 18 Nov 2002, Pierre-Laurent Ribault wrote:
> Date: Mon, 18 Nov 2002 16:13:18 +0900 > From: Pierre-Laurent Ribault <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: spec compliants vs implementation specific parts? > > 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). > Everything in javax.servlet.* is part of the servlet and/or JSP specs. Programming to those APIs is portable. The format of web.xml is portable, but not all servers necessarily support all the configurable features (unless you're on a J2EE server). Tomcat implements the configurable stuff for <env-entry> and <resource-ref> in a manner that is compatible with the J2EE requirements. Thus, you'd be able to portably use the JNDI based resources that Tomcat supports. The mechanisms by which resources are configured (in Tomcat, it's the <ResourceParams> element in server.xml) are specific to each server. Things like the format of server.xml, and any reference to an org.apache.catalina.* or org.apache.jasper.* class, is Tomcat specific. Craig > ――――――――――――――――――――――― > Pierre-Laurent Ribault > Fujitsu Info Software Technologies Ltd. > > > > > > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
