I understand that it would be nice for you not to have to worry about when/how your JSPs get compiled.
This fn-ality should be a part of Jasper. I only do the Jetty/JBoss integration.
If you really want it, and I am always dealing with traffic on this subject - so many people do, then you should find the Jasper project at jakarta.apache.org and suggest it to them.
Good luck,
Jules
Thorbj�rn Ravn Andersen wrote:
Jules Gosnell wrote:
This step is problematic to perform in an automated manner, due to the need for development time knowledge (which jsps are servlets and which are just included, etc...).
I understand there is a problem detecting this automatically, but would it be hard to implement given a configuration file snippet saying exactly which files to compile? I read the FAQ and found that there is a convoluted code sample which apparently maintains such a snippet (it is not easy to understand without running it). This may be adapted to provide such a list.
My current approach is to use the ?jsp_precompile feature, but that is also hard to automate as it is difficult to estimate when the asynchronic deployment with JBoss is finished so Jetty is ready to serve pages.
I understand that the Trifork J2EE server can do this. Perhaps it is a nice feature to have?
________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
