caching by using the 'Cache-Control: no-store' directive. • An n > 0 value caches the given response for n seconds by using the 'Cache-Control: max-age=n' directive. 1.9.2. Controllers WebFlux Controllers example shows: <#-- for FreeMarker --> <#assign xhtmlCompliant = true> After processing this directive, any elements generated by the Spring macros are now XHTML compliant. In similar fashion, you library descriptor is called spring- form.tld. To use the tags from this library, add the following directive to the top of your JSP page: <%@ taglib prefix="form" uri="http://www.springframework.org/tags/form"

specific packages to scan, you can do so using an explicit @ConfigurationPropertiesScan directive on your @SpringBootApplication-annotated class as shown in the following example: 65 @SpringBootApplication that are used to make sure slicing works as expected. If you are using an explicit @ComponentScan directive on your @SpringBootApplication -annotated class, be aware that those filters will be disabled. public class SampleApplication { ... } Doing so effectively overrides the default component scan directive with the side effect of scanning those two packages regardless of the slice that you chose. For

specific packages to scan, you can do so using an explicit @ConfigurationPropertiesScan directive on your @SpringBootApplication-annotated class as shown in the following example: 65 @SpringBootApplication that are used to make sure slicing works as expected. If you are using an explicit @ComponentScan directive on your @SpringBootApplication -annotated class, be aware that those filters will be disabled. public class SampleApplication { ... } Doing so effectively overrides the default component scan directive with the side effect of scanning those two packages regardless of the slice that you chose. For

specific packages to scan, you can do so using an explicit @ConfigurationPropertiesScan directive on your @SpringBootApplication-annotated class as shown in the following example: @SpringBootApplication that are used to make sure slicing works as expected. If you are using an explicit @ComponentScan directive on your @SpringBootApplication -annotated class, be aware that those filters will be disabled. public class SampleApplication { ... } Doing so effectively overrides the default component scan directive with the side effect of scanning those two packages regardless of the slice that you chose. For

specific packages to scan, you can do so using an explicit @ConfigurationPropertiesScan directive on your @SpringBootApplication-annotated class as shown in the following example: @SpringBootApplication that are used to make sure slicing works as expected. If you are using an explicit @ComponentScan directive on your @SpringBootApplication -annotated class, be aware that those filters will be disabled. public class SampleApplication { ... } Doing so effectively overrides the default component scan directive with the side effect of scanning those two packages regardless of the slice that you chose. For

that are used to make sure slicing works as expected. If you are using an explicit @ComponentScan directive on your @SpringBootApplication-annoted class, be aware that those filters will be disabled. If you }) public class SampleApplication { ... } This effectively overrides the default component scan directive with the side effect of scanning those two packages regardless of the slice that you’ve chosen. a sudden scan components and user configurations of your application. Again, moving the custom directive to a separate class is a good way to fix this issue. Tip If this is not an option for you, you

that are used to make sure slicing works as expected. If you are using an explicit @ComponentScan directive on your @SpringBootApplication-annoted class, be aware that those filters will be disabled. If you }) public class SampleApplication { ... } This effectively overrides the default component scan directive with the side effect of scanning those two packages regardless of the slice that you’ve chosen. a sudden scan components and user configurations of your application. Again, moving the custom directive to a separate class is a good way to fix this issue. Tip If this is not an option for you, you

that are used to make sure slicing works as expected. If you are using an explicit @ComponentScan directive on your @SpringBootApplication-annoted class, be aware that those filters will be disabled. If you }) public class SampleApplication { ... } This effectively overrides the default component scan directive with the side effect of scanning those two packages regardless of the slice that you’ve chosen. a sudden scan components and user configurations of your application. Again, moving the custom directive to a separate class is a good way to fix this issue. Tip If this is not an option for you, you

that are used to make sure slicing works as expected. If you are using an explicit @ComponentScan directive on your @SpringBootApplication-annoted class, be aware that those filters will be disabled. If you }) public class SampleApplication { ... } This effectively overrides the default component scan directive with the side effect of scanning those two packages regardless of the slice that you’ve chosen. a sudden scan components and user configurations of your application. Again, moving the custom directive to a separate class is a good way to fix this issue. Tip If this is not an option for you, you

that are used to make sure slicing works as expected. If you are using an explicit @ComponentScan directive on your @SpringBootApplication-annoted class, be aware that those filters will be disabled. If you }) public class SampleApplication { ... } This effectively overrides the default component scan directive with the side effect of scanning those two packages regardless of the slice that you’ve chosen. a sudden scan components and user configurations of your application. Again, moving the custom directive to a separate class is a good way to fix this issue. Tip If this is not an option for you, you