Shulou(Shulou.com)06/03 Report--

This article will explain in detail the example analysis of configuring multiple properties files with wildcards in SpringMVC. The editor thinks it is very practical, so I share it with you for reference. I hope you can get something after reading this article.

SpringMVC configures wildcards for multiple properties files

Configuring and loading properties files in springmvc usually occurs in the

The configuration in the xml file is as follows

If you want to add a new module to the project, and want the new module to be relatively independent from the previous project, you need to add a new properties file, then you need to configure another one in the xml configuration file. For example:

It's too troublesome to do this. Every time you add a properties file, you have to add it to the xml file. You must also set the ignore-unresolvable property to true.

The solution is to use wildcards

The details are as follows:

Unified management of multiple SpringMVC project configurations

Unified configuration ideas from springCloud

Because the company's project is developed in multiple systems, and the system architecture is almost exactly the same, the same configuration file will exist in different systems.

When some of these configurations need to be modified, all the relevant configurations in the system need to be modified in turn.

Purely time-consuming and unskilled manual work

Therefore, we can learn from the unified profile management idea of SpringCloud to manage the configuration files of multiple systems in the company.

1. The first is the properties file

For similar common information such as database connections, it needs to be modified if the database information is changed. For convenience, a default connection configuration is directly placed on the server.

And publish it to server such as IIS, which can be obtained through http request.

Then modify the configuration file that loads the resource file as follows:

Http://192.168.0.32:82/properties/jdbc.properties

PropertyPlaceholderConfigurer supports loading resources in http and file mode by default.

two。 For all types of xml profiles

In addition to web.xml, there are many xml in the project

Like the propertie file, the same configuration file exists in different projects, and you have to change it one by one.

Similarly, publish the xml and modify the IIS settings to make it accessible through the browser

Iis needs to add MIME types properties and xml to text/plain before it can be accessed in the browser

Then you can access it in the browser.

ContextConfigLocation http://192.168.0.32:82/springConfig/applicationContext-resource.xml, http://192.168.0.32:82/springConfig/applicationContext-db.xml, http://192.168.0.32:82/springConfig/applicationContext-redis.xml, http://192.168.0.32:82/springConfig/applicationContext-redission.xml, Http://192.168.0.32:82/springConfig/applicationContext-service.xml, Http://192.168.0.32:82/springConfig/applicationContext-filter.xml spring-mvc mvc org.springframework.web.servlet.DispatcherServlet contextConfigLocation http://192.168.0.32:82/spring-mvc.xml 1

In this way, you can start directly, and you can check the following log information to make sure that the loading is correct.

At first, it was modified like this.

ContextConfigLocation http://192.168.0.32:82/springConfig/applicationContext-*.xml

Same as classpath, but unfortunately, the distribution fee could not be parsed and the file could not be found

Java.io.FileNotFoundException: URL [http://192.168.0.32:82/springConfig/] cannot be resolved to absolute file path because it does not reside in the file system: http://192.168.0.32:82/springConfig/

At org.springframework.util.ResourceUtils.getFile (ResourceUtils.java:215)

At org.springframework.core.io.AbstractFileResolvingResource.getFile (AbstractFileResolvingResource.java:53)

At org.springframework.core.io.UrlResource.getFile (UrlResource.java:213)

At org.springframework.core.io.support.PathMatchingResourcePatternResolver.doFindPathMatchingFileResources (PathMatchingResourcePatternResolver.java:689)

At org.springframework.web.context.support.ServletContextResourcePatternResolver.doFindPathMatchingFileResources (ServletContextResourcePatternResolver.java:92)

At org.springframework.core.io.support.PathMatchingResourcePatternResolver.findPathMatchingResources (PathMatchingResourcePatternResolver.java:478)

At org.springframework.core.io.support.PathMatchingResourcePatternResolver.getResources (PathMatchingResourcePatternResolver.java:293)

Take a closer look at this paragraph in the source code PathMatchingResourcePatternResolver of the source code loading configuration file

@ Override public Resource [] getResources (String locationPattern) throws IOException {Assert.notNull (locationPattern, "Location pattern must not be null") If (locationPattern.startsWith (CLASSPATH_ALL_URL_PREFIX)) {/ / a class path resource (multiple resources for same name possible) if (getPathMatcher () .isPattern (locationPattern.substring (CLASSPATH_ALL_URL_PREFIX.length () {/ / a class path resource pattern return findPathMatchingResources (locationPattern) } else {/ / all class path resources with the given name return findAllClassPathResources (locationPattern.substring (CLASSPATH_ALL_URL_PREFIX.length ();}} else {/ / Generally only look for a pattern after a prefix here, / / and on Tomcat only after the "* /" separator for its "war:" protocol. Int prefixEnd = (locationPattern.startsWith ("war:")? LocationPattern.indexOf ("* /") + 1: locationPattern.indexOf (":") + 1); if (getPathMatcher (). IsPattern (locationPattern.substring (prefixEnd) {/ / a file pattern return findPathMatchingResources (locationPattern) } else {/ / a single resource with the given name return new Resource [] {getResourceLoader () .getResource (locationPattern)};}

The idea is very simple. The configuration parses the directory and the files containing wildcards from the beginning to the end, and then goes to find out which files satisfy the

However, it is a pity that if it is a wildcard path that begins with http, it is not supported for the time being. It supports classpth,jar and other methods.

However, it is gratifying that the file loading method can be overridden for a very simple reason. The http directory knows, and it is very easy to know what files are under the directory (directory browsing with iis enabled). Then after getting all the files, if they match the wildcard, load them.

Although there is a remote service, the remote service is only a default global configuration

In order to facilitate local modification of some parameters for debugging, modify part of the xml address to classpath when needed, but do not submit the code when submitting the code.

If you do need to modify it, you can notify the person with the permission to operate the server to make the global modification.

On "SpringMVC configuration of multiple properties files wildcard example analysis" this article is shared here, I hope the above content can be of some help to you, so that you can learn more knowledge, if you think the article is good, please share it out for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.