https://bz.apache.org/bugzilla/show_bug.cgi?id=64021
Bug ID: 64021
Summary: SCI ordering prevents a web application SCI from using
a service bootstrapped by a container-provided SCI
Product: Tomcat 9
Version: 9.0.x
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: awilkin...@pivotal.io
Target Milestone: -----
This issue relates to a Spring Framework issue [1] that describes a problem
where Spring Framework's ServletContainerInitializer is unable to find Tomcat's
WebSocket support as the latter is initialised by Tomcat's WsSci which runs
after any application SCIs.
>From a comment by Mark Thomas on the Spring Framework issue:
> I've been reading through 8.2.4 again and I think there is some room for
> manoeuvre here. The delegation order matters when both the web application
> and the container specify the same SCI. It must be the one from the web
> application that is used. However, when we are looking at different SCIs I
> think there is scope to load the container provided SCIs first. I don't
> think the spec language precludes that. The more I think about it, the
> more that makes sense. If the web app depends on the container services
> (like Spring does) then the container services need to be loaded first. If
> the web app doesn't depend on them the order doesn't matter (so it is OK
> for container services to be first).
> If you open a Tomcat bug on this I should be able to take a look -
> probably in January now.
[1] https://github.com/spring-projects/spring-framework/issues/22131
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
