Note that there are some explanatory texts on larger screens.

plurals
  1. POReplace Weblogic Jsp Compiler
    text
    copied!<p>We recently migrated our project from IAS OJDBC to Oracle Weblogic 10.3.3. We are using Eclipse Indigo.</p> <p>The problem we've run into is that some JSPs are interpreted into much larger java files than before, and for some of them the "service" function is larger than 64K after compilation, which is apparently larger than the maximum size allowed for a function in the JVM.</p> <p>We've noticed with one JSP file, that the size of the old java file of the JSP that was compiled in the OJDBC server (about 5000 lines of code for the "service" function) is roughly half the size of the new file.</p> <p>One solution I've found online is to "cut" the JSP into pieces and then use the "jsp:include" directive to view them as one page.</p> <p>But I want to tell Eclipse or Weblogic (or both) to use a different JSP interpreter (the part that converts JSP into java), because the difference is so big.</p> <p>Is there a way to do that?</p> <p>Thanks, Malki.</p> <p><strong>EDIT-</strong></p> <p>I have found this documentation: <a href="http://docs.oracle.com/cd/E13222_01/wls/docs81/jsp/reference.html#65756" rel="nofollow">Using the WebLogic JSP Compiler</a>. Under "Precompiling JSPs" they explain about a parameter called "compilerclass" that lets you define the JSP compiler class.</p> <p>The problem is that this is documentation for BEA WebLogic Server 8.1, but I am using Oracle WebLogic Server 10.3.3. I looked for the same parameter in the documentation of 10.3.3 but couldn't find it. Does anyone know if it still exists in this version? And where I can find it?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload