I hate replying to my own posts, but the reason for my 501 error was
surprising...
> Last week, I was busy converting a Java application into a servlet
> which would then load a JSP (ie. a model 2 approach). Everything was
> going fine: I could call the servlet, which would construct a bean &
> then send the bean to a JSP.
>
> Then, I started getting "501 - Not implemented" errors.
In the original application (a piece of middleware), the application
would receive a request from one of its clients. It would then forward
the request to a remote server over a socket. The responses from the
remote server arrive back asynchronously (sp?). Then the app would send
the response back to the original client.
When I converted this application to a servlet, the asynchronous nature
of requests/responses fails completely. If doGet() returns without
writing (or include/forwarding) anything, you *will* get a 501 error.
While I suppose this makes some kind of sense, it is annoying...
- Frank
===========================================================================
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".
