You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2010/10/28 15:28:00 UTC
[jira] Resolved: (AMQ-3005) The spring.schemas file contains an
invalid mapping
[ https://issues.apache.org/activemq/browse/AMQ-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-3005.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.5.0
updated the file and added a few past and future versions. Added note to the release guide to ensure it is not missed in the future: http://activemq.apache.org/release-guide.html
> The spring.schemas file contains an invalid mapping
> ----------------------------------------------------
>
> Key: AMQ-3005
> URL: https://issues.apache.org/activemq/browse/AMQ-3005
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.1
> Reporter: Michael Monette
> Assignee: Gary Tully
> Priority: Minor
> Fix For: 5.5.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.