org.openxava.util.ElementNotFoundException

El módulo favicon.ico no está definido

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 web93

  • El módulo favicon.ico no está definido
  • via openxava by jlhm2012
    , 11 months ago
    El módulo Cliente no está definido
  • El módulo undefinedshow-filter.gif no está definido
  • Stack trace

    • org.openxava.util.ElementNotFoundException: El módulo favicon.ico no está definido at org.openxava.application.meta.MetaApplication.getMetaModule(MetaApplication.java:145) at com.openxava.naviox.impl.MetaModuleFactory.create(MetaModuleFactory.java:21) at com.openxava.naviox.Modules.isModuleAuthorized(Modules.java:182) at com.openxava.naviox.web.NaviOXFilter.doFilter(NaviOXFilter.java:60) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454) at java.lang.Thread.run(Thread.java:745)

    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.