upgrade from 3.0.1

[Chris Kujawa <ck...@nhkujawas.com>]

Hello!

I recently started working for a company and am looking into what it will
take to upgrade our web application from Tapestry version 3.0.1 to
something a bit more...modern. I've read a bunch of the upgrade docs (both
older and new) and am wondering...are we better off if we do an
intermediate upgrade to 4.0.x first, then move to 5, or should we just go
straight to 5.x?

IF we go to 5.x, is there any reason to start at 5.1...or should we just go
straight to 5.7? I realize that there's a bunch of 3rd party libraries you
don't know about, but I can handle determining what the need is there. I
just get the feeling that the stop at 4.0.x is a moot point, and that we've
got our work cut out for us.

Thank you in advance for your help!

-Chris

Re: upgrade from 3.0.1

["Thiago H. de Paula Figueiredo" <th...@gmail.com>]

Hello!

I agree with Volker and Cezary. There would be no value to do any upgrade
other than 5.7. I haven't worked with Tapestry 3, but I did with 4 (even a
couple months ago) and I've been working daily with 5.7. Some of the main
concepts do carry over these versions (pages, the 1-1 relationship they
have with templates, components, heavy reliance on IoC for flexibility),
but the implementation is indeed very different. Unless you want to ditch
server-side rendering for client-side one (i.e. just JavaScript making
calls to REST endpoints), Tapestry 5.7 is the way to go.

Please let us know if you have further questions.

On Mon, Jul 26, 2021 at 4:20 PM Cezary Biernacki <ce...@gmail.com>
wrote:

> Hi,
> There is no point upgrading to Tapestry 4.x. Unfortunately Tapestry 3 is
> quite different from Tapestry 4.x, which is quite different from Tapestry
> 5.x. Differences are so significant, that you should consider this to be
> more of a total rewrite in a new framework, rather than upgrades. At this
> point it might be worth evaluating if Tapestry 5 is the right framework for
> your project.
>
> If you decide to go ahead with Tapestry 5, I think there is little reason
> to try any versions older than 5.7 (and certainly no reason older than
> 5.6).
>
> Best regards,
> Cezary
>
>
>
> On Mon, Jul 26, 2021 at 8:00 PM Chris Kujawa <ck...@nhkujawas.com>
> wrote:
>
> > Hello!
> >
> > I recently started working for a company and am looking into what it will
> > take to upgrade our web application from Tapestry version 3.0.1 to
> > something a bit more...modern. I've read a bunch of the upgrade docs
> (both
> > older and new) and am wondering...are we better off if we do an
> > intermediate upgrade to 4.0.x first, then move to 5, or should we just go
> > straight to 5.x?
> >
> > IF we go to 5.x, is there any reason to start at 5.1...or should we just
> go
> > straight to 5.7? I realize that there's a bunch of 3rd party libraries
> you
> > don't know about, but I can handle determining what the need is there. I
> > just get the feeling that the stop at 4.0.x is a moot point, and that
> we've
> > got our work cut out for us.
> >
> > Thank you in advance for your help!
> >
> > -Chris
> >
>


-- 
Thiago

Re: upgrade from 3.0.1

[Cezary Biernacki <ce...@gmail.com>]

Hi,
There is no point upgrading to Tapestry 4.x. Unfortunately Tapestry 3 is
quite different from Tapestry 4.x, which is quite different from Tapestry
5.x. Differences are so significant, that you should consider this to be
more of a total rewrite in a new framework, rather than upgrades. At this
point it might be worth evaluating if Tapestry 5 is the right framework for
your project.

If you decide to go ahead with Tapestry 5, I think there is little reason
to try any versions older than 5.7 (and certainly no reason older than
5.6).

Best regards,
Cezary



On Mon, Jul 26, 2021 at 8:00 PM Chris Kujawa <ck...@nhkujawas.com> wrote:

> Hello!
>
> I recently started working for a company and am looking into what it will
> take to upgrade our web application from Tapestry version 3.0.1 to
> something a bit more...modern. I've read a bunch of the upgrade docs (both
> older and new) and am wondering...are we better off if we do an
> intermediate upgrade to 4.0.x first, then move to 5, or should we just go
> straight to 5.x?
>
> IF we go to 5.x, is there any reason to start at 5.1...or should we just go
> straight to 5.7? I realize that there's a bunch of 3rd party libraries you
> don't know about, but I can handle determining what the need is there. I
> just get the feeling that the stop at 4.0.x is a moot point, and that we've
> got our work cut out for us.
>
> Thank you in advance for your help!
>
> -Chris
>

Re: upgrade from 3.0.1

[Volker Lamp <vo...@gmail.com>]

Hello Chris,

Having started my app with Tapestry 5.0 I don‘t have first hand experience with the previous versions of Tapestry. Telling from the activity on the mailing list, virtually nobody seems to be using Tapestry 3 or 4.

Since you are facing some work related with backward incompatibilities anyway, you may as well just jump to Tapestry 5.7. In my opinion, it is worth the effort: very useful out-of-the-box features, yet flexible and customizable. The docs are not world class but useful, and there is always help on the mailing list if you make an effort to ask a good question.

Cheers,

Volker

> Am 26.07.2021 um 21:00 schrieb Chris Kujawa <ck...@nhkujawas.com>:
> 
> Hello!
> 
> I recently started working for a company and am looking into what it will
> take to upgrade our web application from Tapestry version 3.0.1 to
> something a bit more...modern. I've read a bunch of the upgrade docs (both
> older and new) and am wondering...are we better off if we do an
> intermediate upgrade to 4.0.x first, then move to 5, or should we just go
> straight to 5.x?
> 
> IF we go to 5.x, is there any reason to start at 5.1...or should we just go
> straight to 5.7? I realize that there's a bunch of 3rd party libraries you
> don't know about, but I can handle determining what the need is there. I
> just get the feeling that the stop at 4.0.x is a moot point, and that we've
> got our work cut out for us.
> 
> Thank you in advance for your help!
> 
> -Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org