[ 
http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422192 
] 
            
Scott Nicholls commented on DAYTRADER-7:
----------------------------------------

Another option would be to change the build process to bundle the needed jar 
files into the war.  Of course, this isn't necessary for those app servers that 
come distributed with those libraries -- which is why it wasn't done in this 
case.  You should also be able to modify the app server's classpath to include 
the missing libraries as well.  IMO, this issue does not "prevent it from 
working with any of the other J2EE application servers."  It does make things a 
little less convenient, I'll agree.

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

        

Reply via email to