Как я могу заставить Шиббол бежать с причалом ⇐ Linux

[Anonymous]

Я установил Jetty 12.0.24 вместе с Shibbaleth v5.1.4. У меня есть причал, работающий нормально, но когда я добавляю Shibbaleth idp.xml в/opt/jetty-base/webapps/Я получаю следующий вывод:
java -jar /opt/jetty/start.jar
2025-08-20 10:49:05.528:WARN :oejk.KeystoreGenerator:main: Generating Test Keystore: DO NOT USE IN PRODUCTION!
2025-08-20 10:49:06.148:WARN :oejx.XmlConfiguration:main: Deprecated method public void org.eclipse.jetty.security.HashLoginService.setHotReload(boolean) in file:///opt/jetty-base/etc/jetty-demo-realm.xml
2025-08-20 10:49:06.151:WARN :oe.jetty:main: demo-realm is deployed. DO NOT USE IN PRODUCTION!
2025-08-20 10:49:06.234:INFO :oejs.Server:main: jetty-12.0.24; built: 2025-08-04T23:40:39.846Z; git: 20bd11c3ce5c2393599bf62873e94a3da7207886; jvm 17.0.16+8-LTS
2025-08-20 10:49:06.288:INFO :oejus.SslContextFactory:main: x509=X509@6b7906b3(jetty-test-keystore,h=[localhost],a=[],w=[]) for Server@3a1dd365[provider=null,keyStore=file:///opt/jetty-base/etc/test-keystore.p12,trustStore=null]
2025-08-20 10:49:06.352:INFO :oejdp.ScanningAppProvider:main: Deployment monitor core in [file:///opt/jetty-base/webapps/] at intervals 0s
2025-08-20 10:49:06.369:INFO :oejdp.ScanningAppProvider:main: Deployment monitor ee10 in [file:///opt/jetty-base/webapps/] at intervals 0s
2025-08-20 10:49:06.374:INFO :oejd.DeploymentManager:main: addApp: App@41925502[ee10,null,/opt/jetty-base/webapps/ee10-demo-async-rest.war]
2025-08-20 10:49:06.432:INFO :oejd.DeploymentManager:main: addApp: App@165b8a71[ee10,null,/opt/jetty-base/webapps/ee10-demo-spec.xml]
2025-08-20 10:49:06.459:INFO :oejd.DeploymentManager:main: addApp: App@64712be[ee10,null,/opt/jetty-base/webapps/ee10-demo-jsp.war]
2025-08-20 10:49:06.461:INFO :oejd.DeploymentManager:main: addApp: App@53499d85[ee10,null,/opt/jetty-base/webapps/demo-moved-context.xml]
2025-08-20 10:49:06.467:INFO :oejd.DeploymentManager:main: addApp: App@1eba372c[ee10,null,/opt/jetty-base/webapps/idp.xml]
2025-08-20 10:49:06.469:WARN :oejd.DeploymentManager:main: Unable to reach node goal: started
java.lang.ClassNotFoundException: org.eclipse.jetty.ee9.webapp.WebAppContext
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:592)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
at org.eclipse.jetty.util.Loader.loadClass(Loader.java:58)
at org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:460)
at org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:388)
at org.eclipse.jetty.deploy.providers.ContextProvider.applyXml(ContextProvider.java:523)
at org.eclipse.jetty.deploy.providers.ContextProvider.createContextHandler(ContextProvider.java:448)
at org.eclipse.jetty.deploy.App.getContextHandler(App.java:108)
at org.eclipse.jetty.deploy.bindings.StandardDeployer.processBinding(StandardDeployer.java:33)
at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:183)
at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:522)
at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:162)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.pathAdded(ScanningAppProvider.java:294)
at org.eclipse.jetty.deploy.providers.ContextProvider.pathAdded(ContextProvider.java:635)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.pathAdded(ScanningAppProvider.java:69)
< /code>



/opt/shibboleth-idp/war/idp.war
/idp
false
false
true

< /code>
It looks like the job is failing on this string:
java.lang.ClassNotFoundException: org.eclipse.jetty.ee9.webapp.WebAppContext
< /code>
When I remove the idp.xml file Jetty runs with no issues.

Подробнее здесь: https://stackoverflow.com/questions/797 ... with-jetty