Pre-compilation

Is it with WLS 4.5.1 possible to automatically pre-compile all JSP pages without having to do it manually for each one of them from the command line?

thank´s a lot for the information. i guess i try out some script some day. in
          case it works just fine i send it over to BEA.
          Martin
          Steve Hoffman wrote:
          > Michael Girdley wrote:
          > > Not out-of-the-box. But, it should be pretty reasonable to read a script
          > > that would think.
          > >
          > > If you do such a thing, I suggest submitting it to our developer site:
          > > developer.BEA.com.
          >
          > This is possible as I did it once when I worked at another company
          > (and therefore don't have access to the work anymore to post to the developer
          > site). However, one thing I want to note if you do try this. The compiled
          > pages contain a check for the .jsp file having changed. This means
          > that the compiled version of the page contains both the full path
          > to the original jsp file as well as the timestamp of the original
          > jsp file. So if you are going to pre-compile pages to move to
          > another server you'll have to make sure the full path is the
          > same on the destination server as where you originally compiled it.
          > You'll also have to preserve the timestamps (assuming both machines
          > are running clocks that are even close) when you tar/mv the files.
          > If either of these don't jive, then the page will re-compile itself
          > because it thinks it's stale (or can't determine for sure if it's stale
          > and err's on the side of caution).
          >
          > Just my $0.02 if you do try this.
          >
          > Steve

Similar Messages

Pre-Compiling JSPs while deploying a .war file in OC4J instance

Hi,
Is there any way to inform the OC4J instance to pre-compile the jsps in a .war file, while deploying..
Thanks for your responses,
Eshwar

Click on the project.
Open the context menu (right mouse button).
Expand the General item in the left list.
Select the Deployment Profiles item.
Select the deployment profile you need from the right.
Follow the wizard.
--olaf

JSP pre-compilation issues

Hi,
I'm trying to pre-compile one of our web applications using Jasper2 and i'm getting build failures. Our setup is like this,
In A.jsp
-- defines a use bean 'test'
--- includes B.jsp
In B.jsp
-- uses the bean 'test' to perform some operations
The pre-compilation steps fails effectively because b.jsp doesnt know about the use bean 'test'. Is this approach fundamentally wrong or is there any flag in the compiler settings we can use to solve this case. This is a third-party web apps which i'm trying to integrate into our solutions. Any help is appreciated.
Thanks
Mustafa

Hi,
I'm trying to pre-compile one of our web applications using Jasper2 and i'm getting build failures. Our setup is like this,
In A.jsp
-- defines a use bean 'test'
--- includes B.jsp
In B.jsp
-- uses the bean 'test' to perform some operations
The pre-compilation steps fails effectively because b.jsp doesnt know about the use bean 'test'. Is this approach fundamentally wrong or is there any flag in the compiler settings we can use to solve this case. This is a third-party web apps which i'm trying to integrate into our solutions. Any help is appreciated.
Thanks
Mustafa

I want to know the pre compiler jsp

please give information

see in one interview ,i was beign asked about the pre
compiler jsp.
i told him that i dont know.What did he ask about it?

Pre-compiled JSPs when deploying an EAR under WebLogic 6.1 SP4

Hello,
We have sucessfully pre-compiled JSP pages when working with and
deploying WAR files (WebLogic 6.1 SP4, Windows).
However, we can't seem to make it work when deploying EAR files.
Examing the "secret" unpacked directories after deployment doesn't
seem to help.
If we extract the WAR from the EAR and deploy it, everything is perfect.
Any ideas? Anyone able to make this work? If so, could you share the
output of
jar -tf yourCoolEarFileThatWorks.ear
as well as the same for the embedded WAR file?
Thank you,
Mike Leo

Some followup information.
We've changed the place where it looks for JSP classes using the
"workingDir" parameter in weblogic.xml.
And we also set "pageCheckSeconds" (also in weblogic.xml) to "-1".
Now, everything in the base directory comes up without being recompiled.
However, nothing in subfolders of the base directory is "picked up". Those
pages are still being compiled when they are accessed.
Any ideas welcome.
Mike Leo
On Tue, 05 Aug 2003 18:43:41 -0500, Michael Leo <[email protected]>
wrote:
Hello,
We have sucessfully pre-compiled JSP pages when working with and
deploying WAR files (WebLogic 6.1 SP4, Windows).
However, we can't seem to make it work when deploying EAR files.
Examing the "secret" unpacked directories after deployment doesn't
seem to help.
If we extract the WAR from the EAR and deploy it, everything is perfect.
Any ideas? Anyone able to make this work? If so, could you share the
output of
jar -tf yourCoolEarFileThatWorks.ear
as well as the same for the embedded WAR file?
Thank you,
Mike Leo

Pre-compilation of DSP objects

Could you please email me the Java class that pre-compiles a set of DSP objects at [email protected]
Thanks

Before you go off on the pre-compilation route - I would point out that pre-compiling has limitations.
(1) it's going to take a while to compile all your functions,
(2) you might spend time pre-compiling funcitons that would never be compiled (not just those that are never called, also functions that are only called from other functions).
(3) the compiled cache is limited you now need to pay (more) attention to filling it.
(4) all these compiled queries take up space
(5) the mechanism to pre-compile queries is going to take some effort to get working to your satisfaction.
What I'm getting at is there must be a reason that you feel you need to pre-compile - I assume that you have some queries that have long compilation times. Your best bet would be to have customer support sort those out for you. If they compiled very quickly - then you'd have no need for pre-compiling, correct?
Here is code written for ALDSP 2.5 that goes through the metadata and compiles functions. It is an ALDSP client - so you will have to go through the process of creating an ALDSP client (see edocs). It uses catalog services, so you will need to add catalog services to your ALDSP data space (see edocs).
import com.bea.dsp.RequestConfig;
import com.bea.dsp.dsmediator.client.DataServiceFactory;
import com.bea.ld.DSPAuditRecord;
import com.bea.ld.DataServiceAudit;
import com.bea.ld.metadata.DataServiceDocument;
import com.bea.ld.metadata.DataServiceDocument.DataService;
import com.bea.ld.metadata.DataServiceRefDocument;
import com.bea.ld.metadata.DataServiceRefDocument.DataServiceRef;
import com.bea.ld.metadata.FunctionDocument;
import com.bea.ld.metadata.FunctionDocument.Function;
import com.bea.ld.metadata.RelationshipDocument;
import com.bea.ld.metadata.RelationshipDocument.Relationship;
import com.bea.ld.server.audit.DataServiceAuditImpl;
import com.bea.dsp.dsmediator.client.exception.SDOMediatorException;
import com.bea.ld.QueryAttributes;
import com.bea.ld.filter.FilterXQuery;
import com.bea.ldAC.metadata.ParameterType;
import java.util.Iterator;
import java.util.List;
import java.util.Map;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import weblogic.jndi.Environment;
import java.util.Properties;
import java.util.Hashtable;
public class Client
public static void main(String[] args){
try{
DataServiceAudit dsAudit=null;
RequestConfig reqConfig = new RequestConfig();
reqConfig.enableFeature(RequestConfig.RETURN_DATA_SERVICE_AUDIT);
reqConfig.setStringArrayAttribute(RequestConfig.RETURN_AUDIT_PROPERTIES, attributes);
String appName="DSApp";
Context ctx = getInitialContext();
catalogservices.DataServiceRef csDSR =catalogservices.DataServiceRef.getInstance(ctx, appName);
int functioncounter = 0;
DataServiceRefDocument[] dataServiceRefDocs = csDSR.getDataServiceRefs( reqConfig );
for(int i=0; i< dataServiceRefDocs.length; i++){
DataServiceRefDocument dataServiceRefDoc=dataServiceRefDocs;
DataServiceRef dataServiceRef=dataServiceRefDoc.getDataServiceRef();
String dsName = dataServiceRef.getId();
//skipping all services under _catalogservices
// IT WOULD BE USEFUL TO ONLY COMPILE FUNCTIONS ACCESSIBLE FROM THE CLIENT (i.e. public).
if( (dsName.indexOf( "LogicalDS" ) != -1 ) )
System.out.println( "\n\n************");
System.out.println("DataServiceRef: " + dsName );
catalogservices.DataService csDS=catalogservices.DataService.getInstance(ctx,appName);
DataServiceDocument dataServiceDoc=csDS.getDataService(dataServiceRefDoc);
System.out.println("Functions: ");
FunctionDocument[] functionDocs=csDSR.getFunctions(dataServiceRefDoc);
for(int j=0; functionDocs != null && j<functionDocs.length; j++){
FunctionDocument functionDoc=functionDocs[j];
Function function=functionDoc.getFunction();
String funcName = function.getFunctionId().getName().getLocalPart();
System.out.println("\nFunction: "+ funcName );
ParameterType[] paratypes = function.getParameterArray();
String[] inPara = new String[paratypes.length];
RequestConfig config = new RequestConfig();
config.enableFeature(RequestConfig.COMPILE_ONLY );
config.setIntegerAttribute( QueryAttributes.FUNCTION_ARITY, inPara.length );
String dName = dsName.substring(0, ( dsName.length()-3) );
functioncounter++;
System.out.println("compiling function: " + functioncounter );
System.out.println("getting data service : " + "\nappName " + appName + "\nds name: " + dName );
com.bea.dsp.dsmediator.client.DataService ds = DataServiceFactory.newDataService( ctx, appName,dName );
ds.invoke( funcName, null, config );
System.out.println("The total functions are: " + functioncounter );
} catch(Exception e){
e.printStackTrace();
public static InitialContext getInitialContext() throws NamingException
Hashtable h = new Hashtable();
h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, "t3://localhost:7001");
h.put(Context.SECURITY_PRINCIPAL, "weblogic" );
h.put(Context.SECURITY_CREDENTIALS, "weblogic" );
System.out.println("Finished getting initialContext");
return new InitialContext( h );
static protected String[] attributes = new String[]{
"common",
"query"

The file '/foo.aspx' has not been pre-compiled, and cannot be requested

Hi All
I am using odp .net to access oracle data. I have also added oracle.dataaccess in my asp .net references. Everything works fine in my development and when I run the code through debugger. However, when I deploy the project in IIS, it gave me following error...
"The file '/foo.aspx' has not been pre-compiled, and cannot be requested
This is pretty generic error and I found out this is related to .Net assemblies.
By further investigation, I found that oracle.dataacess.dll is not present in the bin directory of a deployed web site. I am not sure why .net is dropping that dll in the deployment wizard.
Did anyone encounter this problem before?
I got a workaround for now that manually copting dll into the bin directory of deplyed web site. However, I am looking for more robust and technical answer..
The strange thing is I have been deploying the web site the same way for last 8 months and never encountered this problem.
thanks a lot..
Message was edited by:
amazon

If you add a reference to Oracle.DataAccess at design time it will be added as an assembly definition to web.config. Then you don't need a copy in your bin dir and it will be found in the GAC.
Eric

Pre-compilation with ojspc

I'm using Oracle Application Server 9.0.4.1 and it's OJSPC tool to pre-compile jsp files at build-time. During the compilation I get the following error:
Translating file: C:\Documents and Settings\antio\Local Settings\Temp\tmp3860\index.jsp
File not found: C:\work\app\index.jsp
ant task that runs ojspc:
<target name="jsp">
     <java jar="${j2ee.home}/ojspc.jar" fork="yes" failonerror="true" jvmversion="1.4.1" >
          <arg value="-verbose"/>
          <arg value="-xmlValidate"/>
          <arg value="-extend"/>
          <arg value="com.orionserver.http.OrionHttpJspPage"/>
          <arg value="app.war"/>
     </java>
</target>
It expands the app.war file, and starts to translate index.jsp, but then an error occurs. It searches C:\work\app\index.jsp file, though index.jsp actually is in app.war root directory, which is located in app/build directory. Build script is run from C:\work\app directory.
*.jsp is declared as not found only if it contains some jsp tags, written in XML-syntax. Jsp-s that contain only plain text or html code, or are written in jsp-like syntax will be pre-compiled normally.
Steps to reproduce.
1) download app.zip file and unzip it
http://apunkto.pri.ee/app.zip
2) configure build.properties file, set the Oracle server location
3) run build (default task jsp)
4) error occurs.
Any suggestions would be appreciated,
Thank you.

OK, the patch I was talking about should be patch 3222328.
It seems that you were seeing the wrong interaction between patch 3222328 and patch 3447842. I am not sure what to do. The best I can suggest for you is to apply patch 3447842 before applying patch 3222328. If it still does not work, please raise an oracle support ticket and let me know the ticket number.

What is the Advantage and Disadvantage of Pre-Compiled JSP

Hi All,
What is the advantage and disadvantage of using pre-compiled JSP

Pro:
By pre-compiling your JSPs you don't need a java compiler on the server - just a jre.
The result? No java compiler on the server means a potential security hole patched - people can't just write and deploy jsp's willy nilly on the server.
You KNOW that all your JSPs compile before you visit them - because you have compiled them all :-). It won't fail because of a stupid spelling miskate that prevents compilation. That doesn't mean they will run without error of course...
Con:
Compiling the JSPs ties them to a particular server - unless you take the runtime along with them.

Pre-compiled JSPs getting re-compiled by the server

For our project we are using wlappc to pre-compile JSPs and generate EJB classes. We are using the split directory format, so this is what the task looks like -
<target name="appCompile" depends="init" >
<delete dir="${ear.dist}" />
<mkdir dir="${ear.dist}" />
<wlpackage srcdir="${ear.src}" destdir="${ear.build}"
toDir="${ear.dist}" />
     <wlappc source="${ear.dist}" verbose="true" classpath="${classpath}" />
</target>
After this, we are using wldeploy to deploy the application to another server.
This is how the task looks like -
     <target name="beadeploy" depends="init" >
     <wldeploy action="deploy"
          source="${src.dir}/dist/myapp.ear"
          name="myApplication" remote="true"
          user="${deploy.username}" password="${deploy.password}"
          verbose="true" adminurl="t3://${deploy.host}:${deploy.port}"
          upload="true"
          debug="true" targets="${deploy.target}"/>
     </target>
The problem that I am facing is that, even after re-compiling the JSPs, they get compiled again by the server when accessed for the first time !
We using Weblogic 8.1.2.0. Can you please provide a soplution for this ?

Hi,
The following steps help you troubleshoot why you may be having problems with JSPs recompiling:
1. When invoking jspc, your classpath must contain the same release, service-pack, and any temporary patches as the servers you wish to deploy on. Otherwise, the Server will read the JSPs as being compiled on a different version of the WebLogic, and will recompile them all.
2. You should invoke jspc from the root directory of your open-directory exploded) WebApp or specify -webapp) and use the -d option to deploy the generated classes to the WEB-INF/classes directory. You can then archive these JSP classes into a JAR if you wish from the WEB-INF/classes directory.
3. The JSPs should then be deployed either individually to the WEB-INF/classes/jsp_servlet directory or in a JAR file under the WEB-INF/lib directory.
4. One other thing that could cause JSPs to be recompiled is if the timestamp of the class is different from that of the source.
Also, if your ant classpath is different from whatever WLS-related classpath entries you use to run WLS, this may cause problems, too.
-- Prasanna
Prasanna Yalam

Problem with pre-compiling jsp's

          hi,
          we have an .ear running on wls 6.0 sp2.
          Our app has a web component(part of the .ear) as well which has tld's & jsp.We
          are following the struts framework.
          We configured the <jsp-descriptor> element in the weblogic.xml file to pre-compile
          the jsp's..but the server complains of the following
          any suggestions would be appreciated
          ==================================================================================================================================
          <Jan 9, 2002 4:00:06 PM EST> <Error> <HTTP> <[WebAppServletContext(3001228,ppp)]
          failure pre-compiling JSP's
          java.lang.NullPointerException
          at weblogic.servlet.jsp.Jsp2Java.makeReader(Jsp2Java.java:232)
          at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:112)
          at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:253)
          at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:124)
          at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:44)
          at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebAppServletContext.java:2003)
          at weblogic.servlet.internal.dd.DescriptorLoader.initFromWebApp(DescriptorLoader.java:742)
          at weblogic.servlet.internal.dd.DescriptorLoader.createServletContext(DescriptorLoader.java:359)
          at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:467)
          at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:404)
          at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
          at weblogic.j2ee.Application.addComponent(Application.java:133)
          at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:327)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:143)
          at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
          at $Proxy44.addWebDeployment(Unknown Source)
          at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1012)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:313)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:277)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:232)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:192)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
          at $Proxy41.updateDeployments(Unknown Source)
          at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2299)
          at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:240)
          at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:122)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:439)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:180)
          at $Proxy33.start(Unknown Source)
          at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:435)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1033)
          at weblogic.management.Admin.finish(Admin.java:493)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
          at weblogic.Server.main(Server.java:35)
          >
          <Jan 9, 2002 4:00:06 PM EST> <Debug> <HTTP> <Exception thrown while loading ppp:
          weblogic.utils.NestedException: failure pre-compiling JSP's - with nested exception:
          [java.lang.NullPointerException]>
          <Jan 9, 2002 4:00:06 PM EST> <Error> <J2EE> <Error deploying application ppp:
          Could not load ppp>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[HTTP myserver] Loading web app: wl_management_internal2>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[HTTP myserver] Loading wl_management_internal2
          from WAR file: C:\engr\project\ppp\.\config\Synchronoss\applications\.wl_temp_do_not_delete\wl_local_comp45831.war>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[Default WebApp] extracting classfiles
          to C:\engr\project\ppp\.\config\Synchronoss\applications\.wl_temp_do_not_delete\WEB-INF\_tmp_war_myserver_myserver_wl_management_internal2:>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[Default WebApp] extracted classfiles
          successfully...>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[WebAppServletContext(6559849,wl_management_internal2)]
          registering JSPServlet with initArgs '[JspConfig: verbose=true,packagePrefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\engr\project\ppp\.\config\Synchronoss\applications\.wl_temp_do_not_delete\WEB-INF\_tmp_war_myserver_myserver_wl_management_internal2,pageCheckSeconds=1,superclass=null,keepgenerated=false,encoding=null,defaultfilename=index.jsp,noTryBlocks=false]'>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[WebAppServletContext(6559849,wl_management_internal2)]
          registering classpath servlet with initArgs 'null'>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[WebAppServletContext(6559849,wl_management_internal2)]
          registering getior servlet with initArgs 'null'>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <J2EE> <Deployed : wl_management_internal2>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <J2EE> <Deployed MailSession named com.bea.wlpi.MailSession>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <Initializing WEB server myserver>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[HTTP myserver] Loading web app: DefaultWebApp_myserver>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[HTTP myserver] Loading DefaultWebApp_myserver
          from directory: .\config\Synchronoss\applications\DefaultWebApp_myserver>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[WebAppServletContext(4157813,DefaultWebApp_myserver)]
          registering JSPServlet with initArgs '[JspConfig: verbose=true,packagePrefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\engr\project\ppp\.\config\Synchronoss\applications\DefaultWebApp_myserver\WEB-INF\_tmp_war_myserver_myserver_DefaultWebApp_myserver,pageCheckSeconds=1,superclass=null,keepgenerated=false,encoding=null,defaultfilename=index.jsp,noTryBlocks=false]'>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[WebAppServletContext(4157813,DefaultWebApp_myserver)]
          registering classpath servlet with initArgs 'null'>
          <Jan 9, 2002 4:00:06 PM EST> <Info> <HTTP> <[WebAppServletContext(4157813,DefaultWebApp_myserver)]
          registering getior servlet with initArgs 'null'>


[att1.html]

Pre-compiling JSP's

I am using build.cmd to create an ear and war of my application. I am
          having problems with the code below:
          @REM Create WAR file
          COPY src\dd\war\WEB-INF\* stage\WEB-INF
          COPY src\dd\war\WEB-INF\tlds\* stage\WEB-INF\tlds
          java -classpath %CLASSPATH%;./stage/WEB-INF/classes;./src/jsp;./stage
          weblogic.jspc -docroot src/jsp -d stage/WEB-INF/classes src/jsp/*/*.jsp
          jar cv0f stage/edeploy2WAR.war -C stage WEB-INF -C src/jsp .
          On the third line (the one that starts with java) - I get the following
          error:
          [jspc] warning: expected file C:\edeploy2\src\jsp\WEB-INF\web.xml not found,
          tag
          libraries cannot be resolved.
          [jspc] parsing /*/*.jsp:
          Error: translation of /*/*.jsp failed: java.io.FileNotFoundException:
          src\jsp\*\
          *.jsp (The filename, directory name, or volume label syntax is incorrect)
          Error: [jspc]: 1 file(s) failed:
          /*/*.jsp
          I am trying to pre-compile all the jsp's that are located in 10
          subdirectories under src/jsp/.. subdir
          I shouldn't need a web.xml file should I?
          Thanks,
          Matt


I am now using the following command, which seems to work:
          java weblogic.jspc -compileAll -webapp src\jsp -d stage/WEB-INF/classes
          However, when it begins, it looks for WEB-INF in src\jsp - is there anyway
          to make it look in src\dd for WEB-INF?
          Secondly, I added src/WEB-INF/web.xml for my tag libraries, but now I get
          the following:
          [jspc] resolved taglib uri 'RDBMS' to taglib-location
          ../../src/dd/WEB-INF/tlds/
          rdbmstags6_0.tld:
          [jspc] looking for taglib uri RDBMS as resource /WEB-INF/RDBMS in Web
          Applicatio
          n root:
          [jspc] looking for taglib uri RDBMS as resource RDBMS in Web Application
          root:
          Error: translation of /dev/DB_ConfigurationLocation.jsp failed:
          weblogic.servlet
          .jsp.JspException: (line 5): Could not parse deployment descriptor:
          java.io.IOEx
          ception: cannot resolve 'RDBMS' into a valid tag library
          Error: [jspc]: 1 file(s) failed:
          /dev/DB_ConfigurationLocation.jsp
          Any ideas?
          Thanks,
          Matt
          "Mettu Kumar" <[email protected]> wrote in message
          news:[email protected]...
          > Matt,
          >
          > I use a batch file with following contents. While compiles all my jsp's
          > (including ones in subfolders).
          >
          > java weblogic.jspc -classpath %CLASSPATH% -compileAll -webapp
          > e:\bea\wlserver6.0sp1\config\mydomain\applications\DefaultWebApp_myserver
          >
          > Hope this helps you.
          >
          > Thanks,
          > Kumar.
          >
          > Matt Raible wrote:
          >
          > > How do I change this line?
          > >
          > > java -classpath %CLASSPATH%;./stage/WEB-INF/classes;./src/jsp;./stage
          > > weblogic.jspc -docroot src/jsp -d stage/WEB-INF/classes src/jsp/*/*.jsp
          > >
          > > Thanks,
          > >
          > > Matt
          > >
          > > "Mettu Kumar" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > Matt,
          > > >
          > > > Why not use -webapp option which should fix your problem?
          > > >
          > > > Thanks,
          > > > Kumar.
          > > >
          > > > Matt Raible wrote:
          > > >
          > > > > I am using build.cmd to create an ear and war of my application. I
          am
          > > > > having problems with the code below:
          > > > >
          > > > > @REM Create WAR file
          > > > > COPY src\dd\war\WEB-INF\* stage\WEB-INF
          > > > > COPY src\dd\war\WEB-INF\tlds\* stage\WEB-INF\tlds
          > > > > java -classpath
          %CLASSPATH%;./stage/WEB-INF/classes;./src/jsp;./stage
          > > > > weblogic.jspc -docroot src/jsp -d stage/WEB-INF/classes
          src/jsp/*/*.jsp
          > > > > jar cv0f stage/edeploy2WAR.war -C stage WEB-INF -C src/jsp .
          > > > >
          > > > > On the third line (the one that starts with java) - I get the
          following
          > > > > error:
          > > > >
          > > > > [jspc] warning: expected file C:\edeploy2\src\jsp\WEB-INF\web.xml
          not
          > > found,
          > > > > tag
          > > > > libraries cannot be resolved.
          > > > > [jspc] parsing /*/*.jsp:
          > > > > Error: translation of /*/*.jsp failed:
          java.io.FileNotFoundException:
          > > > > src\jsp\*\
          > > > > *.jsp (The filename, directory name, or volume label syntax is
          > > incorrect)
          > > > > Error: [jspc]: 1 file(s) failed:
          > > > > /*/*.jsp
          > > > >
          > > > > I am trying to pre-compile all the jsp's that are located in 10
          > > > > subdirectories under src/jsp/.. subdir
          > > > >
          > > > > I shouldn't need a web.xml file should I?
          > > > >
          > > > > Thanks,
          > > > >
          > > > > Matt
          > > >
          >

Failure in pre-compiling JSP's

          Hi,
          I am getting the following error while pre-compiling a jsp (showcode.jsp).
          I am using weblogic 5.1 SP8.
          Wed Oct 24 12:03:09 MDT 2001:<E> <WebAppServletContext-quote> cannot make temp
          directory '/cemr2/dev1/app/examples/j
          sp/tagext/quote/WEB-INF/_tmp_war_quote', will not be able to compile JSPs
          Wed Oct 24 12:03:09 MDT 2001:<I> <WebAppServletContext-quote> checking /showcode.jsp:
          Wed Oct 24 12:03:11 MDT 2001:<E> <WebAppServletContext-quote> failure pre-compiling
          JSP's
          java.io.FileNotFoundException: /cemr2/dev1/app/examples/jsp/tagext/quote/WEB-INF/_tmp_war_quote/examples/jsp/tagext/
          sql/_showcode.java (No such file or directory)
          at java.io.FileOutputStream.open(Native Method)
          at java.io.FileOutputStream.<init>(FileOutputStream.java, Compiled Code)
          at java.io.FileOutputStream.<init>(FileOutputStream.java, Compiled Code)
          at java.io.FileOutputStream.<init>(FileOutputStream.java, Compiled Code)
          at java.io.FileWriter.<init>(FileWriter.java, Compiled Code)
          at weblogic.servlet.jsp.Jsp2Java.makeOutputStream(Jsp2Java.java, Compiled Code)
          at weblogic.utils.compiler.CodeGenerator.generateCode(CodeGenerator.java, Compiled
          Code)
          at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java, Compiled
          Code)
          at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java, Compiled Code)
          at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java, Compiled Code)
          at weblogic.servlet.internal.ServletContextImpl.precompileJSPs(ServletContextImpl.java,
          Compiled Code)
          at weblogic.servlet.internal.dd.DescriptorLoader.createServletContext(DescriptorLoader.java,
          Compiled Code)
          at weblogic.t3.srvr.HttpServer.loadWARContext(HttpServer.java, Compiled Code)
          at weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java, Compiled
          Code)
          at weblogic.t3.srvr.HttpServer.start(HttpServer.java, Compiled Code)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
          at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java, Compiled Code)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.Server.startServerDynamically(Server.java, Compiled Code)
          at weblogic.Server.main(Server.java, Compiled Code)
          at weblogic.Server.main(Server.java, Compiled Code)


          << cannot make temp directory '/cemr2/dev1/app/examples/j sp/tagext/quote/WEB-INF/_tmp_war_quote',
          will not be >>
          You don't have sufficiend permission to crease directory.
          Thnaks
          Jignesh Patel
          "Sreenivas Kotapati" <[email protected]> wrote:
          >
          >Hi,
          >
          >I am getting the following error while pre-compiling a jsp (showcode.jsp).
          >
          >I am using weblogic 5.1 SP8.
          >
          >Wed Oct 24 12:03:09 MDT 2001:<E> <WebAppServletContext-quote> cannot
          >make temp
          >directory '/cemr2/dev1/app/examples/j
          >sp/tagext/quote/WEB-INF/_tmp_war_quote', will not be able to compile
          >JSPs
          >Wed Oct 24 12:03:09 MDT 2001:<I> <WebAppServletContext-quote> checking
          >/showcode.jsp:
          >Wed Oct 24 12:03:11 MDT 2001:<E> <WebAppServletContext-quote> failure
          >pre-compiling
          >JSP's
          >java.io.FileNotFoundException: /cemr2/dev1/app/examples/jsp/tagext/quote/WEB-INF/_tmp_war_quote/examples/jsp/tagext/
          >sql/_showcode.java (No such file or directory)
          > at java.io.FileOutputStream.open(Native Method)
          > at java.io.FileOutputStream.<init>(FileOutputStream.java, Compiled
          >Code)
          > at java.io.FileOutputStream.<init>(FileOutputStream.java, Compiled
          >Code)
          > at java.io.FileOutputStream.<init>(FileOutputStream.java, Compiled
          >Code)
          > at java.io.FileWriter.<init>(FileWriter.java, Compiled Code)
          > at weblogic.servlet.jsp.Jsp2Java.makeOutputStream(Jsp2Java.java, Compiled
          >Code)
          > at weblogic.utils.compiler.CodeGenerator.generateCode(CodeGenerator.java,
          >Compiled
          >Code)
          > at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
          >Compiled
          >Code)
          > at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java, Compiled
          >Code)
          > at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java, Compiled
          >Code)
          > at weblogic.servlet.internal.ServletContextImpl.precompileJSPs(ServletContextImpl.java,
          >Compiled Code)
          > at weblogic.servlet.internal.dd.DescriptorLoader.createServletContext(DescriptorLoader.java,
          >Compiled Code)
          > at weblogic.t3.srvr.HttpServer.loadWARContext(HttpServer.java, Compiled
          >Code)
          > at weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java,
          >Compiled
          >Code)
          > at weblogic.t3.srvr.HttpServer.start(HttpServer.java, Compiled Code)
          > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
          > at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java, Compiled Code)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.Server.startServerDynamically(Server.java, Compiled Code)
          > at weblogic.Server.main(Server.java, Compiled Code)
          > at weblogic.Server.main(Server.java, Compiled Code)
          >

Ntop pre-compiled for Snow Leopard?

I was looking for a network traffic monitor and found ntop promising. Unfortunately the 3.2 version -the only binary version I found for Mac- is too old and does not work on Snow Leopard. I have tried to compile ntop 3.3.10 but without success (libraries missing even if Xcode installed, etc.). Does anyone know where I can find a decent ntop version pre-compiled and fully working on SL?

If you're brave, MacPorts has a later version of ntop. It requires installing MacPorts and all its associated cruft, thought.
(IMHO a better solution would be to find what those dependencies are and get a local build working. Given the nature of ntop there are some significant dependencies so it might take a little time but you'd certainly learn from the experience. )

Auto deploy pre-compiled JSP

Hello
In the post of gadegaard in november 2002, there was a problem to au deploy pre-compiled JSP. Is this problem has been fix in the 9.0.4 OC4J version ?
If yes, is it sufficient to create a "_pages" directory in the war (the war is contained in an ear) and auto deploy it ? Because my pre-compiled JSP are not deployed.
Tanks in advance for your answer
Emmanuelle

Emmanuelle:
There are two ways to use the precomiled JSP files.
Method one: You can just copy the generated JSP page implementation classes to the directory application-deployments/yourApp/yourWebApp/persistence/_pages. If the init-param "main_mode" of jsp servlet of your web app is reload, then these classes will be used without stopping the server. This is the fastest way in development.
Method two: You can packaged the generated JSP page implementation classes into a jar just like any other java class libraries. Then create your war with that jar inside WEB-INF/lib. Make sure the init-param "main_mode" of jsp servlet in your web.xml is justrun. Now you have a deployable war file. You can deploy the war file (within an ear file) to oc4j and access the JSP page.
Please tell me if either of thse methods works for you
Please note since oc4j 10.1.3, ojspc will package the generated classes into a jar under WEB-INF/lib if given an war or ear file.

Pre-compilation

Similar Messages

Maybe you are looking for