I have one web application that's integrated with our internal customer service system and it came time to and upgrade to current supported releases of java, jasper, and tapestry. It didn't take long to discover that moving to Tapestry 5.1 from Tapestry 3.0 required a "whole rewrite" of the application.
Apparently T3 to T4 also required extensive code changes, although the scope is much smaller. So I decided that I wasn't going to go down this road (of rewriting the app every 3 years) and started looking into the myriad of java web frameworks available out there.
To make a long story short, I ended up back at Tapestry. I even considered going way back to Cold Fusion, but that didn't sound like it'd be much fun.
Howard was promising that this would be the last time a rewrite would be required. Backward compatibility was going to be there from version 5 on out. (Of course his use of "t:comp" in his #2 screencast is already obsolete!).
Thinking the whole development process through, it seemed that the way this particular application was put together, very little of the code was actually Tapestry specific. It shouldn't be all that difficult to take this small website, move the html files to templates and flesh out the classes behind them with a lot of the same code. Deciding to take a chance, I've begun the process of migrating.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment