Hello, Steve. Before JSP files can be compiled by javac, they have to be translated to Java source files by a JSP compiler. I doubt you really need to compile the JSP yourself as Tomcat will automatically compile JSP files when they are requested by a browser. Move your calendar.jsp into the webapps\ROOT. Then access it as http://localhost:8080/calendar.jsp using your web browser when Tomcat is running.
The only reason why you would want to compile JSP files before they are served is to eliminate the compiler hit when the JSP file is first requested, or to perform some automated tests (by confirming that all of your JSP files are legal). When you are casually building a web application, pre-compiling JSP files unnecessary complicates the process. Sean Dockery [EMAIL PROTECTED] Certified Java Web Component Developer Certified Delphi Programmer SBD Consultants http://www.sbdconsultants.com ----- Original Message ----- From: "Steve Burrus" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, February 08, 2003 23:35 Subject: Need help w. another jsp! > > Hello all, I am having yet more trouble with executing a jsp in the right way! The jsp in question this time is a "calendar.jsp", which as the name of it suggests, displays a calendar. I placed/put it into the right folder, the C:\jakarta-tomcat\webapps\ROOT\WEB-INF\classes, but alas, when I go to compiling it in DOS, all that I seem to get for my efforts is this: > > C:\jakarta-tomcat-4.1.18\webapps\ROOT\WEB-INF\classes>javac calendar.jsp > javac: invalid flag: calendar.jsp > Usage: javac <options> <source files> > where possible options include: > -g Generate all debugging info > -g:none Generate no debugging info > -g:{lines,vars,source} Generate only some debugging info > -nowarn Generate no warnings > -verbose Output messages about what the compiler is doing > -deprecation Output source locations where deprecated APIs are us > ed > -classpath <path> Specify where to find user class files > -sourcepath <path> Specify where to find input source files > -bootclasspath <path> Override location of bootstrap class files > -extdirs <dirs> Override location of installed extensions > -d <directory> Specify where to place generated class files > -encoding <encoding> Specify character encoding used by source files > -source <release> Provide source compatibility with specified release > -target <release> Generate class files for specific VM version > -help Print a synopsis of standard options > > FYI: I had just gotten thru with editing my System applet in the env. variables section for the classpath specifying the lib folder, but that didn't seem to help! Can someone please help me? Thank you > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
