https://issues.apache.org/bugzilla/show_bug.cgi?id=52853
Bug #: 52853
Summary: @HandlesTypes not resolving classes when added as
repository directory
Product: Tomcat 7
Version: 7.0.26
Platform: Macintosh
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: benjamin.musc...@gmail.com
Classification: Unclassified
I am running an embedded container that loads the web application classes and
external JARS using the method WebappLoader#addRepository(java.lang.String).
One of the external JARs is spring-web with version 3.1. That JAR file provides
the class SpringServletContainerInitializer annotated with @HandlesTypes to
load implementations of WebApplicationInitializer for web apps that don't
provide a web.xml.
In my application I provide an implementation of WebApplicationInitializer.
This is found if I add my compiled class files as JAR file using
WebappLoader#addRepository(java.lang.String) - the web application gets
configured correctly. However, adding the classes directory instead will not
resolve the class. This sounds like some kind of class loading issue to me.
As a side-note the web application is loaded just fine when you provide a
web.xml (Servlet compatibility < 3.0). All classes can be resolved and used.
You can have a look at the source code here:
https://github.com/bmuschko/gradle-tomcat-plugin/blob/master/plugin/src/main/groovy/org/gradle/api/plugins/tomcat/TomcatRun.groovy#L70
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- 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
