Type Exception Report
Message Request parameter missing: ['No parameter named: id in request']
Description The request could not be completed due to a conflict with the current state of the target resource.
Exception
pl.psnc.dlibra.web.common.exceptions.MissingRequestParameterException: Request parameter missing: ['No parameter named: id in request'] pl.psnc.dlibra.web.fw.util.servlet.ServletRequestWrapper.getId(ServletRequestWrapper.java:158) pl.psnc.dlibra.web.comp.pages.components.CollectionDescriptionComponent.prepareRemoteContent(CollectionDescriptionComponent.java:43) pl.psnc.dlibra.web.comp.pages.components.AbstractDlibraComponent.prepareContent(AbstractDlibraComponent.java:24) pl.psnc.dlibra.web.fw.pages.PageProducer.executeComponents(PageProducer.java:172) pl.psnc.dlibra.web.fw.pages.PageProducer.getPageContent(PageProducer.java:135) pl.psnc.dlibra.web.fw.RequestDispatcherServlet.handleRequest(RequestDispatcherServlet.java:127) org.apache.velocity.servlet.VelocityServlet.doRequest(VelocityServlet.java:365) org.apache.velocity.servlet.VelocityServlet.doGet(VelocityServlet.java:318) javax.servlet.http.HttpServlet.service(HttpServlet.java:529) javax.servlet.http.HttpServlet.service(HttpServlet.java:623) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:176) org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:394) org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:213) org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:171) org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:394)
Note The full stack trace of the root cause is available in the server logs.