Advice for upgrading from an old version of Wicket

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Advice for upgrading from an old version of Wicket

Scott Carpenter
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 months but consider myself a
newcomer to Wicket. That is, I haven't done a deep dive into learning the
framework yet. I've been updating things based on what I find in the
existing code base. So please forgive me my newbieness and let me know what
details would be helpful.

Furthermore, I'm a newcomer to Java web frameworks in general. There is
Spring and Hibernate involved with this thing, which I've also been able to
update based on the existing state of affairs. The backend is an Oracle
database.

Your thoughts and advice would be greatly appreciated.

Thank you!

Scott
Reply | Threaded
Open this post in threaded view
|

Re: Advice for upgrading from an old version of Wicket

Martin Grigorov-4
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 <[hidden email]>wrote:

> 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 months but consider myself a
> newcomer to Wicket. That is, I haven't done a deep dive into learning the
> framework yet. I've been updating things based on what I find in the
> existing code base. So please forgive me my newbieness and let me know what
> details would be helpful.
>
> Furthermore, I'm a newcomer to Java web frameworks in general. There is
> Spring and Hibernate involved with this thing, which I've also been able to
> update based on the existing state of affairs. The backend is an Oracle
> database.
>
> Your thoughts and advice would be greatly appreciated.
>
> Thank you!
>
> Scott
>
Reply | Threaded
Open this post in threaded view
|

Re: Advice for upgrading from an old version of Wicket

MartinoSuperman
CONTENTS DELETED
The author has deleted this message.
Reply | Threaded
Open this post in threaded view
|

Re: Advice for upgrading from an old version of Wicket

Scott Carpenter
In reply to this post by Martin Grigorov-4
Thank you, Martin. I'll do that.


On Mon, Nov 18, 2013 at 2:00 AM, Martin Grigorov <[hidden email]>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 <[hidden email]
> >wrote:
>
> > 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 months but consider myself a
> > newcomer to Wicket. That is, I haven't done a deep dive into learning the
> > framework yet. I've been updating things based on what I find in the
> > existing code base. So please forgive me my newbieness and let me know
> what
> > details would be helpful.
> >
> > Furthermore, I'm a newcomer to Java web frameworks in general. There is
> > Spring and Hibernate involved with this thing, which I've also been able
> to
> > update based on the existing state of affairs. The backend is an Oracle
> > database.
> >
> > Your thoughts and advice would be greatly appreciated.
> >
> > Thank you!
> >
> > Scott
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Advice for upgrading from an old version of Wicket

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 libraries, and have
updates to support newer versions of those supporting libraries?

Thanks,

Scott


On Tue, Nov 19, 2013 at 7:19 AM, Scott Carpenter <[hidden email]>wrote:

> Thank you, Martin. I'll do that.
>
>
> On Mon, Nov 18, 2013 at 2:00 AM, Martin Grigorov <[hidden email]>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 <[hidden email]
>> >wrote:
>>
>> > 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 months but consider myself a
>> > newcomer to Wicket. That is, I haven't done a deep dive into learning
>> the
>> > framework yet. I've been updating things based on what I find in the
>> > existing code base. So please forgive me my newbieness and let me know
>> what
>> > details would be helpful.
>> >
>> > Furthermore, I'm a newcomer to Java web frameworks in general. There is
>> > Spring and Hibernate involved with this thing, which I've also been
>> able to
>> > update based on the existing state of affairs. The backend is an Oracle
>> > database.
>> >
>> > Your thoughts and advice would be greatly appreciated.
>> >
>> > Thank you!
>> >
>> > Scott
>> >
>>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Advice for upgrading from an old version of Wicket

Martin Grigorov-4
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 may arise
if it is CGLib and they need different major versions.


On Wed, Nov 20, 2013 at 4:13 PM, Scott Carpenter <[hidden email]>wrote:

> 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 libraries, and have
> updates to support newer versions of those supporting libraries?
>
> Thanks,
>
> Scott
>
>
> On Tue, Nov 19, 2013 at 7:19 AM, Scott Carpenter <[hidden email]
> >wrote:
>
> > Thank you, Martin. I'll do that.
> >
> >
> > On Mon, Nov 18, 2013 at 2:00 AM, Martin Grigorov <[hidden email]
> >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 <[hidden email]
> >> >wrote:
> >>
> >> > 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 months but consider myself a
> >> > newcomer to Wicket. That is, I haven't done a deep dive into learning
> >> the
> >> > framework yet. I've been updating things based on what I find in the
> >> > existing code base. So please forgive me my newbieness and let me know
> >> what
> >> > details would be helpful.
> >> >
> >> > Furthermore, I'm a newcomer to Java web frameworks in general. There
> is
> >> > Spring and Hibernate involved with this thing, which I've also been
> >> able to
> >> > update based on the existing state of affairs. The backend is an
> Oracle
> >> > database.
> >> >
> >> > Your thoughts and advice would be greatly appreciated.
> >> >
> >> > Thank you!
> >> >
> >> > Scott
> >> >
> >>
> >
> >
>