On Wed, Nov 05, 2008 at 11:49:02AM -0500, Susan Liebeskind wrote:
> Igor Vaynberg wrote:
> >i think the best way to migrate an app is to migrate it a
> >page/pageflow at a time. running wicket inside a jsp or jsp inside
> >wicket is always going to have gotchas you will have to work around.
> >
> >
> Agreed, and you just have to live with some quirks/gotchas while you go
> through the migration.
>
> But I'm just looking for a sense of how people start actually using
> Wicket. Do you have any feel for the ratio of new development in Wicket
> vs. migration old apps to Wicket, just based on the traffic you've seen
> go by on the list over the years?
>
> Again, I know this is a non-scientific survey and not something that can
> be really quantified.
>
> Susan
I migrated an application from SpringMVC/Freemarker (no JSP) to Wicket
over a period of several weeks. I basically did it as Igor suggested, a
page[flow] at a time; some URLs went to the old pages, some to the new.
The biggest issue I can recall is with feedback panels. If we raised a
feedback message (e.g. Session.get().info("Record saved.")) then
redirected to a non-Wicket page, the user wouldn't see the message until
they later hit a Wicket page. I'm sure we could have worked something up
to display Wicket feedback messages from non-Wicket pages but we
completed the migration before it became much of an issue.
jk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
