[
https://issues.jboss.org/browse/WFLY-9081?page=com.atlassian.jira.plugin....
]
cnsgithub cnsgithub commented on WFLY-9081:
-------------------------------------------
I think something related to this, broke something with WF12 when using Spring. Currently
i can't provide a *.war to test but a class residing in the *.war classes path is no
longer recognized.
import org.springframework.web.WebApplicationInitializer;
public class MyWebApplicationInitializer implements WebApplicationInitializer
[0m[0m09:52:16,244 INFO [io.undertow.servlet] (ServerService Thread Pool -- 51) No
Spring WebApplicationInitializer types detected on classpath
org.springframework.web.SpringServletContainerInitializer
@Override
public void onStartup(@Nullable Set<Class<?>> webAppInitializerClasses,
ServletContext servletContext)
->> WebAppInitializerClasses does not contain the MyWebApplicationInitializer
anymore
Ultimately this call is coming from: WarMetaDataProcessor
I hope this is enough to find the cause of this. The same configuration worked fine with
WF11 Final.
Support ServletContainerInitializer placed on WARs
--------------------------------------------------
Key: WFLY-9081
URL:
https://issues.jboss.org/browse/WFLY-9081
Project: WildFly
Issue Type: Feature Request
Reporter: Guillermo González de Agüero
Assignee: Stuart Douglas
Fix For: 12.0.0.Beta1, 12.0.0.Final
The Servlet spec only talks about the presence of ServletContainerInitializer's
within JAR files bundled on the WAR. It says nothing about what to do when found on the
WAR and Undertow is ignored them right now, which is spec complaint.
However, WildFly has the only Servlet container I'm aware of that ignores that
classes, having tested Payara, WebLogic,WebSphere Liberty, Jetty, Tomcat and Resin.
It would be good to support them on Undertow too.
I've also opened an issue on the Servlet spec repository, so this can be clarified
for future versions of the document:
https://github.com/javaee/servlet-spec/issues/179
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)