JSP and compiling

Question

How do I get weblogic server not to compile the jsp at all and just use the class file that I generated from the JSP?
          

Answer 1

          There is a bug that was fixed in 6.1 SP3 related to the jsp dependency checker
          that was causing jsps to be recompiled when not necessary (i.e. when you'd already
          shipped a valid class file).
          The trouble with setting a working directory as described below is it tends to
          break badly when you want to release the same app across different OS - we develop
          on NT but run on Solaris, and D:\ means nothing there!
          So your best bet for jsp joy is to have your buildsystem precompile all the jsps,
          and upgrade to SP3 if you're still on 6.1
          simon.
          Ann Cao <[email protected]> wrote:
          >Issue 068247 is not really a bug. It's more a documentation issue. The
          >WebLogic
          >on-line doc has fixed it by adding the following at
          >http://e-docs.bea.com/wls/docs70/adminguide/web_server.html:
          >
          >"By default JSPs are compiled into the servers' temporary directory the
          >location
          >for which is (for a server: "myserver" and for a webapp: "mywebapp"):
          ><domain_dir>\myserver\.wlnotdelete\appname_mywebapp_4344862
          >
          >The server deletes the temp directory (and thus the default working directory
          >for the jsps) each time the server is restarted. If the JSPs are configured
          >to
          >be precompiled they will be precompiled each time the server restarts.
          >
          >To avoid this there are following options:
          >
          >
          >Precompile the generated classes into your WEB-INF/classes directory
          >(or a jar
          >file in WEB-INF/lib).
          >
          >Set a workingDir for the jsp-descriptor in your weblogic.xml
          ><jsp-descriptor>
          >
          ><jsp-param> <param-name>workingDir</param-name>
          ><param-value>d:\jsp_store</param-value> </jsp-param>
          >
          ></jsp-descriptor>
          >
          >After this is done the precomiled classes will not be deleted each time
          >the
          >server restarts and they will not be recompiled."
          >
          >
          >
          >
          >
          >Peter Kim wrote:
          >
          >> Hi,
          >>
          >> In the Release Notes for Weblogic 7.x, under Known Issues, it says:
          >> "The JSPs included with WebLogic Server 7.0 are not being pre-compiled
          >> before they are accessed for the first time. If you are deploying
          >> precompiled JSPs, WebLogic Server may recompile them to the /wlnotdelete/
          >> directory. " (068247)
          >>
          >> So apparently it is a known issue that sometimes precompiled pages
          >may not
          >> be recognized
          >> properly and Weblogic will recompile them.
          >>
          >> Could you give more information on the status of this bug?
          >>
          >> My server on Windows is an admin server. Everything else looks good.
          >> I still have problems with recompilation.
          >>
          >> Thank you very much,
          >> Peter Kim
          >>
          >> "Ann Cao" <[email protected]> wrote in message
          >> news:[email protected]...
          >> > It shouldn't matter where you compile it. But the classpath you used
          >to
          >> compile
          >> > JSP and the classpath you used to run the application should contain
          >same
          >> > WebLogic classes and in the same order (weblogic.jar, service pack,
          >> patches,
          >> > etc.). Also, is the server you are running on Windows an Admin server
          >or a
          >> > managed server? There was an issue that managed server always compiles
          >> JSP.
          >> >
          >> > Peter Kim wrote:
          >> >
          >> > > Hello,
          >> > >
          >> > > Does it matter if there's a difference between the operating system
          >on
          >> > > the machine that did the original compilation and the machine that
          >> > > is running the application?
          >> > >
          >> > > I'm currently trying to figure out a problem where the precompiled
          >> > > jsp pages are being picked up properly in UNIX but not on
          >> > > Windows (in Windows, the jsp pages are being recompiled at run-time).
          >> > >
          >> > > Thanks!
          >> > > Peter
          >> > >
          >> > > "Ann Cao" <[email protected]> wrote in message
          >> > > news:[email protected]...
          >> > > > Please compile JSPs into WEB-INF/classes/jsp_servlet directory.
          >When
          >> you
          >> > > compile JSPs, please make sure that the server
          >> > > > build version (WebLogic version, service pack level, and patches)
          > is
          >> the
          >> > > same as the server on which you deploy your
          >> > > > webapp.
          >> > > >
          >> > > > Chris Pesarchick wrote:
          >> > > >
          >> > > > > How do I get weblogic server not to compile the jsp at all
          >and just
          >> use
          >> > > the class file that I generated from the JSP?
          >> > > >
          >> > > > --
          >> > > > Regards,
          >> > > > Ann
          >> > > > Developer Relations Engineer
          >> > > > BEA Support
          >> > > >
          >> > > >
          >> >
          >> > --
          >> > Regards,
          >> > Ann
          >> > Developer Relations Engineer
          >> > BEA Support
          >> >
          >> >
          >
          >--
          >Regards,
          >Ann
          >Developer Relations Engineer
          >BEA Support
          >
          >