Hi -- I've inherited a wicket site that was first developed four years ago.
It is running on version 1.4 and I've been asked to estimate an upgrade to
a more current version, and I was hoping to get some advice from this list
about gotchas and so on.
I've been working on the site for several month
Hi,
I'd advice you to read the migration guides 1.4->1.5 and 1.5->6.0.
Then start migrating the app and ask here if you have specific problems.
On Sun, Nov 17, 2013 at 11:33 PM, Scott Carpenter wrote:
> Hi -- I've inherited a wicket site that was first developed four years ago.
> It is running
When you use a different version of Wicket, check, if the version is the same
in NetBeans.
Otherwise, it will be get stuck...
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Advice-for-upgrading-from-an-old-version-of-Wicket-tp4662469p4662488.html
Sent from the
Thank you, Martin. I'll do that.
On Mon, Nov 18, 2013 at 2:00 AM, Martin Grigorov wrote:
> Hi,
>
> I'd advice you to read the migration guides 1.4->1.5 and 1.5->6.0.
> Then start migrating the app and ask here if you have specific problems.
>
>
> On Sun, Nov 17, 2013 at 11:33 PM, Scott Carpenter
On another angle, suppose you're looking at also upgrading Hibernate and
other supporting libraries/frameworks. Would you recommend starting with
any particular component?
It seems to me that starting with Wicket might be a good idea, since it
would hopefully be backwards compatible with other lib
Hi,
Most of the time this should not matter.
Wicket doesn't use many dependencies.
In this particular case it may matter because Wicket uses CGLib to generate
proxies for classes (in contrast to interfaces) and Hibernate also uses
bytecode generation (either via CGLib or Javassist) so a problem m
