@profile of Spring annotations

@profile in spring is similar to the profile in Maven and is configured to change parameters.

For example, in the development environment and production environment using different parameters, you can configure two sets of configuration files, through the @profile to activate the required environment, but maintenance of two sets of profiles than in Maven to maintain a set of configuration files, in the POM through profile to modify the configuration file parameters of the benefits.

There are exceptions, such as I call the Mall interface in development often can not return the data I need, every time I need to mock data, so I wrote a mock argument to invoke the class, in the development environment to use this class, test environment and production environment using the normal pretext to invoke the class, This way, you don't have to manually change the code every time you develop it.

Note: @profile versions that support the method level and class level after 3.2, the 3.1 version only supports the class level.

To the next, say @profile use method.

First, the annotation configuration

 

2. /** Configuring the production environment Call class **/
4. @service ("Productrpc")
6. @profile ("prop")
8. Public class Productrpcimpl implements PRODUCTRPC
10. Public String Productbaseinfo (Long sku) {
12. return Productresource.querybaseinfo (Long SKU);
14. }
16. }
22. /** Configuring the production environment Call class **/
24. @service ("Productrpc")
26. @profile ("Dev")
28. Public class Mockproductrpcimpl implements PRODUCTRPC
30. Public String Productbaseinfo (Long sku) {
32. return "Iphone7";
34. }
36. }
40. /** Call class **/
42. Public class Demo () {
44. @Resource (name="Productrpc")
46. private Productrpc Productrpc;
50. Public Void Demo () {
52. String skuinfo = Productrpc.productbaseinfo (123123L);
54. Logger.info (Skuinfo);
56. }
58. }

This completes the annotation-based profile configuration. The interface is called normally when configured as a production environment, and the mock interface is used when the callback is made for the development environment.

Second, XML configuration

 

2. <!--development Environment--
4. <beans profile="Dev">
6. <Bean id= "beanname" class="Com.pz.demo.ProductRPC"/>
8. </Beans>
12. <!--production Environment--
14. <beans profile="Dev">
16. <Bean id= "beanname" class="Com.pz.demo.MockProductRPC"/>
18. </Beans>

Third, activate profile

Note: When spring determines that the profile is active, it relies on two separate properties: Spring.profiles.active and Spring.profile.default. If the Spring.profiles.actives property is set, its value is used to determine if the profile is active. If the spring.profiles.active attribute is not set, spring will look for the value of Spring.profiles.default. If both spring.profiles.active and Spring.profiles.default are not set. (The red part is not validated successfully in the project, pending testing)

1. Configuring in the context of a servlet (web. xml)

 

1. <context-param>
2. <param-name>spring.profiles.default</param-name>
3. <param-value>dev</param-value>
4. </context-param>

2. Initialization parameters as Dispatcherservlet

 

2. Ervlet>
4. <servlet-name>springmvc</servlet-name>
6. <servlet-class>org.springframework.web.servlet.dispatcherservlet</servlet-class >
8. <init-param>
10. <param-name>contextconfiglocation</param-name>
12. <param-value>classpath:/spring-servlet.xml</param-value>
14. </init-param>
16. <init-param>
18. <param-name>spring.profiles.default</param-name>
20. <param-value>dev</param-value>
22. </init-param>
24. <load-on-startup>1</load-on-startup>
26. </servlet>

3.spring-junit using @activeprofiles for activation

 

1. @RunWith (Springjunit4classrunner. Class)
2. @ContextConfiguration (locations = "/spring-config.xml")
3. @ActiveProfiles ("Dev")
4. Public class Maintest {
5. ...
6. }

4. As a Jndi entry


5. As an environment variable


6. System Properties as a JVM

@profile of Spring annotations