To be very clear, the Struts 1 plugin lets you run Struts 1 *Actions*, but doesn't do anything about the configuration, pages, and custom tags (where lies the dicey work).
Moving from Struts 1 to Struts 2 is not difficult, but it's not trvial. I'm sure tools could be developed to automate the process, but no one's written them yet. Eventually, I'm sure some soul with a 500 action Struts application that they simply must migrate will step up and help us out. Of course, in the meantime, you can run both S1 and S2 together in the same application and do new development in Struts 2, bringing the Struts 1 stuff forward on an as-need basis. As to the original question, Struts 2 has a rich taglib, which would probably make it easier to migrate to Struts 2 than to anything else. Of course, the very best idea is to pick a representative part of the application and give it a try. Some applications will be easier to migrate than others, and mileage will vary. As to the implied question, I don't know anyone in the Struts group who would recommend migrating to Struts 2 without an actual and good reason. For more see, * http://struts.apache.org/roadmap/#migrate_s1 -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
