Johan Lundberg wrote:
>
> Thanks a lot, you saved my week-end. Last week-end was ruined because of
> this problem.
> I have tried so many things to catch all the translation and compilation
> errors but the "error page" that the JSP specification suggests only seems
> to be invoked when runtime errors occurs. During the JSP translation and
> servlet compilation, an error page seems to be useless. I strongly support
> your suggestion that compilation errors should be reported back to the
> user's browser. There should be a parameter, in the server, that could set
> to where the error messages should be stream to. I found a parameter
> "sendErrToClient" in the FAQ-file that comes with the jswdk-1.0 but I never
> understood how to use it. I gave up yesterday nigh, but after your advice
> I'm up and running again. Thanks.
Great, and now I learned something. I have not seen the sendErrToClient
property before (and I have not tested it yet) but based on the description it
sounds like it *should* do what I was suggesting.
> Since you had that good advice on the startserver.bat script, maybe you have
> been able to edit the stopserver.bat script into a script that works? This
> script doesn't work at all (for me that is) in Windows 95.
That's probably more of an OS problem than a script problem. Do you have
Winsock2 installed? The stopserver script uses RMI to talk to the server and
most problems on Windows 95 related to Java and communication seem to be
solved by installing Winsock2.
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
