I'm interested in comments on how to convert a site written largely in a scripting language (in this case, PHP) to Java/JSP in an incremental fashion. I'm not certain this is the perfect forum for the question, but I couldn't find a better one.
Given where we are in the development of the site, it's not clear to me that reimplementation of the deployed portion in Java would be immediately worthwhile - and even if it were, the client would not stand for it. So I'm interested in opinions on how we might gradually transition the site to Java related technologies. For example, what would be the issues surrounding putting up new sections of the site in Java, alongside existing PHP sections, and what about reimplementing pages in Java when significant changes are requested? Is an incremental approach to a port like this realistic at all?
Some problematic areas might include - passing a session id and the associated data from one "side" to another - running new software for the Java parts - an existing caching layer
Right. I saw the thread on sharing sessions last week, and that had some useful ideas. It may not be easy, but I think it's doable.
New software, yes. In fact, it turns out the client is on Microsoft IIS, not Apache as I thought ... I don't suppose there is any JSP plugin for IIS? Still, the sysadmin is going ahead with at least installing Tomcat on a BSD server we have so we can play around some.
We don't have any caching other than whatever is implemented automatically by the database and the web server.
I'm more interested in process issues ... the rest of the team doesn't know Java, though some are interested in learning - involve everyone from the start, or allow split into a PHP team and a JSP team? And, can it be done a page at a time, or are bigger chunks more realistic? Has anyone done something like this and can they relate their experiences?