Some random thoughts, all of which could be way wrong :) ...
* ActionForms - What makes an ActionForm different than a SAF2 Action? The validate() method, and the reset() method, primarily. I propose creating a StrutsActionFormAware marker interface... when an Action implements it, reset() and validate() are called by a new Interceptor to emulate what SAF1 does. It would have to deal with the messages, and I'm not sure I have the answer for that :)
* Actions - How about more or less directly migrating Action and renaming it StrutsAction... have the SAF2 default execute() construct appropriate Struts objects (ActionForm, ActionMapping, etc) and call the Struts version of execute().... It should be obvious that a lot of these ideas involve directly porting SAF1 classes over to SAF2, with some changes to make them work with SAF2... I'd imagine this is along the lines of the "compatibility layer" that has been talked about previously.
* HTML tag libraries - unless I'm mistaken, most, if not all of them, should work if an ActionForm is emulated and placed in scope... do any of them use anything else? Perhaps a new Result that takes a SAF2 Action and copies the properties to an ActionForm for the tags to use?
* Struts configuration files - I assume this refers to converting struts-config.xml to xwork.xml? If so, I think this is one place that is rip for a tool. In many regards they are close enough that it won't be a big problem, but some of the more complex constructs might be an issue (things like custom ActionMapping's and plug-ins for instance)
* Plug-ins... does SAF2 have an analogy for the Struts plug-in mechanism? If not, this should be looked at (it doesn't strike me as too tough if it has to be developed).
* Unknown - I'm not seeing the ability to mark an action as mapping to unknown paths like you can in SAF1... am I just missing it? If not, I suggest implementing this since it is a commonly used security guard.
Maybe more later, but my Chinese good just got here :) Frank Don Brown wrote:
As we approach the topic of migration for Struts Action 1 applications to Struts Action 2, I want to find out what we should focus on first. You are able to run both frameworks side-by-side, but for the developers that want to migrate a Struts 1.x application to Action 2, what aspect of a Struts Action 1 application is the most important to support for migration? 1. ActionForms 2. Actions 3. Validator definitions 4. Message resources 5. Struts configuration files 6. HTML tag libraries 7. Other (please explain) Please let us know your thoughts so we can focus on developing tools to make migration as easy as possible. Thanks, Don --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
