首页上一页 1 下一页尾页 3 条记录 1/1页
运行《JSP数据库系统开发案例精选》书中第三章中客户管理系统项目时出错
发表在JavaWeb图书答疑
2009-03-31
是否精华
是
否
版块置顶:
是
否
老师:
您好!
我在运行《JSP数据库系统开发案例精选》书中第三章中客户管理系统项目时出现以下错误提示信息,我已按照书使用说明书进行操作与ODBC设定,请老师赐教!!!
HTTP Status 500 -
--------------------------------------------------------------------------------
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
java.lang.NullPointerException
com.dao.UserDaoImpl.checkUser(UserDaoImpl.java:35)
com.service.UserFacadeImpl.checkUser(UserFacadeImpl.java:28)
com.webtier.manager.UserCheck.perform(UserCheck.java:30)
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1787)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.26 logs.
--------------------------------------------------------------------------------
Apache Tomcat/5.5.26
您好!
我在运行《JSP数据库系统开发案例精选》书中第三章中客户管理系统项目时出现以下错误提示信息,我已按照书使用说明书进行操作与ODBC设定,请老师赐教!!!
HTTP Status 500 -
--------------------------------------------------------------------------------
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
java.lang.NullPointerException
com.dao.UserDaoImpl.checkUser(UserDaoImpl.java:35)
com.service.UserFacadeImpl.checkUser(UserFacadeImpl.java:28)
com.webtier.manager.UserCheck.perform(UserCheck.java:30)
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1787)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.26 logs.
--------------------------------------------------------------------------------
Apache Tomcat/5.5.26