geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Hogstrom (JIRA)" <>
Subject [jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp prevents Daytrader EAR from running on other J2EE servers like WebSphere
Date Thu, 20 Jul 2006 02:11:14 GMT
    [ ] 
Matt Hogstrom commented on DAYTRADER-7:

I'm torn on this one.  The reason we added the pre-compilation was to improve user experience
so they didn't have to wait for the initial page loads to compile which overall is a good
thing.  However, if someone is planning on doing a performance comparison the least amount
of tweaking of ears/wars and such the better as it calls less into question about what has
changed.  It would be nice to simply download and install DT with the least amount of intrusion
(ala messing around with the ear).  

Jeff's suggestion is probably the right way to go strategically but I'm sympathetic to Piyush's

We can simply comment out the pre-compilation step in Maven and let the user "suffer" the
first time on all platforms.  Or, the commercial vendors can simply uncomment the precompilation

A third option is pre-compilation at deploy for G and others.  Anyone have thoughts on that
?  Aaron?

> [Daytrader] Precompiled jsp prevents Daytrader EAR from running on other J2EE servers
like WebSphere
> ----------------------------------------------------------------------------------------------------
>                 Key: DAYTRADER-7
>                 URL:
>             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:
For more information on JIRA, see:


View raw message