On 1/10/07, Ted Husted <[EMAIL PROTECTED]> wrote:
* http://struts.apache.org/roadmap/#migrate_s1
Better yet: http://struts.apache.org/roadmap#migrate_s1
-T.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional command
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 pr
We want to migrate because it is just difficult to develop with struts1.
I understand that it is also not great having two MVC-s in one web
application but in long term I believe it is more reasonable to use a better
MVC that struts1.
We don't (cannot) do that in one step thus we need a solution
On 1/10/07, Medhat M. Saleh <[EMAIL PROTECTED]> wrote:
IMHO, major framework upgrades for existing application, in general is
unworthy of the cost, headache, and the gotchas that they never tell you
about. If there are new compelling business-value-producing features in the
upgrade, more than lik
IMHO, major framework upgrades for existing application, in general is
unworthy of the cost, headache, and the gotchas that they never tell you
about. If there are new compelling business-value-producing features in the
upgrade, more than likely you have to redesign the application. That's
another
I don't think it's that trivial. For every struts 1 action, you have to
configure an action entry in the struts.xml. (At least as far as I can tell
based on the plugin documentation at
http://cwiki.apache.org/S2PLUGINS/struts-1-plugin.html) Remember that
struts 1 and struts 2 are completely dif
> From: Zsolt Koppany [mailto:[EMAIL PROTECTED]
> we have a pretty large code in struts-1. What is more complicated
> moving to struts2 or spring mvc?
Moving to Struts2 is trivial since there's a Struts1 plugin that will
let you run it unchanged! :)
Dave
-
7 matches
Mail list logo
