I am exploring options for how to re-design an application that is a few years old running on java 1.2 with iPlanet 4.1. The entire application is written using JSP (several thousand lines of code in each) and "beans" (again, several thousand lines of code a piece). Right now each bean has much embedded JDBC. A lot of logic is in stored procedures as well (sybase).
My desire is to pilot something using Struts or JSTL. I want to see more passing of objects/interfaces rather than calls to a storedProc that returns just tons of data to be displayed. There are many, many methods (150 in one class) that pass upwards of 15-20 params... yikes.
My constraints are that there is a desire to not use EJBs. Also, the migration from iPlanet 4.1 might take a while, and I need to know what my otions are if I am forced to stay with Java 1.2/iPlanet 4.1. I also have some pushback from people who think this is going to take too long, but I think the gain outweighs this argument and don't thik it will take as long as they think.
So, my question is where to start... is Struts the way to go? JSTL? Something else? How can I make those DB calls more manageable and easier to resue through the app? What are my options since I can't use EJBs? I would like to run this on Tomcat or WLS.
With all that said, if someone could just throw me a bone on where to start, I'd appreciate it. I've got use cases and system requirements down. Some rough interaction diagrams, but need to quickly get something running to show an approach that will foster some confidence by my group.