You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 112 Next »

Download, install and configure the Oracle OC4J 10.1.3.5 stand alone server

${renderedContent}

Download

${renderedContent}

Install

${renderedContent}

Configure

${renderedContent}

You will be asked to enter and confirm a password.  Pick a password that is easy for you to remember.  You will need to use this password when configuring Maven.

Getting Better Debugging Information  From OC4J

By default, some run time errors that you'll see when testing web apps in OC4J are not too helpful.  You can coax OC4J into giving you more information about certain errors by making the following changes in global-web-application.xml:

Open ${ORACLE_HOME}/j2ee/home/config/global-web-application.xml with a text editor.

  1. Turn on "development" mode - in the <orion-web-app> section at the top of the file, change the "development" setting to true:
    <orion-web-app
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-web-10_0.xsd"
      jsp-cache-directory="./persistence"
      servlet-webdir="/servlet"
      development="true"
      jsp-timeout="0"
      jsp-cache-tlds="standard"
      schema-major-version="10"
      schema-minor-version="0">
    
  2. Turn on debug mode. In the "jsp" servlet section, set a parameter debug_mode to true. The section should look like this:
    <servlet>
          <servlet-name>jsp</servlet-name>
          <servlet-class>oracle.jsp.runtimev2.JspServlet</servlet-class>
          <init-param>
            <param-name>debug_mode</param-name>
            <param-value>true</param-value>    
          </init-param>
          <load-on-startup>0</load-on-startup>
    </servlet>
    
    With these settings, you should get more meaningful messages in your browser when you run into certain errors (JSP syntax errors for example).
    ${renderedContent}
  • No labels