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.
If I understand the task correctly, you want to be able to access data stored in a database via a Web client.
You've worked out that it probably means JSPs or JSP/Struts.
Both are excellent choices for thin Web clients, especially if the application is simply to access/update information stored in a database.
I'd image there's lots of business applications that require that and not much else.
I'd like to recommend the following:
-you'll be better off with a three tier rather than two tier application. I think you should have a data access tier based on Data Access Objects as your middle tier. DAOs are a core J2EE design pattern so you won't be doing anything unusual or unsustainable for long term maintenance even if another developer takes over later
-either Struts or plain JSPs are fine really. So go with your whatever skill level you can handle.
-you could try generating the entire application using a tool such as FireStorm/DAO. It can import you existing database schema and generate both a persistence tier (based on JDBC DAOs, EJB CMP, JDO, or Hibernate - I suggest using JDBC DAOs in this case) and can also generate your presentation tier (either Struts or plain JSPs - I suggest using plain JSPs in this case).
A simple application like this should really have a simple architecture. You should be able to download a tool like FireStorm/DAO and generate a working application in less than 30 minutes.