How to turn off the warning message when re-compiling jsp in embedded OC4J?

Question

Members,
I would like to remove the annoying warning messages whenever we re-compile a jsp file using embedded OC4J.
Steps:
1. create an web project
2. create a test jsp file (say, test.jsp)
3. run the jsp file.
4. on the jsp visual editor, modify the jsp file.
5. go to the browser, reload the page. the following warning messages are displayed:
06/03/03 08:09:13 Warning: directory C:\Projects\TestAgain\UserInterface\public_html\WEB-INF\classes doesn't exist on classpath
06/03/03 08:09:14 C:\Projects\TestAgain\UserInterface\classes\.jsps\_test.java:31: warning #556: variable session assigned to but never used
06/03/03 08:09:14 HttpSession session = pageContext.getSession();
06/03/03 08:09:14 ^
06/03/03 08:09:14 C:\Projects\TestAgain\UserInterface\classes\.jsps\_test.java:32: warning #559: variable __jsp_tag_starteval declared but never used
06/03/03 08:09:14 int __jsp_tag_starteval;
06/03/03 08:09:14 ^
06/03/03 08:09:14 C:\Projects\TestAgain\UserInterface\classes\.jsps\_test.java:33: warning #556: variable application assigned to but never used
06/03/03 08:09:14 ServletContext application = pageContext.getServletContext();
06/03/03 08:09:14 ^
06/03/03 08:09:14 C:\Projects\TestAgain\UserInterface\classes\.jsps\_test.java:35: warning #556: variable page assigned to but never used
06/03/03 08:09:14 _test page = this;
06/03/03 08:09:14 ^
06/03/03 08:09:14 C:\Projects\TestAgain\UserInterface\classes\.jsps\_test.java:36: warning #556: variable config assigned to but never used
06/03/03 08:09:14 ServletConfig config = pageContext.getServletConfig();
06/03/03 08:09:14 ^
06/03/03 08:09:14 C:\Projects\TestAgain\UserInterface\classes\.jsps\_test.java:37: warning #556: variable __ojsp_varRes assigned to but never used
06/03/03 08:09:14 javax.servlet.jsp.el.VariableResolver __ojsp_varRes = (VariableResolver)new OracleVariableResolverImpl(pageContext);
06/03/03 08:09:14
I'm so much glad to see JDeveloper giving out all the details and warnings, but sometimes they spit out too much warning messages that simply annoys and distracts my programming.
There seems to be no parameters for me to shut those up, maybe I should do it manually?
thanks.

Answer 1

Ronald,
I've already tried setting up the j2ee-config.xml file, but
it seems that the warning message does not come from the oc4j, but is generated when jsp file is being compiled, so no matter what you do with the j2ee-config.xml, it would not work to remove the warnings.
I was thinking maybe I could setup the java compiler option found in server.xml, by adding -nowarn option in javac options attribute, but it seems that the file server.xml gets overwritten automatically whenever the oc4j restarts (so, no avail).
So... any other ideas?