Thanks for your feedback, everyone. I had suspected that version
incompatibilities with some of the byte code and libraries and other utilities
would prove to be the root cause of a lot of the problems.
We’ll keep this in mind as we determine our modernization strategy.
Thanks again,
Steve
--
S
Sorry for the late response.
I tried the same a few years ago but I was never abel to overcame issues
with javassist : version shipped with tapestry 4 was not compatible with
Java 8 and upgrading javasisst not worked too.
Il 06/02/2019 15:50, Numa Schmeder ha scritto:
> Hi Steve,
>
> I have the
Hi Steve,
I have the same problem, you will have a lot of issues. The best would be to
transfer your app to tapestry 5, but you will be loosing all dojo compatibility
and quite a lot of rework.
I am still hesitating on the best process. You will have to port a lot of code
from external librari
No responses? I think you’re right - it will be try it and see.
> On 31 Jan 2019, at 7:57 pm, Steve Shaw wrote:
>
> Good morning,
>
> Short version: is there any information available on running Tapestry 4
> (specifically 4.1.6) with a modern JVM (specifically Java 11, but we’d settle
> for i
Good morning,
Short version: is there any information available on running Tapestry 4
(specifically 4.1.6) with a modern JVM (specifically Java 11, but we’d settle
for information regarding Java 8)?
Longer version: I’m assisting a client with a platform modernization project.
This particular c
