Hi,
I replaced JSF 2.2.1 with 2.2.20 and the problem is gone! It seems that the
old 2.2.1 JAR had some kind of old format that crushed with the way the
latest Eclipse works. And since 2.2.1 to 2.2.20 is not a huge upgrade, my
old JSF pages still work. Nice!
Thanks!
On Thu, Oct 12, 2023 at 4:35 P
Hi Chris,
Its JSF version 2.2.1
What is a bytecode scanner? I will google that, I don't have any idea.
And why did I start getting this problem a few days ago? The only thing
that changed is Eclipse (I upgraded it to the latest) and the Tomcat that
Eclipse uses to run the website everytime I run i
Brian,
On 10/12/23 16:55, Brian Braun wrote:
Hello,
First of all, I apologize if maybe my issue is not exclusively related to
Tomcat, but I think it is.
I started my website many years ago, using Struts 1.2.4 and since then I
have been using it. Some years after that I had the intention to mig
Hello,
First of all, I apologize if maybe my issue is not exclusively related to
Tomcat, but I think it is.
I started my website many years ago, using Struts 1.2.4 and since then I
have been using it. Some years after that I had the intention to migrate to
JSF (version 2.2.X) and combine both fra