4.2.7. Debug and Resolve JBoss Seam Debug Page Errors
After you migrate and successfully deploy your application, you may encounter a runtime error that redirects you to the "JBoss Seam Debug" page. The URL for this page is "http://localhost:8080/APPLICATION_CONTEXT/debug.seam". This page allows you to view and inspect the Seam components in any of the Seam contexts associated with your current login session.
Figure 4.1. JBoss Seam Debug Page
The most likely reason you are redirected to this page is because Seam has caught an Exception that was not handled in the application code. The root cause of the exception can be often be found in one of the links on the "JBoss Seam Debug Page".
Procedure 4.11.
- Expand the
Component
section on the page and look for theorg.jboss.seam.caughtException
component. - The cause and stacktrace should point you to the missing dependencies.
Figure 4.2. Component
org.jboss.seam.caughtException
information - Use the technique described in Section 4.2.2, “Debug and Resolve ClassNotFoundExceptions and NoClassDefFoundErrors” to resolve module dependencies.In the example above, the simplest solution is to add
org.slf4j
to theMANIFEST.MF
Manifest-Version: 1.0 Dependencies: org.slf4j
Another option is to add a dependency for the module to thejboss-deployment-structure.xml
file:<jboss-deployment-structure> <deployment> <dependencies> <module name="org.slf4j" /> </dependencies> </deployment> </jboss-deployment-structure>