[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422480 ] Paul McMahan commented on DAYTRADER-7: --------------------------------------
as I recall the JSPs are precompiled and put in a jar file because allowing them to be compiled at runtime ended up generating long pathnames that caused problems on windows. > [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
