WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  Precompile JSP files while deployment

    Posted 11/17/14 10:56 AM
    Hi,

    What happen when we check(check box) the Precompile JSP files while deployment and what happen when we uncheck it?

    What would be the diffrence while checking it and unchecking it?


  • 2.  Precompile JSP files while deployment

    Posted 11/19/14 02:00 PM
    Hi Group,

    Finally I found the answer for my above query.

    By default, the JavaServer Pages (JSP) engine translates a requested JSP file, compiles the .java file, and loads the compiled servlet into the run-time environment. You can change the JSP engine default behaviour by indicating a JSP file should never be translated or compiled at run-time, even when a .class file does not exist.

    If run-time compilation is disabled, you must precompile the JSP files, which provides the following advantages:

       *Reduces compilation related disk operations.
        *Minimizes disk storage requirements necessary for handling temporary .java files generated during a run-time compilation.
        *Allows you to not include the JSP source files in the application.
        *Allows verification that a JSP file compiled successfully before deploying and installing the application in WebSphere Application Server.



Related Content