org.openxava.util.ElementNotFoundException

El módulo GrupsIncidencio no está definido at org.openxava.application.meta.MetaApplication.getMetaModule(MetaAppli cation.java:100) at org.openxava.controller.ModuleManager.getMetaModule(ModuleManager.jav a:739) at org.openxava.controller.ModuleManager.setupModuleControllers(ModuleMa nager.java:162) at org.openxava.controller.ModuleManager.setModuleName(ModuleManager.jav a:718) at org.apache.jsp.xava.module\_jsp.\_jspService(module\_jsp.java:312)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web102

  • via openxava by eescrihuela
    , 11 months ago
    El m├│dulo GrupsIncidencio no estí definido at org.openxava.application.meta.MetaApplication.getMetaModule(MetaAppli cation.java:100) at org.openxava.controller.ModuleManager.getMetaModule(ModuleManager.jav a:739) at
  • via openxava by ironrage
    , 11 months ago
    El controlador StartOnDetail no estß definido at org.openxava.controller.meta.MetaControllers.getMetaController(MetaCo ntrollers.java:54) at org.openxava.controller.ModuleManager.getMetaControllers(ModuleManage r.java:201) at
  • via openxava by jlhm2012
    , 11 months ago
    El módulo Cliente no está definido
  • Stack trace

    • org.openxava.util.ElementNotFoundException: El m├│dulo GrupsIncidencio no est├í definido at org.openxava.application.meta.MetaApplication.getMetaModule(MetaAppli cation.java:100) at org.openxava.controller.ModuleManager.getMetaModule(ModuleManager.jav a:739) at org.openxava.controller.ModuleManager.setupModuleControllers(ModuleMa nager.java:162) at org.openxava.controller.ModuleManager.setModuleName(ModuleManager.jav a:718) at org.apache.jsp.xava.module\_jsp.\_jspService(module\_jsp.java:312) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:619)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.