[AMQ-3005] The spring.schemas file contains an invalid mapping

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.4.1
• Fix Version/s: 5.4.2
• Assignee: Gary Tully
• Reporter: Michael Monette
• Created: 27/Oct/10 15:37
• Updated: 28/Oct/10 13:27
• Resolved: 28/Oct/10 13:27

Description

The spring.schemas file, in META-INF, contains the following mappings:

http\://activemq.org/config/1.0=activemq.xsd
http\://activemq.org/config/1.0/1.0.xsd=activemq.xsd
http\://activemq.apache.org/schema/core=activemq.xsd
http\://activemq.apache.org/schema/core/activemq-core.xsd=activemq.xsd
http\://activemq.apache.org/schema/core/activemq-core-5.0.0.xsd=activemq.xsd
http\://activemq.apache.org/schema/core/activemq-core-5.1.0.xsd=activemq.xsd
http\://activemq.apache.org/schema/core/activemq-core-5.2.0.xsd=activemq.xsd
http\://activemq.apache.org/schema/core/activemq-core-5.3.0.xsd=activemq.xsd
http\://activemq.apache.org/schema/core/activemq-core-${pom.version}.xsd=activemq.xsd

The final mapping contains an unresolved placeholder, ${pom.version}. XML files which use, for example http://activemq.apache.org/schema/core/activemq-core-5.4.1.xsd as a schemaLocation reference will fail to be mapped correctly with the spring.schemas mechanism. This failure is silent on an internet-connected machine which is allowed to resolve the schemaLocation through the http:// url. When the machine is not internet-connected, though, the failure rears its ugly head and smacks down hard on my webapp's startup with a SAXParseException.