> -----Original Message----- > From: Denis Avdic [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 10, 2004 11:55 AM > To: Struts Users Mailing List > Subject: Servlet help for a Struts programmer > > > I have an strange request: > > While I am very familiar with Struts (I've worked almost exclusively > in Struts for last 2 years, right after college), I have only basic > knowledge of actual Servlet programming. Now I am faced with a task > of updating and maintaining a pure Servlet application. > > Does anyone know of a resource (or resources) where I can compare > servlet functionality to struts functionality. I know they are > related, but (for example) I miss having a Struts config file, where I > can glance at one file and see all my action mappings. Is there > anyone there in a similar situation? How are you coping?
I would have several suggestions, depending on what kind of legacy stuff you have. If you are adding new functionality, you can get away with doing it in struts... you might have to change the extension mapping from *.do to something else, but it beats trying to do everything the old way. If you are modifying existing code (ie bug fixing, enhancements) then you are looking at trying to keep the exisiting code base, and thats going to require a lot of study as to how the application works. Start in the web.xml file, looking at urls there and what's being generated on the app. Once you get an understanding for how it all works, then you can make changes as you need to. If you have a struts like MVC controller, then again you'll probably have to read the code to figure out how it works. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
