Ant oracle:compileJsp errors in JDeveloper 10.1.3.5 with PolicyClassLoader

Question

Hi,
I am developing ant script to build and ADF 10g application through jDeveloper 10.1.3.5 and then later we'll running it on the app server.
As part of the ant script, when I use the oracle:compileJsp task to pre-compile jsps, I am getting NoClassDefFoundError: oracle/classloader/PolicyClassLoader
After a little research I found that this class is located in JDEV_HOME/j2ee/home/lib/pcl.jar
There is no way to get around the problem as the java process that is spawned by the oracle:compileJsp ant task has hard-coded classpath setting and pcl.jar is not one of them
I am not getting this error when I am using JDeveloper 10.1.3.4
So the questions are:
1) Is the oracle:compileJsp ant task supposed to use this classloader?
2) If yes, how can I make this class available to the java process spawned by the ant task?
3) If no, how can I make ant task no use the classloader?
regards - rutwik

Answer 1

There is a workaround for this issue.. instead of using standard <tt>oracle:compileJsp</tt> task you can do the following:
Add the following path entry in your ant build file
  <path id="ojspcInvokeClasspath">
    <path location="${oracle.home}/j2ee/home/lib/pcl.jar"/>
    <path location="${oracle.home}/j2ee/home/lib/ojsp.jar"/>
    <path location="${oracle.home}/j2ee/home/lib/oc4j-internal.jar"/>
    <path location="${oracle.home}/j2ee/home/lib/servlet.jar"/>
    <path location="${oracle.home}/j2ee/home/lib/commons-el.jar"/>
    <path location="${oracle.home}/j2ee/home/lib/bcel.jar"/>
    <path location="${oracle.home}/lib/xmlparserv2.jar"/>
    <path location="${oracle.home}/j2ee/home/lib/oc4j-schemas.jar"/>
    <path location="${oracle.home}/j2ee/home/jsp/lib/taglib/ojsputil.jar"/>
  </path>Then after bundling the war file do the following in your build.xml
    <java jar="${oracle.home}/j2ee/home/ojspc.jar" classpathref="ojspcInvokeClasspath" fork="true">
        <arg value="-addClasspath"/>
        <arg pathref="classpath"/>
        <arg line="'${view.deploy.dir}/${view.appname}.war'"/>
    </java>Thanks to guys on Metalink who suggested a similar workaround approach to compile indivisual pages. But that will not work if you have large no of pages ( > 10) in your application.
Pre-compiling pages inside a war file as mentioned above works and also is has better performance.
For those having access to Metalink they should be able to download the patch for the actual fix... sooon...