On 21/12/2022 22:37, Tim N wrote:
This was fixed by adding "--add-opens=java.base/java.lang=ALL-UNNAMED". Now
all applications are running, and various other issues have been fixed by
other "--add-opens" arguments. So these and the last couple of issues are
related to Java 17 and not the classloader code above.
Can a Tomcat expert comment on the approach and code to customise the
classpath as per the thread topic - I'll repeat here for clarity:
Add Dependency:
<dependency>
<groupId>org.apache.tomcat</groupId>
<artifactId>tomcat-catalina</artifactId>
<version>${tomcat.version}</version>
</dependency>
This should be unnecessary. The classes in that package should be
included in tomcat-embed-core
Java
<snip/>
The Java code looks good to me. The calls to
SecurityClassLoad.securityClassLoad() and Service.setParentClassLoader()
may be unnecessary but I don't think they'll cause any harm.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
