I'm a newbie. :(
I've taken about 4 Java courses and written some simple apps. As part of a class, I wrote a order purchasing application with JDBC and JSP pages/servlets. The bummer about all this is that there wasn't much info in the class on using eclipse & such and it seems there are more efficient and modern ways of doing this now.
I want to keep learning and since my ski club has a need to streamline it's booking process (currently email), I thought I would see if I could write an application to do this. I think the right way to do this would be to write something that could support a webservices type interface, so I could eventually (maybe I'm getting ahead of myself) write a mobile app as well. I'm getting a bit confused by all the choices out there though as I don't understand well how the different layers fit together and what the best place is to start. So, to summarize:
1) Beginner level Java - would like to continue using it.
2) Want to build a simple hotel booking type app.
3) Would like a webservices (SOAP?) like interface to the front end
4) Open-source tools
FWIW: I'll be doing this on a macbook but could also do a linux VM. I also have my own hosted domain and mysql db I could setup there for testing.
I'd like it if someone could recommend an approach for me. Perhaps some tutorials or an online class that would get me closer to getting started? Pretend you are me. :)
Your plan seems pretty good.
I think this makes sense.
I guess that would be sufficient.
Use Spring ROO. It is good for an entry-level website and it doesn't required in-depth knowledge of all technologies enlisted. As you learn more you can replace components with your own.
I would suggest -
UI - JSP, HTML , CSS
Database - You said you already have MySQL, which should be good for your use case.
Java Framework - Spring framework. This will give you out of the box support for rest service. Using spring will help you adhere to some good design principles without having to know them. As a newbie I would highly recommend to go with spring. I am not a big fan of SOAP. Unless that is imposed as a constraint I would not recommend SOAP.
Reference that could be helpful - http://docs.spring.io/docs/Spring-MVC-step-by-step/