严重: Null component Catalina:type=DataSource,path=/webtest,host=localhost,class=javax.sql.DataSource,name="jdbc/webtest" 2007-01-07 22:43:59,890[org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/webtest]]-[位置：org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3653)]-[DEBUG]Sending application start events 2007-01-07 22:43:59,890[org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/webtest]]-[位置：org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3528)]-[DEBUG]Starting filters 2007-01-07 22:43:59,890[org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/webtest]]-[位置：org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3537)]-[DEBUG] Starting filter 'loginFilter' 2007-01-07 22:43:59,906[org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/webtest]]-[位置：org.apache.catalina.core.ApplicationContext.log(ApplicationContext.java:636)]-[INFO]D:/Apache/Tomcat/webapps/webtest/WEB-INF/user.xml javax.naming.NameNotFoundException: Name java:comp is not bound in this Context at org.apache.naming.NamingContext.lookup(NamingContext.java:769) at org.apache.naming.NamingContext.lookup(NamingContext.java:152) at javax.naming.InitialContext.lookup(InitialContext.java:351) at cn.edu.ctgu.bean.DBConnectionManager.<clinit>(DBConnectionManager.java:24) at cn.edu.ctgu.bean.UserManagerDBImpl.<init>(UserManagerDBImpl.java:41) at cn.edu.ctgu.bean.UserManagerDBImpl.getInstance(UserManagerDBImpl.java:29) at cn.edu.ctgu.bean.ManagerFactory.creteDBUserManager(ManagerFactory.java:26) at cn.edu.ctgu.servlets.SaveUserServlet.init(SaveUserServlet.java:134)
之类的异常，让我糊涂了，昨天可以的，今天什么都没改啊，怎么就出问题了呢
后来仔细想了想，是不是MyEclipse给我搞了什么好东西了，算了，自己手工部署一下
怪了，一切正常，怎么手工部署就没问题呢？
再来一次，MyEclipse部署
哈哈，有来问题了，还是那个javax.naming.NameNotFoundException: Name java:comp is not bound in this Context，开来是这的问题了，把两次的部署比较了一下，发现了点不同的东西
In a J2SE 2 (that is, J2SE 1.2 or later) environment, class loaders are arranged in a parent-child tree. Normally, when a class loader is asked to load a particular class or resource, it delegates the request to a parent class loader first, and then looks in its own repositories only if the parent class loader(s) cannot find the requested class or resource. The model for web application class loaders differs slightly from this, as discussed below, but the main principles are the same.
System - 这个类装载器通常是以CLASSPATH环境变量的内容为基础来初始化的。所有的这些类既可被Tomcat内部classes使用，又可被网络程序使用。不过，标准的Tomcat 5启动脚本( $CATALINA_HOME/bin/catalina.sh or %CATALINA_HOME%/bin/catalina.bat )完全忽略了CLASSPATH环境变量自身的内容，相反从下面的贮藏室去建造系统类装载器：
$CATALINA_HOME/bin/commons-logging-api.jar - Jakarta commons 记录应用程序界面。
$CATALINA_HOME/bin/commons-daemon.jar - Jakarta commons daemon API.
jmx.jar - JMX 1.2 执行。
Common - This class loader contains additional classes that are made visible to both Tomcat internal classes and to all web applications. Normally, application classes should NOT be placed here. All unpacked classes and resources in $CATALINA_HOME/common/classes, as well as classes and resources in JAR files under the $CATALINA_HOME/commons/endorsed, $CATALINA_HOME/commons/i18n and $CATALINA_HOME/common/lib directories, are made visible through this class loader. By default, that includes the following:
commons-el.jar - Jakarta commons el, 执行Jasper使用的表达语言。
jasper-compiler.jar - The JSP 2.0 编译器。
jasper-compiler-jdt.jar - The Eclipse JDT Java compiler.
naming-factory-dbcp.jar - Jakarta commons DBCP, providing a JDBC connection pool to web applications. The classes have been moved out of their default org.apache.commons package.
naming-java.jar - Handler for the java: namespace.
naming-resources.jar - The specialized JNDI naming context implementation used to represent the static resources of a web application. This is not related to the support of the J2EE ENC, and cannot be removed.
servlet-api.jar - The Servlet 2.4 API.
tomcat-i18n-**.jar - Optional JARs containing resource bundles for other languages. As default bundles are also included in each individual JAR, they can be safely removed if no internationalization of messages is needed.
tomcat-ajp.jar - Classes for the Java portion of the AJP web server connector, which allows Tomcat to run behind web servers such as Apache and iPlanet iAS and iWS.
As mentioned above, the web application class loader diverges from the default Java 2 delegation model (in accordance with the recommendations in the Servlet Specification, version 2.3, section 9.7.2 Web Application Classloader). When a request to load a class from the web application's WebappX class loader is processed, this class loader will look in the local repositories first, instead of delegating before looking. There are exceptions. Classes which are part of the JRE base classes cannot be overriden. For some classes (such as the XML parser components in J2SE 1.4+), the J2SE 1.4 endorsed feature can be used (see the common classloader definition above). Last, any JAR containing servlet API classes will be ignored by the classloader. All other class loaders in Tomcat 5 follow the usual delegation pattern.
Among many other changes, the J2SE 1.4 release packages the JAXP APIs, and a version of Xerces, inside the JRE. This has impacts on applications that wish to use their own XML parser.
In previous versions of Tomcat 5, you could simply replace the XML parser in the $CATALINA_HOME/common/lib directory to change the parser used by all web applications. However, this technique will not be effective when you are running on J2SE 1.4, because the usual class loader delegation process will always choose the implementation inside the JDK in preference to this one.
615
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
