Originally Posted by
fishtoprecords
Do the NetBeans new -> web app thing, let it generate the code, put "hello world" in it, and make that all run.
I have the base jsp page coded, as a simple copy paste of the index page that already works. I have come up with package kitty - so that I will have a package name. I am using TemporaryOrderForm so that I use 'meaningful class names' as a mental note to be sure and not leave this running untested. I have
public class TemporaryOrderForm extends HttpServlet
with the same base html copy pasted into
protected void processRequest(HttpServletRequest request, HttpServletResponse response)
and am looking at doPost(..... wondering whether I should just put what I have already in there as getting this MeanBean is so that I can deploy on Tomcat with a reasonably tested prototype.
I have three states:
1/ ship a base html page
2/ Order processing
3/ Flush the order
This stuff is not all that hard to write, it does take some contemplation and I have a great deal of it prototyped already in doPost() as I have it. A short test run on local would make prototyping more effective. Everything I have up now is in /kitty/ on the public server. Everything that comes in to kitty goes to someplace in this project I now have open in NetBeans.
Server level 3 help rewrote my .htaccess and provided pointers on a /kitty/index.html that would point to /kitty/kitty.html - which is where I have the page right now.
What I have in processRequest is the equivalent of kitty.html
I figured out I need to have a final static Character for " to avoid manually escaping literals.
{ choking on Humble Pie: }
Try really hard to focus on loading and testing my first web application, I am hurting to get a simple app up - maybe I will not have to manually fix 193 lines of html again. This is at least the tenth time to do that, I have to get the server to issue something so that I can subject it to wc3 checker and so on. Sometimes simple sample drive the project in unwanted directions.