Jsp precompile problem

hi to you all (using WLS 6.1 sp1, win2000)
          until today I didn't use the prcompile flag in weblogic.xml and my jsps have
          been complied on access -> no problems whatsoever. today I wanted to try the
          precompile option and after having added this flag -BANG- no deploying
          possible anymore. this is ther log snipplet:
          <snip>
          ####<22.11.2001 14:10:35 CET> <Info> <HTTP> <ws-vep> <myserver> <Application
          Manager Thread> <> <> <101047>
          <[WebAppServletContext(51375,cyberibisng,/cyberibisng)] checking
          html/accountoverview.jsp:>
          ####<22.11.2001 14:10:36 CET> <Debug> <HTTP> <ws-vep> <myserver>
          <Application Manager Thread> <> <> <101158> <Exception thrown while loading
          cyberibisng: weblogic.servlet.jsp.JspException: (line 7): Could not parse
          deployment descriptor: java.io.IOException: cannot resolve 'webwork' into a
          valid tag library>
          weblogic.servlet.jsp.JspException: (line 7): Could not parse deployment
          descriptor: java.io.IOException: cannot resolve 'webwork' into a valid tag
          library
          </snip>
          and it happens because of this taglib definition:
          <%@ taglib uri="webwork" prefix="webwork" %>
          why is this happening and doesn't happen when I don't let it precompile??
          many thanks in advance!
          -paolo

Similar Messages

JSP Precompile - Doesnt Work

Hi All,
          I am having serious trouble trying to precompile my JSP's and have the wl
          server recognise them (and not re-compile them for me). Im using WLS6.1 with
          SP2 installed.
          I am running the JSPC pre-compiler with -D ....WEB-INF\classes. The files
          get created as expected and then I put them into my WAR file. When I deploy
          the WAR file, WLS always recompiles. I have experimented at length with
          different settings in my weblogic.xml, but as yet have had no success. I
          have also read some previous posts, but these have not helped either.
          Any suggestions or advice are very welcome!
          Thanks,
          Mark


          The suggestion to register JSPs as servlets is not at all practical or acceptable
          to me. Across multiple applications, we have over 200 JSP files and there's no way
          I would even consider this approach. What needs to happen is BEA should fix the problem
          and be more forthcoming about such "bugs" instead of letting the customers serve
          as QA and having to "ask" for patches. Why is 6.1 SP3 not on the web site? Why aren't
          all the patches available online for download? For the amount of money BEA charges,
          especially for clustered licenses, this type of problem should not go unfixed.
          Sam Fowler
          "Ashok Madhavan" <[email protected]> wrote:
          >
          >hi,
          >for pre-compiling the jsps in production in .ear format we found a way of
          >doing it.
          >We treated all the jsps in the application as servlets. we precompiled all
          >the jsps
          >before-hand and in the web.xml we gave a servlet-name, sevlet-class etc
          >just as we
          >do for a normal servlet. The compiled classes were in WEB-INF/classes/jsp_servlet.
          >we used hte weblogic.jspc coming along with weblogic. we have weblogic 6.1
          >with SP
          >2.
          >
          >we then did a .war file of this as we do normally.
          >
          >now we deployed this war file and it did work. we didnt include even a single
          >jsp
          >file with our application, just compiled jsps as servlets.
          >
          >The main problem with this is all the jsp need to be pre-compiled and the
          >deployment
          >has to be .war/.ear. this is not suitable for development. for developement
          >there
          >are other easy ways of doing it though.
          >
          >regards
          >Ashok Madhavan
          >
          >"Eric Ma" <[email protected]> wrote:
          >>
          >>Simon:
          >>
          >>Can you do the community a service by posting the patched weblogic.servlet.jsp.Precompiler
          >>class? If it is not convenient to share the Java source file, how about
          >>just the
          >>.class file? I am sure a lot of people will great appreciate the help.
          >>
          >>Eric Ma
          >>
          >>
          >>"Simon Spruzen" <[email protected]> wrote:
          >>>
          >>>There's still a bug in WebLogic's precompile dependency checking in
          >6.1
          >>>SP1 and
          >>>SP2. It will always recompile every JSP in a war file on deployment
          >if
          >>>precompile
          >>>option is true because WebLogic incorrectly generates the mangled JSP
          >servlet
          >>>class
          >>>name. I just patched the appropriate class (weblogic.servlet.jsp.Precompiler)
          >>>and
          >>>all is cool - I precompile my JSPs, put the generated servlet classes
          >into
          >>>the war
          >>>file and deploy it. Much quicker.
          >>>
          >>>I have raised this as a bug with BEA (I sent them my fix too) and they're
          >>>going to
          >>>try and sort this out for SP3. (Judging by postings, this is still a bug
          >>>in 7.0)
          >>>
          >>>simon.
          >>>
          >>>Ryan Barker <[email protected]> wrote:
          >>>>I am having a similar problem. With sp1, the process we would do the
          >following:
          >>>>Unjar the application into exploded format
          >>>>start up the server using the exploded format with precompile turned
          >on
          >>>>copy the /WEB-INF/_tmp_war_..../jsp_servlets directory into the /WEB-INF/classes/jsp_servlets
          >>>>directory
          >>>>rejar up the application
          >>>>start up the server using the war file.
          >>>>
          >>>>Now when we do this process, it recompile all of the jsps into the .wlnotdelete
          >>>>directory.
          >>>>
          >>>>This is seriously annoying. In production we have to have the applications
          >>>>directory as read only due to security policies and jsps need to
          >>>>be pre-compiled. Also on a slightly different note, if the config.xml
          >>>file
          >>>>is set to readonly, weblogic sp1 complained very loudly every 30
          >>>>seconds, have not checked with sp2 yet, hope that this has been fixed.
          >>>>
          >>>>Ryan Barker
          >>>>
          >>>>ludovic le goff wrote:
          >>>>> Hello Mark,
          >>>>>
          >>>>> Please check that in the weblogic.xml file of your web application,
          >>you
          >>>>get
          >>>>> an entry like:
          >>>>>
          >>>>> <context-param>
          >>>>> <param-name>weblogic.jsp.precompile</param-name>
          >>>>> <param-value>true</param-value>
          >>>>> </context-param>
          >>>>>
          >>>>> With the WLS 6.1 SP2, a fix has been done ( 041729 ) and now, the
          >>>>> weblogic.servlet.jsp.Precompiler honors weblogic.xml parameters, like
          >>>>> workingdir, packagePrefix, etc., for the JSPs that it precompiles
          >>>>>
          >>>>> Hope this helps,
          >>>>> Ludovic
          >>>>> Developer Relations Engineer
          >>>>> BEA Support
          >>>>> "newsgroups.bea.com" <[email protected]> a écrit dans le message
          >>news:
          >>>>> [email protected]...
          >>>>>
          >>>>>>Hi All,
          >>>>>>
          >>>>>>I am having serious trouble trying to precompile my JSP's and have
          >the
          >>>>wl
          >>>>>>server recognise them (and not re-compile them for me). Im using WLS6.1
          >>>>>
          >>>>> with
          >>>>>
          >>>>>>SP2 installed.
          >>>>>>
          >>>>>>I am running the JSPC pre-compiler with -D ....WEB-INF\classes. The
          >>files
          >>>>>>get created as expected and then I put them into my WAR file. When
          >I
          >>>>>
          >>>>> deploy
          >>>>>
          >>>>>>the WAR file, WLS always recompiles. I have experimented at length
          >with
          >>>>>>different settings in my weblogic.xml, but as yet have had no success.
          >>>>I
          >>>>>>have also read some previous posts, but these have not helped either.
          >>>>>>
          >>>>>>Any suggestions or advice are very welcome!
          >>>>>>Thanks,
          >>>>>>Mark
          >>>>>>
          >>>>>>
          >>>>>
          >>>>>
          >>>>>
          >>>>
          >>>>
          >>>
          >>
          >

JSP PRECOMPILER IS NOT WORKING WITH WEBLOGIC 6.1 SERVICE PACK 5

          When i compile JSPs using JSP PreCompiler in weblogic 6.1
          ( Service Pack 4 ) , compilation is perfect.
          But when i precompile the same JSPs with weblogic 6.1 (Service Pack 5 )
          , i get compilation error.
          Variable Not Found error comes in service pack 5. But the same code works
          well with service pack 4.
          Could anyone help me ?
          [java] C:\CVSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WE
          NF\classes\jsp_servlet\_secure\__confirmation.java:280: cannot resolve symbol
          [java] symbol : variable yesLinkPageText
          [java] location: class jsp_servlet._secure.__confirmation
          [java] htmllink0.setPage(yesLinkPageText); //[ /secure/co
          rmation.jsp; Line: 32]
          [java] ^
          [java] C:\CVSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WE
          NF\classes\jsp_servlet\_secure\__confirmation.java:378: cannot resolve symbol
          [java] symbol : variable noLinkPageText
          [java] location: class jsp_servlet._secure.__confirmation
          [java] htmllink0.setPage(noLinkPageText); //[ /secure/con
          mation.jsp; Line: 37]
          [java] Error: compilation of jsp file /secure/confirmation.jsp (java file C
          VSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WEB-INF\classes
          p_servlet\_secure\__confirmation.java failed):
          [java] ^
          [java] null
          [java] 2 errors
          [java] Error: [jspc]: 1 file(s) failed:
          [java] /secure/confirmation.jsp
          [java] java.io.IOException: Compiler failed executable.exec(java.lang.String


Can you post the jsp page or a example which doesnt compile in sp5. It seems
          difficult to guage what the problem could be from looking at the error.
          --Nagesh
          "george vargeese" <[email protected]> wrote in message
          news:40c56502$1@mktnews1...
          >
          > When i compile JSPs using JSP PreCompiler in weblogic 6.1
          > ( Service Pack 4 ) , compilation is perfect.
          >
          > But when i precompile the same JSPs with weblogic 6.1 (Service Pack
          5 )
          > , i get compilation error.
          >
          > Variable Not Found error comes in service pack 5. But the same code
          works
          > well with service pack 4.
          >
          > Could anyone help me ?
          >
          >
          > [java]
          C:\CVSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WE
          > NF\classes\jsp_servlet\_secure\__confirmation.java:280: cannot resolve
          symbol
          >
          > [java] symbol : variable yesLinkPageText
          > [java] location: class jsp_servlet._secure.__confirmation
          > [java] htmllink0.setPage(yesLinkPageText); //[
          /secure/co
          > rmation.jsp; Line: 32]
          > [java] ^
          > [java]
          C:\CVSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WE
          > NF\classes\jsp_servlet\_secure\__confirmation.java:378: cannot resolve
          symbol
          >
          > [java] symbol : variable noLinkPageText
          > [java] location: class jsp_servlet._secure.__confirmation
          > [java] htmllink0.setPage(noLinkPageText); //[
          /secure/con
          > mation.jsp; Line: 37]
          > [java] Error: compilation of jsp file /secure/confirmation.jsp (java
          file C
          >
          VSMessageRouter\platform-apps\2notify\webapp\consoleapp\.\web\WEB-INF\classe
          s
          > p_servlet\_secure\__confirmation.java failed):
          > [java] ^
          > [java] null
          > [java] 2 errors
          > [java] Error: [jspc]: 1 file(s) failed:
          > [java] /secure/confirmation.jsp
          > [java] java.io.IOException: Compiler failed
          executable.exec(java.lang.String
          >
          >

Jsp precompile - does it work?

          Part of a weblogic.xml file. Now, it sets the precompile option to true, but if I deploy the app. or touch the redeploy the .jsp arent't precompiled. They are always compiled the first time they load. (And this often gives me a ClassCastException, that why I want to precompile them!!!)
          <.....snip.....>
          <jsp-descriptor>
          <jsp-param>
          <param-name>pageCheckSeconds</param-name>
          <param-value>-1</param-value>
          </jsp-param>
          <jsp-param>
          <param-name>precompile</param-name>
          <param-value>true</param-value>
          </jsp-param>
          <jsp-param>
          <param-name>verbose</param-name>
          <param-value>true</param-value>
          </jsp-param>
          <jsp-param>
          <param-name>keepgenerated</param-name>
          <param-value>true</param-value>
          </jsp-param>
          </jsp-descriptor>
          <.....snip.....>


Hi.
          I have the same problem.
          I am using the default Application and have put the context parameter tag in
          the web.xml file as follows:
          <context-param>
          <param-name>weblogic.jsp.precompile</param-name>
          <param-value>true</param-value>
          </context-param>
          Still no good :( ..... Is BEA listening ???
          -Sandeep
          "Merg" <[email protected]> wrote in message
          news:3a766611$[email protected]..
          >
          > Part of a weblogic.xml file. Now, it sets the precompile option to true,
          but if I deploy the app. or touch the redeploy the .jsp arent't precompiled.
          They are always compiled the first time they load. (And this often gives me
          a ClassCastException, that why I want to precompile them!!!)
          >
          > <.....snip.....>
          > <jsp-descriptor>
          > <jsp-param>
          > <param-name>pageCheckSeconds</param-name>
          > <param-value>-1</param-value>
          > </jsp-param>
          > <jsp-param>
          > <param-name>precompile</param-name>
          > <param-value>true</param-value>
          > </jsp-param>
          > <jsp-param>
          > <param-name>verbose</param-name>
          > <param-value>true</param-value>
          > </jsp-param>
          > <jsp-param>
          > <param-name>keepgenerated</param-name>
          > <param-value>true</param-value>
          > </jsp-param>
          > </jsp-descriptor>
          > <.....snip.....>
          >

Re: [iPlanet-JATO] sp3 jsp compiler problem

Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text
substitution situations, and as a completely independent tool its use is not
restricted to migration situations (or file types for that matter).
Second, I sympathize with the unfortunate trouble you are experiencing due to
Jasper's (perhaps more strict) compilation, but in what way did the iMT
automated translation contribute to these inconsistencies that you cited?
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a
translation situation, the only way "OnClick" would have been introduced was if
it had been part of the pre-existing project's "extraHTML" (which was written
by the original customer and just passed through unchanged by the iMT) or if it
was added manually by the post-migration developer.
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
similar to the OnClick situation described above?
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no
equivalent in the NetDynamics world, so any content tags in your code must have
been introduced by your developers manually. Its a shame that jasper is so
particular, but the iMT could not help you out here even if we wanted to. The
constants that are used by the iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
[Non-text portions of this message have been removed]

Thanks a lot Matt and Mike for your prompt replies.
I agree completely that iMT doesn't introduce the inconsistencies.
About the three cases I mentioned, the third one happens only in
manually created JSPs. So it has nothing to do with iMT. The first
two are mainly due to the existing HTML code, as you rightly pointed
out.
The reason I made the suggestion is since we know that case 1 and 2
won't pass the japser compiler in sp3, we have to do something about
it. The best place to do this, in my mind, is iMT. Of course, there
might be some twists that make it impossible or difficult to do this
kind of case manipulation or attribute discard.
Weiguo
--- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
tool its use is not restricted to migration situations (or file types
for that matter).
>
Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
in what way did the iMT automated translation contribute to these
inconsistencies that you cited?
>
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
introduced was if it had been part of the pre-existing
project's "extraHTML" (which was written by the original customer and
just passed through unchanged by the iMT) or if it was added manually
by the post-migration developer.
>
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
>
>
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
in your code must have been introduced by your developers manually.
Its a shame that jasper is so particular, but the iMT could not help
you out here even if we wanted to. The constants that are used by the
iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
see, the only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
>
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as
what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
>>
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
Service.
>
>
>
[Non-text portions of this message have been removed]

Jsp precompile

          Hi,
          I using weblogic 6.0 sp1 and struts to develop the web application, I deployed
          my web application by war file,I want precompile jsp when weblogic server starts
          up by defining the following context parameter in web.xml deployment descriptor:
          <context-param>
          <param-name>weblogic.jsp.precompile</param-name>
          <param-value>true</param-value>
          </context-param>
          but it failure to pre-compiling JSP's when weblogic server start. I visited
          weblogic newsgroup, and followed the info to try using directory struct to deploy
          (under .\config\mydomain\applications
          or outside of the .\applications directory), both of them had errors. the following
          is my web.xml file and error info. Could you give some idea to fix it?
          Thanks
          Judy
          <?xml version="1.0" encoding="ISO-8859-1"?>
          <!DOCTYPE web-app
          PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
          "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
          <web-app>
          <context-param>
          <param-name>weblogic.jsp.precompile</param-name>
          <param-value>true</param-value>
          </context-param>
          
          <servlet>
          <servlet-name>action</servlet-name>
          <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
          <init-param>
          <param-name>application</param-name>
          <param-value>ApplicationResources</param-value>
          </init-param>
          <init-param>
          <param-name>config</param-name>
          <param-value>/WEB-INF/struts-config.xml</param-value>
          </init-param>
          <init-param>
          <param-name>debug</param-name>
          <param-value>2</param-value>
          </init-param>
          <init-param>
          <param-name>detail</param-name>
          <param-value>2</param-value>
          </init-param>
          <init-param>
          <param-name>validate</param-name>
          <param-value>true</param-value>
          </init-param>
          <load-on-startup>2</load-on-startup>
          </servlet>
          <servlet>
          <servlet-name>InitServlet</servlet-name>
          <servlet-class>ccd.web.misc.InitServlet</servlet-class>
          <load-on-startup>3</load-on-startup>
          </servlet>
          
          <servlet-mapping>
          <servlet-name>action</servlet-name>
          <url-pattern>*.do</url-pattern>
          </servlet-mapping>
          
          <welcome-file-list>
          <welcome-file>index.htm</welcome-file>
          </welcome-file-list>
          
          <taglib>
          <taglib-uri>/WEB-INF/tlds/app.tld</taglib-uri>
          <taglib-location>/WEB-INF/tlds/app.tld</taglib-location>
          </taglib>
          
          <taglib>
          <taglib-uri>/WEB-INF/tlds/struts-bean.tld</taglib-uri>
          <taglib-location>/WEB-INF/tlds/struts-bean.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>/WEB-INF/tlds/struts-html.tld</taglib-uri>
          <taglib-location>/WEB-INF/tlds/struts-html.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>/WEB-INF/tlds/struts-logic.tld</taglib-uri>
          <taglib-location>/WEB-INF/tlds/struts-logic.tld</taglib-location>
          </taglib>
          
          <security-constraint>
          <web-resource-collection>
          <web-resource-name>AdminPages</web-resource-name>
          <description>
          These pages are only accessible by authorised user.
          </description>
          <url-pattern>/misc/ccd.htm</url-pattern>
          <http-method>POST</http-method>
          <http-method>GET</http-method>
          </web-resource-collection>
          <auth-constraint>
          <description>
          These are the roles who have access
          </description>
          <role-name>
          CcdApp
          </role-name>
          </auth-constraint>
          <user-data-constraint>
          <description>
          This is how the user data must be transmitted
          </description>
          <transport-guarantee>NONE</transport-guarantee>
          </user-data-constraint>
          </security-constraint>
          <login-config>
          <auth-method>FORM</auth-method>
               <form-login-config>
               <form-login-page>/misc/login.jsp</form-login-page>
               <form-error-page>/misc/fail_login.jsp</form-error-page>
          </form-login-config>
          </login-config>
          <security-role>
          <description>
          An administrator
          </description>
          <role-name>
          CcdApp
          </role-name>
          </security-role>
          </web-app>
          Error info for war file deployed:
          <May 9, 2001 11:20:23 AM EDT> <Error> <HTTP> <[WebAppServletContext(6040101,ccd)
          ] 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(WebAppS
          ervletContext.java:2003)
          at weblogic.servlet.internal.dd.DescriptorLoader.initFromWebApp(Descript
          orLoader.java:741)
          at weblogic.servlet.internal.dd.DescriptorLoader.createServletContext(De
          scriptorLoader.java:358)
          at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:4
          98)
          at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
          at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
          at weblogic.j2ee.Application.addComponent(Application.java:126)
          at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:283)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:109)
          at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServe
          r.java:76)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          at $Proxy29.addWebDeployment(Unknown Source)
          at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDe
          ployment(WebServerMBean_CachingStub.java:985)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:269)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:109)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
          s(ConfigurationMBeanImpl.java:409)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:287)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMB
          eanImpl.java:866)
          at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMB
          eanImpl.java:853)
          at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.ja
          va:838)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:566)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          at $Proxy12.addTarget(Unknown Source)
          at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(Appli
          cationManager.java:486)
          at weblogic.management.mbeans.custom.ApplicationManager.addApplication(A
          pplicationManager.java:557)
          at weblogic.management.mbeans.custom.ApplicationManager.addApplication(A
          pplicationManager.java:504)
          at weblogic.management.mbeans.custom.ApplicationManager.poll(Application
          Manager.java:428)
          at weblogic.management.mbeans.custom.ApplicationManager.poll(Application
          Manager.java:380)
          at weblogic.management.mbeans.custom.ApplicationManager.update(Applicati
          onManager.java:152)
          at weblogic.management.mbeans.custom.ApplicationManager.startAdminManage
          r(ApplicationManager.java:205)
          at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
          nManager.java:120)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          at $Proxy2.start(Unknown Source)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1034)
          at weblogic.management.Admin.finish(Admin.java:491)
          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)
          >
          <May 9, 2001 11:20:23 AM EDT> <Error> <J2EE> <Error deploying application ccd:
          C
          ould not load ccd>
          <May 9, 2001 11:20:26 AM EDT> <Notice> <WebLogicServer> <WebLogic Server started
          >
          <May 9, 2001 11:20:26 AM EDT> <Notice> <WebLogicServer> <SSLListenThread listeni
          ng on port 7002>
          <May 9, 2001 11:20:26 AM EDT> <Notice> <WebLogicServer> <ListenThread listening
          on port 7001>
          Error info for directory deployed:
          <May 9, 2001 4:50:55 PM EDT> <Error> <HTTP> <[WebAppServletContext(6044546,ccd)]
          failure pre-compiling JSP's
          weblogic.servlet.jsp.JspException: (line 35): Non-matching extension tags
          at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:640)
          at weblogic.servlet.jsp.JspLexer.mCLOSE_EXTENSION_TAG(JspLexer.java:2076
          at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1676)
          at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1552)
          at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:893)
          at weblogic.servlet.jsp.JspParser.doit(JspParser.java:71)
          at weblogic.servlet.jsp.JspParser.parse(JspParser.java:139)
          at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:113)
          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(WebAppS
          ervletContext.java:2003)
          at weblogic.servlet.internal.dd.DescriptorLoader.initFromWebApp(Descript
          orLoader.java:741)
          at weblogic.servlet.internal.dd.DescriptorLoader.createServletContext(De
          scriptorLoader.java:358)
          at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:4
          98)
          at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
          at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
          at weblogic.j2ee.Application.addComponent(Application.java:126)
          at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:283)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:109)
          at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServe
          r.java:76)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          at $Proxy29.addWebDeployment(Unknown Source)
          at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDe
          ployment(WebServerMBean_CachingStub.java:985)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:269)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
          loymentTarget.java:233)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
          ments(DeploymentTarget.java:194)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
          DeploymentTarget.java:158)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          at $Proxy28.updateDeployments(Unknown Source)
          at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
          yments(ServerMBean_CachingStub.java:2299)
          at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
          er(ApplicationManager.java:240)
          at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
          nManager.java:122)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          at $Proxy21.start(Unknown Source)
          at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
          .start(ApplicationManagerMBean_CachingStub.java:435)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1030)
          at weblogic.management.Admin.finish(Admin.java:491)
          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)
          >
          <May 9, 2001 4:50:55 PM EDT> <Error> <J2EE> <Error deploying application ccd:
          Co
          uld not load ccd>
          <May 9, 2001 4:51:03 PM EDT> <Error> <HTTP> <[WebAppServletContext(466450,web)]
          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(WebAppS
          ervletContext.java:2003)
          at weblogic.servlet.internal.dd.DescriptorLoader.initFromWebApp(Descript
          orLoader.java:741)
          at weblogic.servlet.internal.dd.DescriptorLoader.createServletContext(De
          scriptorLoader.java:358)
          at weblogic.servlet.internal.HttpServer.loadWARContext(HttpServer.java:4
          98)
          at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:421)
          at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
          at weblogic.j2ee.Application.addComponent(Application.java:126)
          at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:115)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:283)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:109)
          at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServe
          r.java:76)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          at $Proxy29.addWebDeployment(Unknown Source)
          at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDe
          ployment(WebServerMBean_CachingStub.java:985)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:269)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
          oymentTarget.java:109)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBean
          s(ConfigurationMBeanImpl.java:409)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:287)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMB
          eanImpl.java:866)
          at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMB
          eanImpl.java:853)
          at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.ja
          va:838)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:566)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          at $Proxy12.addTarget(Unknown Source)
          at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(Appli
          cationManager.java:486)
          at weblogic.management.mbeans.custom.ApplicationManager.addApplication(A
          pplicationManager.java:557)
          at weblogic.management.mbeans.custom.ApplicationManager.addApplication(A
          pplicationManager.java:504)
          at weblogic.management.mbeans.custom.ApplicationManager.poll(Application
          Manager.java:428)
          at weblogic.management.mbeans.custom.ApplicationManager.poll(Application
          Manager.java:380)
          at weblogic.management.mbeans.custom.ApplicationManager.update(Applicati
          onManager.java:152)
          at weblogic.management.mbeans.custom.ApplicationManager.startAdminManage
          r(ApplicationManager.java:205)
          at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
          nManager.java:120)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
          eanImpl.java:562)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
          .java:548)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
          ionMBeanImpl.java:285)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          55)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
          23)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:437)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:178)
          at $Proxy2.start(Unknown Source)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1034)
          at weblogic.management.Admin.finish(Admin.java:491)
          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)
          >
          <May 9, 2001 4:51:04 PM EDT> <Error> <J2EE> <Error deploying application web:
          Co
          uld not load web>
          <May 9, 2001 4:51:18 PM EDT> <Notice> <WebLogicServer> <WebLogic Server started>
          <May 9, 2001 4:51:18 PM EDT> <Notice> <WebLogicServer> <SSLListenThread listenin
          g on port 7002>
          <May 9, 2001 4:51:18 PM EDT> <Notice> <WebLogicServer> <ListenThread listening
          o
          n port 7001>


Trying adding this to your weblogic.xml file:
          <jsp-descriptor>
                    <jsp-param>
                    <param-name>precompile</param-name>
                    <param-value>true</param-value>
                    </jsp-param>
               </jsp-descriptor>

Jsp precompilation in weblogic 10.3

I tried precompiling jspx and jsff files using weblogic.jspc.
generated class files are copied to .war/web-inf/classes as i specified this path as destination directory.
when i deploy the .war and try to access page, i get following error
java.lang.IllegalStateException: <f:view> was not present on this page; tag [email protected]b8encountered without an <f:view> being processed.
at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperties(UIXComponentELTag.java:97)
at javax.faces.webapp.UIComponentClassicTagBase.findComponent(UIComponentClassicTagBase.java:613)
at javax.faces.webapp.UIComponentClassicTagBase.doStartTag(UIComponentClassicTagBase.java:1142)
at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.doStartTag(UIXComponentELTag.java:72)
at oracle.adfinternal.view.faces.taglib.region.IncludeTag.doStartTag(IncludeTag.java:179)
at oracle.adfinternal.view.faces.taglib.region.DynamicIncludeTag.doStartTag(DynamicIncludeTag.java:109)
at jsp_servlet._components.__domainpage_jspx._jspService(__domainpage_jspx.java:137)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
After precompiling, do i need to do any config step.
Kindly suggest list of steps to precompile Jsp in .war using weblogic.jspc

From the previous posts, I am assume that the desire is to have jsps precompile during the build process not when the app is deployed to the server. We build ours with Maven and have a command line call to invoke appc. [Jspc should not be used since it is depricated. |http://download.oracle.com/docs/cd/E14571_01/web.1111/e13749/utils.htm#ADMRF158]. Here is the [appc documentation|http://download.oracle.com/docs/cd/E14571_01/web.1111/e13706/splitbuild.htm#i1113244] and [more appc documentation|http://download.oracle.com/docs/cd/E14571_01/web.1111/e13719/appc_ejbc.htm#EJBPG1090] . To make appc run manually, you pretty much have to supply every library that your weblogic.xml references to the -library option. You also need enviroment variable set piror to calling. Anyhow this is what our bat file for calling appc looks like.
set BEAWLS_HOME=%1
set WAR=%2
call %BEAWLS_HOME%\wlserver_10.3\server\bin\setWLSEnv.cmd
call java weblogic.appc -verbose -librarydir %BEAWLS_HOME%\wlportal_10.3\portal-admin\lib\j2ee-modules -library %BEAWLS_HOME%\wlserver_10.3\common\deployable-libraries\jsf-1.2.war,%BEAWLS_HOME%\modules\com.bea.content.vcr_10.3.2.0\content-management-faces-web-lib.war -classpath %BEAWLS_HOME%\wlportal_10.3\light-portal\lib\system\netuix_common.jar %WAR%
This is for Oracle Portal 10.3.2. The locations of the war moved around from Portal 10.3.0 to 10.3.2. BEAWLS is our the Oracle\Middleware (bea\home in older installs) folder from our Weblogic Portal install. WAR is the existing war file. I deleted most war libararies, since there are a lot to list making it really long. It takes our war and compiles all the jsps in it and then makes a new war in its place. The war is then packaged into an ear. Building with ant probably take care some of it for you, but this is what it looks like to call the command manually.

JSP Precompiler could not load class

          Has anyone come across this ?
          Thanks,
          MBI
          I am trying to have a generated jsp page load and this uses a generated bean class.
          The precompiler complains about not being able to load the class.
          <May 4, 2004 3:40:11 PM GMT-08:00> <Debug> <HTTP> <BEA-101158> <Exception thrown
          while loading /Testful: weblogic.servlet.jsp.JspException: (line 11): class 'co
          m.foo.test.TestfulJspBean' could not be loaded
          weblogic.servlet.jsp.JspException: (line 11): class 'com.foo.test.TestfulJspBean'
          could not be loaded
          More info
          at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:711)
          at weblogic.servlet.jsp.JspLexer.processBeanTag(JspLexer.java:1379)
          at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(JspLexer.java:3647)
          at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1931)
          at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1824)
          at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1752)
          at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:962)
          at weblogic.servlet.jsp.JspParser.doit(JspParser.java:105)
          at weblogic.servlet.jsp.JspParser.parse(JspParser.java:228)
          at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:120)
          at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:25
          at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:191)
          at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:71)
          at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:82)
          at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebApp
          ontext.java:4916)


          Has anyone come across this ?
          Thanks,
          MBI
          I am trying to have a generated jsp page load and this uses a generated bean class.
          The precompiler complains about not being able to load the class.
          <May 4, 2004 3:40:11 PM GMT-08:00> <Debug> <HTTP> <BEA-101158> <Exception thrown
          while loading /Testful: weblogic.servlet.jsp.JspException: (line 11): class 'co
          m.foo.test.TestfulJspBean' could not be loaded
          weblogic.servlet.jsp.JspException: (line 11): class 'com.foo.test.TestfulJspBean'
          could not be loaded
          More info
          at weblogic.servlet.jsp.JspLexer.jspException(JspLexer.java:711)
          at weblogic.servlet.jsp.JspLexer.processBeanTag(JspLexer.java:1379)
          at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(JspLexer.java:3647)
          at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1931)
          at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1824)
          at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1752)
          at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:962)
          at weblogic.servlet.jsp.JspParser.doit(JspParser.java:105)
          at weblogic.servlet.jsp.JspParser.parse(JspParser.java:228)
          at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:120)
          at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:25
          at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:191)
          at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:71)
          at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:82)
          at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebApp
          ontext.java:4916)

Want to know abt jsp-precompile option

Hi,
if i passed jsp-precompile=true then what will happen?
what situation we have to send that parameter...
what is the exact functionality of jsp-precompile option....
In our application we are having 200 jsp files.
in our application, once the user logs then 7 frames are loaded and a jsp page is called for each frame...
sometime i am getting jasper exception in some frame.... so should i pass this parameter to all jsp's..
Reply please
Thanks
Saravanan

I don't think precompile is an option that you pass to a JSP. It's a container option, and how it's supported depends on the container AFAIk. I don't think it's in the JSP spec, but I could be wrong.
Basically what it does it turns the .jsp files into .java files (and possibly .java into .class files too) at the point where the app is deployed or started or something. This is in contrast to doing the compilation page by page when a given .jsp is requested.
What you gain is smoother first-time loading of the pages at the cost of one-time startup delay.

HELP.....!!!!! Chinese jsp compilation problem.....

Hi,
Could someone please help on the above mentioned?
I'm using JDeveloper 3.2.3 for my program development under Chinese windows platform. I have created a simple JSP page, which contains few static Chinese words and I have included the line
<%@ page contentType="text/html;charset=UTF-8"%>
at the top of the page. When I tried to compile it using encoding "UTF8" (under compiler option), the compiler gave me this error:
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.jsp
Error: (0) sun.io.MalformedInputException.
Btw, when I have removed the line <%@ page contentType="text/html;charset=UTF-8"%> from the page and compile, I've got this error:
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.jsp
Warning: (0) ISO-8859-1 character set may not match project compiler setting.
C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.java
Error: (0) malformed input character in C:\Program Files\Oracle\JDeveloper 3.2.3\myhtml\Chinese_html\ChineseList.java.
I do appreciate your help on this. Thank you.

Here's some info one of the JSP Developers sent me:
1. HELP.....!!!!! Chinese jsp compilation problem.....
The customer is trying to parse a document generated by
Windows's notepad. When saved in UTF-8, the byte
order mark is saved too. We have a know bug that
JSP parser doesn't recognize Byte Order Mark. The
bug is : 1915285.
2. CHINESE CHARACTER ON JSP
. SQLPLUS depends on NLS_LANG setting. If you
check the windows registry, the default of NLS_LANG
depends on the OS. The user environment is Traditional
Chinese, so does NLS_LANG. If we set NLS_LANG
to .UTF8, SQLPLUS dumps the data in UTF8, however,
the command prompt will have problem displaying them.
. For JSP, as mentioned in a previous mail:
<%@ page contentType="text/html;charset=UTF-8" %> for all languages
<%@ page contentType="text/html;charset=GB2312" %> for simplified Chinese
<%@ page contentType="text/html;charset=Big5" %> for traditional Chinese
. When you enter Chinese characters on a browser,
the data is automatically converted to page encoding
(UTF-8 in your case) before sent back to the server.
But your receiving servlet/JSP needs to have request
encoding set correctly.
    I'm not sure about the JDeveloper environment,
but here is a simple JSP you may try to verify your
OC4J environment:
a.    To set up the schema:
connect scott/tiger
create table tab01(col varchar2(100));
b. Edit the connect string in nls.jsp
c. Run the nls.jsp in oc4j instance.

<%@ page contentType="text/html; charset=UTF-8" %>
<%@ page import="oracle.jdbc.*,java.sql.*,java.io.*"%>
<HTML>
<HEAD>
<TITLE>Hello</TITLE></HEAD>
<BODY>
<%
request.setCharacterEncoding("UTF-8");
String sampledata="\u7D20";
String paramValue = request.getParameter("myparam");
String connStr = "jdbc:oracle:thin:@dlsun478:5521:j2ee01";
String user = "scott";
String passwd = "tiger";
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection(connStr, user, passwd);
if (paramValue == null || paramValue.length() == 0) { %>
   <FORM METHOD="GET">
   Please input your name: <INPUT TYPE="TEXT" NAME="myparam"
value="<%=sampledata%>" size=20>
<BR>
   <INPUT TYPE="SUBMIT" value="Insert Data">
   </FORM>
<%
selectData(conn, out);
else
%>
   <H1> Insert Data: <%= paramValue %> </H1>
   <br/>
<%
insertData(conn, paramValue);
%>
<a href="nls.jsp">back</a>
<%
%>
</BODY>
</HTML>
<%!
public void insertData(Connection aConn, String myval)
    try {
      PreparedStatement stmt = aConn.prepareStatement("insert into tab01
values(?)");
      stmt.setString(1, myval);
      stmt.executeUpdate();
      aConn.close();
    catch (SQLException e) {
      e.printStackTrace();
public void selectData (Connection aConn, JspWriter out)
    try {
      Statement stmt = aConn.createStatement( );
      ResultSet r = stmt.executeQuery("SELECT col FROM tab01");
      out.println("<H1>List of Data:</H1>");
      while (r.next()) {
        out.println(r.getString(1)+"<br/>");
      aConn.close();
    catch (SQLException e) {
      e.printStackTrace();
    catch (IOException e) {
      e.printStackTrace();
%>

Precompiled JSP Compatibility Problem

I am a developer in the Cross Applications Unlimited group. We are experiencing a problem with precompiled jsps in a ADF web application that we have developed. Any help that you can provide with this problem would be much appreciated. Neither Oracle forums nor the internet have yielded any leads to us so far. Here are the specifics of our problem.
In our application, we precompile our JSPs when the EAR is built. The application was initially developed in JDeveloper 10.1.3.2 and worked without problems when deployed to OAS 10.1.3.2. However, our application server MTR recently shifted to OAS 10.1.3.3. We migrated our workspace and projects to JDeveloper 10.1.3.3 and rebuilt our EAR file in JDeveloper 10.1.3.3. We are getting "500 Internal Server Errors" when this new ear file is deployed to OAS 10.1.3.3. The error does not always manifest when running the application. We can login and navigate to JSPs linked directly from our navigation menu (our first level pages). However, in these first level pages are buttons that navigate to second level pages. The error is being seen whenever we try to access one of these second level pages. Everything else about the application works fine. When we don't precompile our JSPs and deploy, the application works fine.
This is the error we find reported in our application logs...
EWCoreViewController: Servlet error
javax.faces.el.PropertyNotFoundException: Error testing property 'inputValue' in bean of type null
at com.sun.faces.el.PropertyResolverImpl.isReadOnly(PropertyResolverImpl.java:274)
at oracle.adfinternal.view.faces.model.FacesPropertyResolver.isReadOnly(FacesPropertyResolver.java:124)
at com.sun.faces.el.impl.ArraySuffix.isReadOnly(ArraySuffix.java:236)
at com.sun.faces.el.impl.ComplexValue.isReadOnly(ComplexValue.java:209)
at com.sun.faces.el.ValueBindingImpl.isReadOnly(ValueBindingImpl.java:266)
Enabling enhanced java logging yields these logs...
<record>
<date>2008-04-09T11:27:25</date>
<millis>1207762045495</millis>
<sequence>258943</sequence>
<logger>com.sun.faces.application.ViewHandlerImpl</logger>
<level>FINE</level>
<class>com.sun.faces.application.ViewHandlerImpl</class>
<method>renderView</method>
<thread>14</thread>
<message>Found no URL patterns mapping to FacesServlet </message>
</record>
<record>
<date>2008-04-09T11:27:25</date>
<millis>1207762045495</millis>
<sequence>258944</sequence>
<logger>com.sun.faces.taglib.jsf_core.ViewTag</logger>
<level>FINE</level>
<class>com.sun.faces.taglib.jsf_core.ViewTag</class>
<method>doStartTag</method>
<thread>14</thread>
<message>Can't leverage base class</message>
<exception>
<message>java.lang.IllegalStateException</message>
<frame>
<class>com.sun.faces.taglib.jsf_core.ViewTag</class>
<method>getComponentType</method>
<line>253</line>
</frame>
Any information anyone can provide would be greatly appreciated.
Thanks

Hi Ian,
Add this jar file to classpath...use either web interface or directly edit jvm12.conf to modify classpath..
Raj

Error while deploying war file with jsp precompile option in weblogic 7.0

          Hi
          I am trying to precompile jsp file which is there in a war.Main jsp file code
          includes one more jsp which is there in other folder under defaultweb directory.
          While deploying the war i am getting the following error.Can any bosy help me
          in this regard
          <Nov 23, 2002 5:01:28 PM IST> <Error> <HTTP> <101045> <[ServletContext(id=464413
          3,name=ArkinTestWeb,context-path=/ArkinTestWeb-3)] translation of /Admin/account
          _access.jsp failed: weblogic.utils.ParsingException: nested TokenStreamException
          : antlr.TokenStreamException: Could not include ./../includes/sessionStatusPage.
          jsp>
          <Nov 23, 2002 5:01:28 PM IST> <Error> <Deployer> <149201> <The Slave Deployer
          fa
          iled to complete the deployment task with id 1 for the application ArkinTestWeb.
          weblogic.management.ApplicationException: Prepare failed. Task Id = 5
          Module Name: ArkinTestWeb, Error: Could not load ArkinTestWeb: weblogic.utils.Ne
          stedException: ArkinTestWeb:ArkinTestWeb Failure while Precompiling JSPs: weblog
          ic.utils.ParsingException: nested TokenStreamException: antlr.TokenStreamExcepti
          on: Could not include ./../includes/sessionStatusPage.jsp - with nested exceptio
          n:
          [weblogic.utils.ParsingException: nested TokenStreamException: antlr.TokenStream
          Exception: Could not include ./../includes/sessionStatusPage.jsp]
          at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
          er.java:657)
          at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
          er.java:548)
          at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Sla
          veDeployer.java:1026)
          at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDep
          loyer.java:700)
          at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHan
          dler.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          >
          Regards
          Anand Mohan


Hi,
1] Remove following from server.xml
<Context path="/SEA" docBase="SEA" debug="0"/>
2] Paste SEA.WAR (test WAR file) into /webapps of TOMCAT
3] Start Tomcat Server - This will create SEA folder under webapps
4] Stop server.
5] Add following to server.xml
<Context path="/SEA" docBase="SEA" debug="0"/>
6] Start Tomcat Server
7] Access the URL.
This will work. Somehow Tomcat does not extract war file contents which are mentioned in server.xml.
I have Apache Tomcat 4.0.3 and faced this problem. The above solution works for it.
Regards,
Sandesh
hi.
I have put my SEA.WAR (test WAR file) into /webapps of
TOMCAT.
I checked the server.xml and put:
     <Context path="/SEA" docBase="SEA" debug="0"/>
I restarted TOMCAT and tried to execute the file:
     http://localhost:8080/SEA/index.jsp
But I got error message:
Apache Tomcat/4.0.3 - HTTP Status 404 -
/SEA/index.jsp
What was happenning?
Anyone can help me?
Thank you.

JSP precompilation ClassNotFoundException

Hi,
I am facing a weird problem. I am using maven2.2.1(ant plugin) to build my portal project. Using Weblogic 10.3. Requirement is to precompile jsps duing build. I added an ant task to precompile jsps which uses weblogic jspc compiler. It generates .class files for all the jsps and includes it in WEB-INF/classes folder. I removed all the jsps from EAR. When I deploy the EAR file. I get the following Error.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "jsp_servlet._myProfile.__AdditionalBillingAccountInfo" failed to preload on startup in Web application: "MyEnergyUserProfileWeb".
javax.servlet.ServletException: [HTTP:101249][weblogic.servlet.internal.WebAppServletContext@864cfc - appName: 'MyEnergyUserProfileEar-1', name: 'MyEnergyUserProfileWeb', context-path: '/MyEnergyUserProfileWeb', spec-version: '2.5']: Servlet class jsp_servlet._my
Profile.__AdditionalBillingAccountInfo for servlet jsp_servlet._com._myProfile.__AdditionalBillingAccountInfo could not be loaded because the requested class was not found in the classpath .
The above is just an example. there are many "classnotfound" exceptions. I double checked it, the .class files were inside wlcls_gen.jar, which was inside classpath. I have the mapping done in web.xml(jspc compiler doesnt update web.xml with mappings). Below is the mapping in web.xml
<servlet>
          <servlet-name>jsp_servlet._myProfile.__AdditionalBillingAccountInfo</servlet-name>
          <servlet-class>jsp_servlet._myProfile.__AdditionalBillingAccountInfo</servlet-class>
     <servlet>
<servlet-mapping>
          <servlet-name>jsp_servlet._myProfile.__AdditionalBillingAccountInfo</servlet-name>
          <url-pattern>/myProfile/AdditionalBillingAccountInfo.jsp</url-pattern>
     </servlet-mapping>
I tried to deploy the EAR which is not precompiled at built time, but instead included <jspdescriptor><precompile> to true, so that it generates class files before deploying. I tried comparing the class files generated at deploy time and build time. There is a difference in classnames. The deploy time generated class files have their name with all characters in lower case like below:
jsp_servlet._com._myProfile.__additionalbillingaccountinfo. Is this the problem? How do i solve it? I dont know if jspc compiler has the option of generating .class files with lower case names.
any advice?
--Ram

Got it... The thing was I included the "CaseSensitive" property to true while compiling the JSPs. It was necessary for previous versions of weblogic(8.1 and previous). By default Weblogic jspc compiles the JSPs and saves the generated class files renaming them to lower case letters. It also replaces special characters to asciinumber . Even the package name is changed if it has Upper case letter or special characters. Mapping in web.xml should be done accordingly.
Thanks,

JSP Precompilation

          I have an interesting issue when deploying an EAR file, Weblogic appears to want
          to recompile JSP's at first request even though I have included compiled JSP code
          in the EAR and have added a couple of suggested parameters to the Weblogic.xml
          file (precompile=false, pageCheckSeconds=-1).
          The JSP's themselves are included in a WAR file under what appears to be a valid
          location :
          WEB-INF/classes/jsp_servlet/__simple1.class (simple1.jsp being the page in question)
          The WAR and subsequent EAR are created from a set of Ant build files and the JSP's
          are compiled using weblogic.jspc. I have seen a solution to this whereby you include
          a custom servlet (weblogic.servlet.JSPClassServlet) in the web.xml file and map
          any *.jsp requests to it. This appears to work although may have other implications
          in terms the app I am trying to deploy.
          I have been able to deploy a Struts demo WAR and achieve the desired results so
          am thinking it could be something to do with how our build creates it's WAR file
          but everything appears to be OK at first glance.
          That being the case - is there anything obvious from these limited details that
          I need to consider that will get WL to use the compiled code ?
          Thx in advance


Ilya,
If you haven't already seen it, perhaps this OJSPC Compilation problem may help.
Good Luck,
Avi.

JSP precompilation through Ant on Weblogic 8.1problem

Hi,
I updated the build.xml script such that it precompiles all JSPs. The environment is Ant and the server is weblogic 8.1. The Jsp classes get generated, but then all of a sudden at the end of compilation, during the resolving phase, I get the errors - cannot resolve symbol.
Here is one example:
..... au_head.java:122 cannot resolve symbol
symbol: class Reference
location: jsp_servlet._jsp._common._au_head
Reference provinceList = selfserve.getProvniceList(); //[ /jsp/common/au_head.jsp; Line 4]
The au_head.jsp file is imported in addressupdate.jsp file. Here is the snap of addressupdate.jsp.
<%@ page import="com.xertex.selfserve.application.AddressUpdateManager" %>
<%@ page import="com.xertex.api.account.Address" %>
<%@ page import="com.xertex.api.reference.Reference" %>
<%@ page import="com.xertex.api.reference.UnitType" %>
<%@ page import="com.xertex.api.reference.Country" %>
<%@ include file="../common/au_head.jsp" %>
As you can see all the imports that au_head.jsp needs are specified in addressupdate.jsp. According to my understanding, the reason why au_head.java complains is because its imports are specified in another JSP java file. My question is how can au_head.java knows from which classes its references come from WITHOUT putting the import statements in au_head.jsp. At runtime, this gets resolved by weblogic server withouth problems. But during compilation time, I can't get it to work. Here is my snapshot of my code that I use for precompiling:
<taskdef name="wlappc" classname="weblogic.ant.taskdefs.j2ee.Appc" classpath="${wl.home}/server/lib/weblogic.jar"/>
<target name="jspcompile" depends="init">
<wlappc deprecation="true" source="${build.dir}">
<patternset refid="sources.jsp.path"/>
<classpath>
<path refid="classes.path.compile" />
</classpath>
</wlappc>
</target>
The sources.jsp.path reference is the location of all jsp files in no particular order. The classes.path.compile reference is the location of all classes that jsps use in no particular order. Please Help. I really need this for my work.
Regards,
Vlad

You may need to add the location of the unresolved reference to the classpath IN THE ANT SCRIPT.
just a guess

Jsp precompile problem

Similar Messages

Maybe you are looking for