Provide annotation based alternative to AbstractAnnotationConfigDispatcherServletInitializer [SPR-10359]

[spring-projects-issues]

Oliver Drotbohm opened SPR-10359 and commented

Most of the WebApplicationInititalizer implementations based on AbstractAnnotationConfigDispatcherServletInitializer look like this:

public class MyWebApplicationInitializer extends AbstractAnnotationConfigDispatcherServletInitializer {

  @Override
  protected Class<?>[] getRootConfigClasses() {
    return new Class<?>[] { ApplicationConfig.class };
  }

  @Override
  protected Class<?>[] getServletConfigClasses() {
    return new Class<?>[] { WebConfig.class };
  }

  @Override
  protected String[] getServletMappings() {
    return new String[] { "/" };
  }
}

It would be cool if this could be boiled down to this:

@InitWebApplication(
  rootConfig = ApplicationConfig.class,
  webConfig = WebConfig.class,
  mapping = "/")
public abstract class MyWebApplicationInitializer implements WebApplicationInitializer { }

Alternatively we could introduce annotations to mark configuration classes directly:

public abstract class MyWebApplicationInitializer implements WebApplicationInitializer {

  @RootContext
  public static class ApplicationConfig { … }

  @WebContext
  public static class WebConfig { … }
}

The latter probably has the issue of ordering as looking up the static classes probably does not return them in a predefined order (in case there are multiple ones defined to get into the @WebContext. Also the servlet mapping definition does not fit into this model nicely. I just thought to document it as a slightly less usable alternative.

---

No further details from SPR-10359

[spring-projects-issues]

Bulk closing outdated, unresolved issues. Please, reopen if still relevant.