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.

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.

Best regards
johan

-------------------------------------------------
- Digital Television?
- Hey, it's only television.
--------------------------------------------------

        Johan Lundberg wrote:
        >
        > I'm trying to develop a JSP application in a Windows 95
environment.
        > This is done with the newly released jswdk-1.0. My problem is that
I
        > get all the error messages from the JSP into Servlet translation,
and
        > the subsequent Servlet compilation, errors in the jswdk server
DOS-window.
        > This window automatically opens upon web server startup and is
        > impossible (for me) to resize. We all make mistakes, but my error
messages
        > disappears out of the non-scrollable server DOS-window. [...]

        I agree compilation error should be reported in a better way (e.g.
as a response
        to the browser), but here's a simple fix for the "no-scrollable
DOS-window"
        for now:

        * In the startserver.bat script, change "start java ..." to just
"java ...".
          This will cause the Java process to execute in the same DOS window
as you
          run the script in instead of popping a new window,
        * Start a new DOS window, adjust the screen buffer size (using the
          Properties->Layout tab) to get a scrollable window (set Height to
a large
          number like 999), cd to the JSWDK bin directory and run
startserver.bat,
          instead of just dubble-clicking the BAT file. This way you can
scroll back
          and see the complete message.

        Hope this helps.
        --
        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

___________________________________________________________________________
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

Reply via email to