[
https://issues.jboss.org/browse/AS7-3892?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-3892:
------------------------------
Fix Version/s: 7.1.2.Final
(was: 7.1.1.Final)
This issue is being relocated to 7.1.2 so that 7.1.1 only contains criticals, blockers,
and EAP LA issues (which are probably not yet at the right status, or need an extra triage
pass).
If these issues are completed in a 7.1.1 timeframe please change the fix version. Although
if you forget I will bulk correct.
Integration with SpringServletContainerInitializer incorrect
------------------------------------------------------------
Key: AS7-3892
URL:
https://issues.jboss.org/browse/AS7-3892
Project: Application Server 7
Issue Type: Bug
Components: Server, Web
Affects Versions: 7.0.2.Final, 7.1.0.Final
Reporter: Martin Vanek
Assignee: Jason Greene
Fix For: 7.1.2.Final
Recently I have tried to install simple Spring 3.1 MVC application without web.xml to
jboss 7.0.2. The context failed to load, only message indicating the something is wrong is
from spring:
INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/test]] (MSC
service thread 1-3) No Spring WebApplicationInitializer types detected on classpath.
I have tried to investigate the problem and it seems that problem is in class
org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor. The reason is
that spring uses interface WebApplicationInitializer in @HandlesTypes annotation and the
method processHandlesType of class ServletContainerInitializerDeploymentProcessor scans
only subclasses. I guess Spring guys did not nothing wrong in implementation of the
ServletContainerInitializer so I think it is the problem of JBoss.
@HandlesTypes(WebApplicationInitializer.class)
public class SpringServletContainerInitializer implements ServletContainerInitializer {
....
}
I guess the processHandlesType method has to be changed something like this.
private Set<ClassInfo> processHandlesType(DotName typeName, Class<?> type,
CompositeIndex index) throws DeploymentUnitProcessingException {
Set<ClassInfo> classes = new HashSet<ClassInfo>();
if (type.isAnnotation()) {
.....
} else {
classes.addAll(index.getAllKnownSubclasses(typeName));
classes.addAll(index.getAllKnownImplementors(typeName));
}
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira