Sorry every day i've been meaning to write this reply… > On my end I intend to drop the need for > "tiles-request-servlet-wildcard". It provides only one short class, > which we can include with our own integration.
Are we not coming back to SpringApplicationContext ? WildcardServletApplicationContext is basically the exact same class as SpringApplicationContext (albeit cleaner by using ResourcePatternResolver instead of ApplicationContext). To me it looks like tiles-request-servlet-wildcard is really just a subset of the spring-tiles integration. And that we can remove tiles-request-servlet-wildcard altogether. If people want spring-io resource loading why don't they just include spring-webmvc? > I'll remove the dependency on tiles-request-servlet-wildcard in > tiles-request 1.1 / tiles 3.1 (actually I'd like to deprecate > tiles-request-servlet-wildcard entirely, we'll have better options in > tiles 3.1 imho). My vote is to: - move WildcardServletApplicationContext into spring-webmvc-tiles3, renaming it SpringApplicationContext - remove tiles-request-servlet-wildcard altogether, promoting instead spring-webmvc If we need to maintain compatibility in the short term tiles-request-servlet-wildcard can remain with a deprecated WildcardServletApplicationContext that just extends SpringApplicationContext. ~mck
