geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piyush Agarwal (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp prevents Daytrader EAR from running on other J2EE servers like WebSphere
Date Thu, 20 Jul 2006 13:36:14 GMT
    [ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422418 ] 
            
Piyush Agarwal commented on DAYTRADER-7:
----------------------------------------

"We can simply comment out the pre-compilation step in Maven and let the user "suffer" the
first time on all platforms"

Users using the Daytrader application for benchmarking purposes will surely be doing an initial
warmup run to warmup the JVM and load the necessary classes. This will also have the affect
of compiling the JSPs, so that when they do the measurement run they will not be affected
by this change. Its only users who directly use the application as a sample application who
will notice the initial lag due to JSP compilation.

The precompile JSPs at deploy option inside Geronimo would definitely be a cleaner way to
implement precompiled JSPs and avoid vendor-specific code inside Daytrader.

> [Daytrader] Precompiled jsp prevents Daytrader EAR from running on other J2EE servers
like WebSphere
> ----------------------------------------------------------------------------------------------------
>
>                 Key: DAYTRADER-7
>                 URL: http://issues.apache.org/jira/browse/DAYTRADER-7
>             Project: DayTrader
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Piyush Agarwal
>
> In Daytrader1.1 ear file, JspC (Jasper) compiler has been used to precompile the JSPs
and it adds these compiled JSP to servlet mappings in the web.xml file and places the compiled
classes in the ear file. These precompiled JSPs extend and implement JspC specific classes.

> This EAR deploys successfully on WebSphere which doesn't use the JspC compiler for compilation.
But when the precompiled JSPs are requested from the browser it causes application server
to load the precompiled JSP classes which throw exceptions as it cannot find the Jasper specific
classes in the classpath. 
> The only way I have been able to fix this problem is to remove the rules in the pom.xml
which cause the precompilation of the JSPs and places the precompiled JSP to servlet mapping
in the web.xml and then rebuild the EAR file. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message