Updated documentation to point out that AnnotationConfigWebApplicationContext can accept both fully-qualified class names as well as base packages to the contextConfigLocation init-param.
@ -5832,7 +5832,8 @@ The above assumes that <literal>MyServiceImpl</literal>, <literal>Dependency1</l
@@ -5832,7 +5832,8 @@ The above assumes that <literal>MyServiceImpl</literal>, <literal>Dependency1</l
</context-param>
<!-- Configuration locations must consist of one or more comma- or space-delimited
fully-qualified @Configuration classes -->
fully-qualified @Configuration classes. Fully-qualified packages may also be
specified for component-scanning -->
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>com.acme.AppConfig</param-value>
@ -5847,7 +5848,7 @@ The above assumes that <literal>MyServiceImpl</literal>, <literal>Dependency1</l
@@ -5847,7 +5848,7 @@ The above assumes that <literal>MyServiceImpl</literal>, <literal>Dependency1</l