JHove2 too aggressive when loading Spring configuration

Issue #66 resolved
Laurent Bihanic created an issue

I tried to integrate JHove2 within an existing application. I encountered a problem due to the aggressive loading of the Spring configuration files from the classpath : one of the frameworks used by the application has a non-Spring configuration file named login-config.xml. The name of this file matches the JHove2 Spring configuration search pattern but its presence causes the loading of the Spring configuration to fail (XML parse error).

Would it be possible to : either limit configuration search to a predefined subset of the classpath (e.g. "{{{jhove2//-config.xml}}}"), * or allow the user to change the SpringConfigInfo classpath search pattern by adding a public static method?

Or both!

Comments (4)

  1. Log in to comment