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 Wed, 19 Jul 2006 16:34:14 GMT
    [ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422184 ] 
            
Piyush Agarwal commented on DAYTRADER-7:
----------------------------------------

I agree that Daytrader is in the Geronimo source tree and I am not trying to promote the above
change just so that Daytrader works on WebSphere.  Adding vendor-specific options and features
to the default descriptors will prevent it from working with any of the other J2EE application
servers like websphere, weblogic, oracle etc. Daytrader's focus is to be a performance benchmark
application for all the J2EE application servers and to be that it has be vendor-neutral.
We should be avoiding adding of vendor specific options in it which will go ahead and break
all the other J2EE application servers.

> [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