I've discovered a bit of strange behavior when doing applet to servlet or
application to servlet communication using URLConnection objects. I have a
Java class which uses a URLConnection object to establish a connection to a
servlet and send it an ArrayList using serialization. In the current
context, the communication between the Java application making the request
and the servlet processing the request is not bi-directional. The
application doesn't expect and doesn't care about a response from the
servlet (doInput is set to false on URLConnection). When I try to run with
the former setup, the service method in my servlet is never called and no
exceptions are generated. Eventually I modified the servlet to send a
response code back to the calling class in the form of an Integer object and
the code worked: the servlet's service method was called and response
returned to the calling class.

My question is, why, when calling a servlet through a URLConnection, must I
set doInput on the URLConnection to true and return a response from the
servlet's service method in order for the servlet container to execute the
servlet's service method. If I neglect to set doInput to true or return a
response, the service method doesn't execute. I tested with the following
configurations with the exact same test results: IIS with JRun, Apache with
JRun, and Apache with Tomcat. Any help appreciated.

Grant

___________________________________________________________________________
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