This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am in the process of writing a "speaking" web browser for in house use. This browser will only access internal web pages. When I attempt to submit a form to a servlet. When the form is submitted it dosen't seem to do anything. There is never a response and I eventually have to kill it. Any suggestions?
Who wrote the servlet? Which servlet engine is being used? Are there any log entries? Error messages on consoles? Can you get other servlets to work on the same server? Bill
Joined: Jun 05, 2001
The servlet was written by another department within the company, so I don't know much about it. The preceeding servlet that is submitted works fine. I was wondering if it was a security issue since the page is of the https type.
you still didn't answer if there are any log messages? error messages in the console? It's pretty impossible to debug something without some kind of hint from the system as to what the problem might be. If you don't see anything, make sure you have the debug level in your appserver set appropriately so you can see all the log messages.
Since it is a company wide web application I don't see the messages from the app server ( and don't think this would likely happen ), just the dos window of my java application. When the page is submitted to the servlet I never get a response back. I know this isn't much information. I was just wondering if there was something in general I should be doing when submitting a page to an https:// servlet. thanks.