Wow, thanks for all the great information. I am not sure the direction I am
going to take at this point.
Questions:
Does anyone have any idea of how long it will be before Jakarta comes out?
When will there be another implementation of apache that will support Java
server pages? (Not until Jakarta?)
What other versions of JavaServer Pages can I use for free?
Is there a good review/comparison of the JSP servers out there today?
I think I am going to go try the new GNUJSP.
Thanks for all the great response.
Bob Byron
RAD Systems, Inc.
----- Original Message -----
From: Jean-Michel Leon <[EMAIL PROTECTED]>
To: Bob Byron <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, August 23, 1999 10:56 AM
Subject: Re: Apache + JServ + JSWDK + WinNT
Bob Byron wrote:
>
> I am trying to get Java Server Pages to work under Apache. So far I have
> yet to succeed. I would like to hear from you if you have successfully
> gotten Java Server Pages to work under NT.
>
> My configuration is:
> WinNT
> Apache 1.3.6
> Jserv 1.0
> JSWDK-1.0-ea
that's not supposed to be a working combination, because JSP 1.0 wants
jsdk2.1, and jserv does not support jsdk2.1, yet. I've hacked JServ to
work with jsdk2.1 (I'm running the exact same set up you're describing),
and can supply the changes to people who are interested (it's about 30
minutes work, though).
> Everything works fine when I browse except my ".jsp" pages. I do have the
> scratchdir environment variable set up with keepgenerated turned on.
> Strangely, after I attempt to connect to a ".jsp" file, I will see a java
> file created in the scratchdir, however, the file is empty (0 bytes).
>
> So, how do I debug this problem? The logs aren't telling me anything
> beyond:
> (ERROR) ajp11: Servlet Error: Internal Server Error
> (ERROR) an error returned handling request via protocol "ajpv11"
this is the log of mod_jserv (the apache side of JServ) not JServ
itself.
> Is there a way I can get more detail?
first of all, make sure you use a standalone JServ, that you start by
hand in a console window; makes things mush easier to debug, because the
log is right there, in the console.
next, you can try to statically compile your JSP files into .java
This is very helpful, because it can be automated at build time, instead
of having to run your web app to finally see that you have a syntax
error in your java code.
Here is a snipet of the Makefile (for nmake) I'm using
# you need the right CLASSPATH here
JSPFILES = \
foo.jsp \
bar.jsp \
default: jsp
clean: clean_jsp
JSPC = java com.sun.jsp.compiler.Main -keepgenerated
.SUFFIXES: .jsp .class
CLASSFILES = $(JSPFILES:jsp=class)
TMPFILES = $(JSPFILES:.jsp=_jsp_*.java)
jsp: $(CLASSFILES)
clean_jsp:
del $(CLASSFILES) $(TMPFILES)
.jsp.class:
$(JSPC) $<
hope this helps,
jm.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
For JSP FAQ, http://www.esperanto.org.nz/jsp/jspfaq.html
