首页上一页 1 下一页尾页 1 条记录 1/1页
《jsp数据库系统开发案例精选》客户管理系统
发表在JavaWeb图书答疑
2009-03-27
是否精华
是
否
版块置顶:
是
否
问题1.如何将《客户管理系统》导入MyEclipse中,请详述步骤。
问题2.已经正确配置jdk tomcat sql sever sp4 并按光盘提示连接数据库,输入用户名密码后出现如下错误,请您指教。非常感谢!
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:637)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.18 logs.
--------------------------------------------------------------------------------
Apache Tomcat/6.0.18
问题2.已经正确配置jdk tomcat sql sever sp4 并按光盘提示连接数据库,输入用户名密码后出现如下错误,请您指教。非常感谢!
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:637)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.18 logs.
--------------------------------------------------------------------------------
Apache Tomcat/6.0.18