This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am thinking about your issue and having this questions for others: When the client access the JSP, how will WebLogic know where the corresponding compiled Servlet class is? So all it will do is again compile the jsp in its own package structure and then keep a reference of it for future requests. If you precompile your jsp's then in web.xml you need to map the url's to the generated servelt's instead on jsp's. I read on some other websites that precompiling JSP is mainly used to validate the jsp's for syntax errors at the same time I also heard that precompiling jsps will improve the response for the first request in production environment. I am a bit with the advantage/usage of the pre-compiling jsp. On a separate note: Here's 2 properties that can do the trick. pageCheckSeconds Default Value = 1 Desc = Sets the interval, in seconds, at which WebLogic Server checks to see if JSP files have changed and need recompiling. Dependencies are also checked and recursively reloaded if changed. If set to 0, pages are checked on every request. If set to -1,page checking and recompiling is disabled. precompile Default Value = false Desc = When set to true, WebLogic Server automatically precompiles all modified JSPs when the Web Application is deployed or re-deployed or when starting WebLogic Server.