Still struggling launching my hck app on Win10 & tomcat 9.0.88.It runs (dont
laugh) on: XP/Win7 & tomcat 4.0.4 Linux-gnu & tomcat 6.0.32
Tomcat 9.0.88 displays fine with localhost:8080.
App hck compiles OK (dont laugh) with a script
using:CLASSPATH=.;c:\tomcat4\j2ee.jar;c:\tomcat4\webapps\hck\WEB-INF\classes;c:\tomcat4\lib\
Starting subsequently tomcat4 hiccups with:<<<<<NOTE: Picked up
JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.base/java.util=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED08-Jul-2024 12:00:24.731 INFO
[main] org.apache.catalina.startup.VersionLoggerListener.log Server version
name: Apache Tomcat/9.0.8808-Jul-2024 12:00:24.748 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server built:
Apr 9 2024 13:22:30 UTC08-Jul-2024 12:00:24.748 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server version number:
9.0.88.008-Jul-2024 12:00:24.748 INFO
[main]org.apache.catalina.startup.VersionLoggerListener.log OS Name:Windows
10......08-Jul-2024 12:00:27.313 INFO [main]
org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
application directory [C:\tomcat4\webapps\hck]08-Jul-2024 12:00:30.041 SEVERE
[main] org.apache.catalina.startup.HostConfig.deployDirectory Error deploying
web application directory [C:\tomcat4\webapps\hck]
java.lang.IllegalStateException: Error starting child at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:690)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:659)
atorg.apache.catalina.core.StandardHost.addChild(StandardHost.java:661)at...
... ...>>>>>
Why, oh why does this tomcat not accept what has been compiled withj2ee.jar??
Using the classpath without j2ee.jar:
CLASSPATH=.;c:\tomcat4\webapps\hck\WEB-INF\classes;c:\tomcat4\lib\the
compilation of the hck app fails early
with:<<<<<c:\tomcat4\webapps\hck\WEB-INF\classes\com>javac *.javaZAjax.java:9:
error: cannot find symbolpublic class ZAjax extends HttpServlet {
^ symbol: class HttpServletZAjax.java:12: error: cannot find
symbol public void doGet (HttpServletRequest req, ^
symbol: class HttpServletRequest location: class ZAjax >>>>>
Why, oh why is the servlet infrastructure not found?
BTW tomcat 8 is not available anymore, neither on the backup site ...
dennis de
champeaux--------------------------------------------------------------
Home page: rs6.risingnet.net/~ddccMarketing site: www . OntoOO.comKindle
books: Side Effects: Impacts on the 21st
Century::https://www.amazon.com/-/es/Dennis-Champeaux-ebook/dp/B09MHJ5W48
Even if not
true::https://www.amazon.com/-/es/Dennis-Champeaux-ebook/dp/B09Y4WR9J7 9/11::
They had the Sun in their
Eyeshttps://www.amazon.com/11-They-had-their-Eyes-ebook/dp/B0CMQ2WSK9https://www.amazon.nl/dp/B0CMQ2WSK9
On Tuesday, May 21, 2024 at 08:38:02 AM PDT, Christopher Schultz
<ch...@christopherschultz.net> wrote:
Hello,
On 5/18/24 23:40, DdC wrote:
> Gave up on installing 9.0.88. on Win10.
Why did you give up? ZIP installation is a single command (either via
CMD or UI shell). EXE installer is pretty straightforward, too. There's
also a third-party installer that has a few more features including the
ability to upgrade an existing installation. (I recommend against
upgrading an existing installation specifically, but that's not a
recommendation against that third-party installer.)
Do you mean you gave up trying to get your application running on it?
> Succeeded with 10.1.23 andjdk-18.0.2.1.
Why Java 18? It's been EOL for years at this point. You should use Java
21 these days for anything new.
Did you know that Tomcat 10 is fundamentally different than previous
versions?
> The lib directory has j2ee.jar, which I have used in earliertomcat versions.
What does j2ee.jar contain? That seems so unspecific as to be problematic.
> Compilation of a system was OK apart from some warnings because Java
> has changed since the code was written.
?
> There is a web.xml file in WEB-INF.
Okay...
> Invoking a servlet gives a 500 error with the ominous complaint:
> class su.SUlogin cannot be cast to jakarta.servlet.Servlet
> (su.SUlogin is in unnamed module of loader org.apache.catalina ...
> ) Looks like that my code is quite out of date.Any suggestion for a
> fix?Going back to an earlier tomcat?
Did you read the migration guide for Tomcat 10.1?
I would highly recommend going back to 9.0 for the time being. If you
remove j2ee.jar, does your project compile? If not, what errors do you
get (missing classes, of course, but what major packages are missing)?
j2ee.jar sounds like an uber-jar with "everything we need in it" without
any specificity. You should replace that with modern, separate libraries
that support your application.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
