Compile failed; see the compiler error output for details.
org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:938)
org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:758)
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:407)
Originally posted by Ben Souther:
Are you using ant to precompile all the jsps up on your production machine?
When doing so, it is a good idea to name files that are to be included with the <%@ include ...%> tag with a ".jspf" extension.
The pre-compiler task will look for all files with a '.jsp' extension and try to compile them. Often files meant for static include do not contain everything needed to compiled and run as standalone JSPs. Changing the extension causes ant to ignore these files except as includes.
I don't see anything wrong with your index.jsp page or the include you've posted but, if the production environment is trying to compile everything before running, any problem in any JSP will keep the app from starting up.
[ July 20, 2007: Message edited by: Ben Souther ]
Originally posted by othman El Moulat:
i changed all include tags with <jsp:include page="url.." flush="true"/>
Well before you change anything, answer my earlier question.
Are you (or your hosting company) using ANT to pre-compile all of the JSPs in the application before or during deployment?
Originally posted by Ben Souther:
Are you pre-compiling your JSPs on the production machine?
Originally posted by Ben Souther:
You still haven't answered that and nobody suggested changing your includes from directives to actions.
If this is production code, you should really stop grabbing at straws and make sure you understand what you are about to do before you do it.
Originally posted by othman El Moulat:
i didn't like your offending way of replying..
Don't get me started about those stupid light bulbs. |