Error running the application as WAR in tomcat 9

Hi; I use Spring Boot to develop GraphQL applications. However, when the application is packaged as WAR and deployed to Tomcat 9, it throws illegalstate exception. I have tried the workaround by adding a ServletContextAware bean but it doesn't help on Tomcat 9. I have filed 2 issues in separate

Re: Tomcat webapp undeploy no longer possible (after windows system crash)

Because I‘m running into more trouble with the system I have restored the system once more from the backup (the same backup used before). And this time all things works. Also the tomcat/tomee, the netbeans deployment and so on. Thanks for all inputs and help. Joerg > Am 08.12.2018 um 18:21 sc

Re: Duplicate web fragment

On 09/12/2018 10:21, Stephane Passignat wrote: > Hello, > > I've seen this non compliancy. In TC 7.042 and 7.0.72. How, who can fix this ? Tomcat is open source so in theory anyone can provide a patch to fix a bug. > Servlet 3.0 spec 8.2.2 2b: Duplicate name exception: if, when traversing the >

Sci and web fragment initialization

Hello, I've seen this non compliancy. In TC 7.042 and 7.0.72. How, who can fix this ? The case is related to web-fragment loading and SCI initialization. In Tomcat 7.0.42 and 7.0.72 at least, SCI (with @HandlesTypes annotation) are initialized web-fragments per web-fragments, with the classes

Incomplete list of handle types

Hi I've seen this non compliancy. In TC 7.042 and 7.0.72. How, who can fix this ? @HandlesTypes classes implementations. The mecanism in place only accept classes implementing an the type but doesn't accept classes inheriting from class implementing the @HandlesTypes classes. The (Servlet 3.0 s

Duplicate web fragment

Hello, I've seen this non compliancy. In TC 7.042 and 7.0.72. How, who can fix this ? Servlet 3.0 spec 8.2.2 2b: Duplicate name exception: if, when traversing the web-fragments, multiple members with the same element are encountered, the application must log an informative error message includ

Re: --illegal-access-warn and --illegal-access-deny show different violations

Yes. --illegal-access=warn It doesn't stop the JVM. I misunderstood. But --illegal-access=deny shows the Spring violation first. While 'warn' showed Tomcat's first. So I assumed that 'deny' will first show Tomcat's messages again. Why does 'deny' not show Tomcat's messages first like 'warn' do