You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Piyush Agarwal (JIRA)" <de...@geronimo.apache.org> on 2006/07/19 02:33:13 UTC
[jira] Created: (DAYTRADER-7) [Daytrader] Precompiled jsp prevents
Daytrader EAR from running on other J2EE servers like WebSphere
[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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Jeff Genender (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422194 ]
Jeff Genender commented on DAYTRADER-7:
---------------------------------------
"Im leaning towards Piyush's view (sorry Jason and Jeff), but on the other hand it's got me thinking whether DayTrader should be part of Geronimo at all. If its goal is to be a platform-independent performance benchmark application why it's part of Apache Geronimo project?"
I agree with you somewhat here, but unfortunately it is very Geronimo centric (codewise/DD) at this point and we would need to decide if this is Geronimo or not. From someone who lead a team to get this working on several platforms, I can honestly say that this is/was no simple task. and we will likely run into issues where things need to be significantly different for each of the application servers.
IMHO, if we strip out much of the server specific code and start using tools like XDoclet and some of the AXIS compiling tools to be a part of the build rather than hard code the stubs and DDs, I think this will be a very viable possibility.
We kind of do support multiple appservers. I believe we have a set of jboss DDs in there.
"On to the main question, why can't we support other application servers? Why do we precompile these JSPs at all? The more servers DayTrader supports the merrier, right?"
Being that this is a performance application, I would think that the more precompiling one can do, the better. However, why can't we make precompiling an option? If we do remove it, we may need a web option to compile the JSPs (Liferay has a really cool precompile option build into the web application itself)...i.e. it can hit all the JSP links behind the scenes...thus using the web server's native compiler. But this will be a bit of a PITA since a server restart will possibly yield a requirement to compile the JSPs once again depending on app server vendor.
Yes we can support multiple application servers, but I think the answer will lie in leveraging XDoclet and other compilers.
> [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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422322 ]
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 request.
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 themselves.
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: 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
[jira] Closed: (DAYTRADER-7) [Daytrader] Precompiled jsp prevents
Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=all ]
Matt Hogstrom closed DAYTRADER-7.
---------------------------------
Fix Version/s: 1.2
Resolution: Fixed
Assignee: Matt Hogstrom
Removed JSPC precompilation from modules/web. After considering the issues I am more concerned with people having to monkey around with the ear which will make performance comparisons more difficult for released versions.
If this issue causes grief for Windows users due to long pathnames I will reverse this change.
Sending modules/web/pom.xml
Transmitting file data .
Committed revision 425415.
> [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
> Assigned To: Matt Hogstrom
> Fix For: 1.2
>
>
> 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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422191 ]
Jacek Laskowski commented on DAYTRADER-7:
-----------------------------------------
I'm leaning towards Piyush's view (sorry Jason and Jeff), but on the other hand it's got me thinking whether DayTrader should be part of Geronimo at all. If its goal is to be a platform-independent performance benchmark application why it's part of Apache Geronimo project?
On to the main question, why can't we support other application servers? Why do we precompile these JSPs at all? The more servers DayTrader supports the merrier, right?
> [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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422011 ]
Jason Dillon commented on DAYTRADER-7:
--------------------------------------
Still not a bug... I don't mind if it is a bit more work to get it running inside of WAS... you should use Geronimo anyways :-P
> [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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Jeff Genender (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422013 ]
Jeff Genender commented on DAYTRADER-7:
---------------------------------------
Agreed...this is not a bug. Daytrader in the Geornimo source tree is not an official part of WAS.
> [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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Piyush Agarwal (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Piyush Agarwal (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422477 ]
Jason Dillon commented on DAYTRADER-7:
--------------------------------------
If this is such a big deal to non-G users, lets just make a new -generic war module that is happier for deployment into non-G systems.
Or, still I don't mind if those users have to some work to get it functional... just document the steps in the wiki and be done with it.
> [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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Paul McMahan (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422494 ]
Jason Dillon commented on DAYTRADER-7:
--------------------------------------
Blah... more windows-specific hacking.
I hope that vista fixes some of these problems...
Anyone know definitively if it will fix this long filename issue or not?
> [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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Piyush Agarwal (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422010 ]
Piyush Agarwal commented on DAYTRADER-7:
----------------------------------------
Just removing the compiled classes from the war doesn't solve the issue as the web.xml still contains the precompiled jsp to class mappings. As long as these mappings exist the server believes that the compiled class-files exist at the speicified path and tries to serve them from that path.
Also to bear in mind is the fact that the path that Jasper uses to place its precompiled JSP classes is Jasper specific.
> [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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/DAYTRADER-7?page=comments#action_12422008 ]
Jason Dillon commented on DAYTRADER-7:
--------------------------------------
I'm not sure this is a bug... if you want to run the app on WAS, then remove the compiled classes from the war.
> [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
[jira] Commented: (DAYTRADER-7) [Daytrader] Precompiled jsp
prevents Daytrader EAR from running on other J2EE servers like WebSphere
Posted by "Scott Nicholls (JIRA)" <de...@geronimo.apache.org>.
[ 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