In Release 11i deployment of a custom JSP or JSPs, in general, was done as follows:<\/p>\n
1. Copy the file (for example: mycustom.jsp) to the server in the $OA_HTML directory You will notice mycustom.jsp compiled in the cache directory of the middle tier server, as follows<\/p>\n cd $OA_HTML\/..\/_pages\/_oa__html<\/p>\n Listing this directory will display<\/p>\n _mycustom.class <\/p>\n Performing the same steps in Release 12 environment just shows a blank screen – result mycustom.jsp does not get compiled. <\/p>\n In Release 12 the (automatic) compilation of JSP is disabled and on runtime, only the pre-compiled JSP’s are picked up and displayed in the browser. This is the case with 11i as well, however, in 11i it was easier to deploy custom JSPs. <\/p>\n In cases where development activities are in abundance and JSP pages change often the default setting makes things a bit cumbersome to use and deployment takes a longer time. Each time a JSP is deployed a manual compilation, using the ojspCompile.pl, is needed. OC4J process needs to be restarted to pick up the modifications done to the custom JSP. <\/p>\n Follow the steps below to:<\/p>\n * Automatically have the JSP recompile when JSP code has changed (or at least the time stamp has changed) The objective is to change the setting for main_mode from justrun<\/strong> to recompile<\/strong> in<\/p>\n $INST_TOP directory<\/p>\n \/ora\/10.1.3\/j2ee\/oacore\/application-deployments\/oacore\/html\/orion-web.xml<\/p>\n This can be achieved by the following steps<\/p>\n * Use the Context editor to change the value for “s_jsp_main_mode” in the $INST_TOP\/ora\/10.1.3\/j2ee\/oacore\/application-deployments\/oacore\/html\/orion-web.xml file<\/p>\n has the following lines, under the init-param <\/strong>tag<\/p>\n main_mode * Restart the Middle Tier services<\/p>\n * Request a JSP in the browser which is compiled.<\/p>\n Notice that a new _ * Make a change to the JSP file<\/p>\n * Refresh the JSP file in the browser window. Notice that _ In Release 11i deployment of a custom JSP or JSPs, in general, was done as follows: 1. Copy the file (for example: mycustom.jsp) to the server in the…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-42","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/www.ibizsoftinc.com\/blog\/wp-json\/wp\/v2\/posts\/42","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ibizsoftinc.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ibizsoftinc.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ibizsoftinc.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ibizsoftinc.com\/blog\/wp-json\/wp\/v2\/comments?post=42"}],"version-history":[{"count":0,"href":"https:\/\/www.ibizsoftinc.com\/blog\/wp-json\/wp\/v2\/posts\/42\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.ibizsoftinc.com\/blog\/wp-json\/wp\/v2\/media?parent=42"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ibizsoftinc.com\/blog\/wp-json\/wp\/v2\/categories?post=42"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ibizsoftinc.com\/blog\/wp-json\/wp\/v2\/tags?post=42"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n 2. Using the browser URL, enter the following http:\/\/
\n_mycustom.java<\/p>\n
\n * See the new JSP, in a browser window, without having the need to restart the OC4J process.<\/p>\n
\n * Run Autoconfig to propagate the changes to the configuration files
\n * Verify that <\/p>\n
\nrecompile<\/p>\n
\nchange can be noticed in the browser<\/p>\n","protected":false},"excerpt":{"rendered":"