【问题标题】:UriFragmentUtility causes servlet exceptionUriFragmentUtility 导致 servlet 异常
【发布时间】:2012-01-24 00:38:38
【问题描述】:

当我关注这个 vaadin:https://vaadin.com/book/-/page/advanced.urifu.html 关于如何正确使用 UriFragmentUtility 的教程时,我最终创建了对象,在尝试将此组件添加到我的主窗口后,它失败并出现以下异常:

SEVERE: Servlet.service() for servlet [Dugsi_Manager Vaadin Application Servlet] in context with path [/Dugsi_Manager] threw exception [java.lang.UnsupportedOperationException] with root cause
java.lang.UnsupportedOperationException
    com.vaadin.ui.CustomComponent.addComponent(CustomComponent.java:218)
    com.vaadin.ui.Panel.addComponent(Panel.java:301)
    com.vaadin.ui.Window.addComponent(Window.java:281)
    org.bixin.dugsi.web.DugsiManagerApplication.init(DugsiManagerApplication.java:44)
    com.vaadin.Application.start(Application.java:554)
    com.vaadin.terminal.gwt.server.AbstractApplicationServlet.startApplication(AbstractApplicationServlet.java:1213)
    com.vaadin.terminal.gwt.server.AbstractApplicationServlet.service(AbstractApplicationServlet.java:484)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
    org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:359)
    org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:275)
    org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)
    org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)
    org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:344)
    org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:272)
    org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:81)
    org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
    org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)

这是我将对象添加到我的主应用程序类的方法:

//Thread Local to create instances of our application
private static ThreadLocal<DugsiManagerApplication> threadLocal = new ThreadLocal<DugsiManagerApplication>();
@Override
public void init() {
    setInstance(this); // immediate access to the app
    //Window homeWindow = createNewWindow();
    Subject currentUser = SecurityUtils.getSubject();
    // Create the URI fragment utility
    Window window = createLoginWindow();    

    setMainWindow(window);
    final UriFragmentUtility urifu = new UriFragmentUtility();
    window.addComponent(urifu);

}

在教程中,它讨论了 URI 主要部分(地址 + 路径 + 可选查询参数),我的路径设置为 /Dugsi_Manager (web.xml),如果在将 urifu 对象添加为 @987654326 后它不会启动@?

编辑:添加了登录窗口的声明:

public Window createLoginWindow(){
     final Window loginWindow = new LoginWindow();

    //remove the window if closed to avoid memory leaks
    loginWindow.addListener(new CloseListener() {
        @Override
        public void windowClose(CloseEvent e) {
            if (getMainWindow() != loginWindow) {
                DugsiManagerApplication.this.removeWindow(loginWindow);
            }
        }
    });
    return loginWindow;
}

\ ** 似乎 UriFragmentUtility 对象可以添加到标准 Vaadin 窗口,但不适用于使用我的 createLoginWindow 函数创建的窗口?我不知道为什么?

【问题讨论】:

    标签: vaadin url-pattern servletexception uri-fragment


    【解决方案1】:

    CustomComponent 的 addComponent 方法抛出异常。所以我猜 CustomComponent 是一个窗口的内容。要解决此问题,请将 UriFragmentUtility 直接添加到作为 CustomComponent 的组合根的布局中,而不是

    window.addComponent(urifu);
    

    【讨论】:

    • 我尝试将此 UriFragmentUtility 添加到调用启动窗口的自定义组件中,但它没有影响。似乎它不喜欢我使用 createLoginWindow() 函数创建窗口的方式。如果我使用标准 vaadin.ui.Window 类创建窗口,它可以正常工作。我添加了编辑以显示我如何创建我的 LoginWindow 类
    猜你喜欢
    • 2015-07-16
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2017-03-23
    • 2011-06-08
    • 2017-02-16
    • 2018-11-09
    • 2014-03-13
    相关资源
    最近更新 更多