Precompiling JSP files

[JeanLouis Marechaux]

Hi folks.
How can I precompile JSP pages when I install an EAR file with WAS AE 4.x ??
I remember there was an option (yes/no) during the deploy process with WAS Single server edition.
Sounds like this option is gone with WAS AEE.
So how can I do it ?

[JeanLouis Marechaux]

Hi Bill,
You can force WebSphere to precompile JSPs using the property preCompileJSPs="true" in the file ibm-web-ext.xmi :

<webappext:WebAppExtension xmi.id="WebAppExtension_1" 
    reloadInterval="0" 
    reloadingEnabled="false" 
    defaultErrorPage="error.jsp" 
    fileServingEnabled="true" 
    directoryBrowsingEnabled="true"      serveServletsByClassnameEnabled="false" 
    preCompileJSPs="true">
      <webappext:WebAppExtension.webApp>
  

HTH.
[ July 12, 2002: Message edited by: Bill Bailey ]

[SJ Adnams]

I think it needs to be precompilejsps=true (lower case), never tried it, but I remember reading something like that on a n.g.
Simon

[JeanLouis Marechaux]

Actually, I did not try it, so I can't certify the upper cas is the good one.
Nevertheless, when you set the "Pre compile JSP" property from AAT, it modifies the ibm-web-ext.xmi adding :
preCompileJSPs="true"
So, if the case (upper/lower) is not correct, it sounds like a AAT bug

[Baba Batsha]

wait..wait..There is a bug in WAS.
The java code produced by the precompile procedures are not the same when accessed normally.
IBM has an e-fix for this.
Apply it first and play with precompile options.

[JeanLouis Marechaux]

Originally posted by Baba Batsha:
wait..wait..There is a bug in WAS.
The java code produced by the precompile procedures are not the same when accessed normally.
IBM has an e-fix for this.
Apply it first and play with precompile options.

Baba,
Do you have the efix number.
'm unable to find it ... plz help.

[Se Ravin]

I have used ,JspBatchCompiler.sh in solaris with WAS 4.0.2 itz really cool...

[Baba Batsha]

do you have a hammer?..take it and hit my head.
The e-fix is for 3.5.x and it is fixed by FixPack 6 which includes the following e-fix
"PQ53329 JSPBATCHCOMPILER PRODUCES DIFFERENT JAVA CODE THAN NORMAL COMPILATION"
This is not a problem with WAS 4.0.x
Since I work simultaneously with 3.5.x and 4.0.x I mess up the issue.
So.. go ahead with Jsp Batch compiler as posted above.

[Shalini Komarla]

I recently came across an issue with JSPBatchCompiler for WAS 4.0.2 Here is the link to the e-fix. I am not running 4.0.2, so I cannot tell you much more about this.
http://www-1.ibm.com/support/docview.wss?uid=swg24001138