Where are my compiled JSP pages on JBoss / WildFly?
WildFly application server places the source and compiled Servlets (derived from your JSP) under the standalone/tmp/<deployment_unit>/org/apache/jsp folder.
Let’s see an example. You have deployed a Web application named “hello.war” which contains,in the root folder, the hello.jsp page.
When requested, the following hello_jsp.java Servlet,java will be created and compiled:
tmp
├── auth
├── hello.war
│ └── org
│ └── apache
│ └── jsp
│ ├── hello_jsp.class
│ └── hello_jsp.java
├── startup-marker
└── vfs
└── temp
If running the server in Domain mode, the equivalent file system path will be:
domain/servers/<server_name>/tmp/<deployment_unit>/org/apache/jsp
JBoss AS 7 / JBoss EAP 6
If you are this server version, the same hello.jsp page would be placed in the following file system path:
tmp
├── auth
├── vfs
└── work
└── jboss.web
└── default-host
├── _
└── hello
└── org
└── apache
└── jsp
├── hello.class
└── hello_jsp.java
JBoss AS 5 / JBoss EAP 5
If you are running the embedded Tomcat server in JBoss AS 5, the compiled JSP files are under the folder $JBOSS_HOME\jboss-as\server\default\work\jboss.web\localhost_\org\apache\jsp
Recommended Articles
Discover Where JBoss EAP/WildFly Logs Are Located: Standalone vs Domain Mode
Learn where to find and view logs in JBoss EAP/WildFly, whether running in standalone or domain mode.
Efficient JSP Deployment Strategies for Java Applications
Deploy JSPs in exploded format for immediate changes with JBoss EAP 6/AS7 or WildFly, setting development attributes.
How to Start, Stop, and Restart WildFly and JBoss EAP
Learn how to manage WildFly application server lifecycle and troubleshoot issues. Explore standalone vs domain modes.
Mastering JBoss CLI Scripts for Domain Mode Operations
Learn how to configure resources, reach server nodes, and manage server groups with JBoss CLI scripts in domain mode.