org.springframework.web.util.NestedServletException：处理程序处理失败;嵌套异常是java.lang.ExceptionInInitializerError

Question

我是J2EE和Hibernate的新手 请帮我解决这个问题，我找不到解决方案

这是我的代码：  

package inventory.service.user;

import inventory.domain.User;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.hibernate.validator.constraints.NotEmpty;


public class Authentication {
    protected final Log logger = LogFactory.getLog(getClass());

    @NotEmpty
    private String login;
    @NotEmpty
    private String password;
    private String error;

    public User getUser(){
        User user = new User();
        user.setLogin(login);
        user.setPassword(password);
        return user;
    }

    public void setLogin(String login){ 
        this.login = login; 
        logger.info("Authentication: login set to "+ login);
    }

    public void setPassword(String password){ 
        this.password = password;
        logger.info("Authentication: password set to "+ password);
    }

    public String getLogin() {
        return login;
    }

    public String getPassword() {
        return password;
    }

    public String getError() {
        return error;
    }

    public void setError(String error) {
        this.error = error;
    }
}

的

我在netBeans IDE中工作，并添加了这些jar文件

  

aopalliance

     

aspectjweaver

     

derbyclient

     

hibernate-core-4.3.10.Final

     

冬眠-搜索5.3.0.Beta2 - 距离

     

JSTL-1.2

     

ORG-netbeans的模块的Web-jstl11.jar

消息错误是：

HTTP Status 500 - Internal Server Error
type Exception report
messageInternal Server Error
descriptionThe server encountered an internal error that prevented it from fulfilling this request.
exception
org.springframework.web.util.NestedServletException: Handler processing failed; nested exception is java.lang.ExceptionInInitializerError
root cause
java.lang.ExceptionInInitializerError
root cause
java.lang.NoClassDefFoundError: org/dom4j/DocumentException
root cause
java.lang.ClassNotFoundException: org.dom4j.DocumentException
note The full stack traces of the exception and its root causes are available in the GlassFish Server Open Source Edition 4.1 logs.