Type Exception Report
Message Wrong article identifier
Description The server encountered an unexpected condition that prevented it from fulfilling the request.
Exception
java.lang.RuntimeException: Wrong article identifier com.enpassant.tennis.core.service.ArticleService.loadArticle(ArticleService.java:106) com.enpassant.tennis.article.screen.ArticleScreen$RenderArticleScreenHandler.mapRequest(ArticleScreen.java:53) com.enpassant.tennis.article.screen.ArticleScreen$RenderArticleScreenHandler.getModels(ArticleScreen.java:45) com.enpassant.tennis.main.screen.MainScreenHandler.getTemplateModels(MainScreenHandler.java:49) org.enhydra.barracuda.core.event.helper.BTemplateViewHandler.handleViewEvent(BTemplateViewHandler.java:82) org.enhydra.barracuda.core.event.helper.DefaultViewHandler.handleViewEvent(DefaultViewHandler.java:174) com.enpassant.tennis.main.screen.MainScreenHandler.handleViewEvent(MainScreenHandler.java:150) org.enhydra.barracuda.core.event.DefaultBaseEventListener.handleEvent(DefaultBaseEventListener.java:63) org.enhydra.barracuda.core.event.DefaultEventDispatcher.notifyListeners(DefaultEventDispatcher.java:421) org.enhydra.barracuda.core.event.DefaultEventDispatcher.dispatch(DefaultEventDispatcher.java:185) org.enhydra.barracuda.core.event.DefaultEventDispatcher.dispatchEvent(DefaultEventDispatcher.java:122) org.enhydra.barracuda.core.event.DefaultEventBroker.dispatchEvent(DefaultEventBroker.java:447) org.enhydra.barracuda.core.event.ApplicationGateway.handleDefaultExt(ApplicationGateway.java:693) org.enhydra.barracuda.core.event.ApplicationGateway.handleDefault(ApplicationGateway.java:257) org.enhydra.barracuda.core.event.ApplicationGateway.doGet(ApplicationGateway.java:1124) com.enpassant.tennis.MainGateway.doGet(MainGateway.java:147) javax.servlet.http.HttpServlet.service(HttpServlet.java:635) javax.servlet.http.HttpServlet.service(HttpServlet.java:742) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) com.enpassant.tennis.core.service.UserLoginFilter.doFilter(UserLoginFilter.java:40)
Note The full stack trace of the root cause is available in the server logs.