I've been asked for a rough estimate of the effort to convert a couple of
ASP webs to JSP. The reason for this is to get us into a Java platform so
that future releases of the product can be componentized and put into EJB,
but we do not have the time right now to do a complete rewrite.
I suggested that we start with a straightforward translation of ASP to JSP,
and the addition of a simple data access layer using servlets and/or beans.
Right now the ASP pages are accessing the database via stored procedures,
and the stored procedures themselves are wrapped in ASP functions which hide
all the ADO ugliness. If the ASP in the "front end" pages is translated more
or less in place, and the functions are converted to methods of some data
access layer object, we can avoid doing a major rewrite, correct?
Can anyone give me a good way of estimating the effort to do this, it just
needs to be an order of magnitude estimate at this time. One web has 43
front-end pages, calling 25 "procedure" pages that wrap the stored
procedures (each "procedure" page wraps one stored procedure). The other one
has 64 front end and 68 procedure pages.
Jeff Sahol
[EMAIL PROTECTED]
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
