activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] Commented: (AMQ-3005) The spring.schemas file contains an invalid mapping
Date Thu, 28 Oct 2010 13:13:00 GMT


Gary Tully commented on AMQ-3005:

The lack of filtering must be the result of a change to the resources plugin or the apache
parent pom. In any event, just filtering the current version does not give us what we want
for backward compatibility. We want all previous versions referenced so that existing schema
references will still work. 

This is tricky to automate as it requires a commit and part of the pre release process. For
the moment it may just be best to add the current and a set of future versions and note that
it needs to be checked before doing a release.

> The spring.schemas file contains an invalid mapping 
> ----------------------------------------------------
>                 Key: AMQ-3005
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.1
>            Reporter: Michael Monette
>            Priority: Minor
> The spring.schemas file, in META-INF, contains the following mappings:
> http\://
> http\://
> http\://
> http\://
> http\://
> http\://
> http\://
> http\://
> http\://${pom.version}.xsd=activemq.xsd
> The final mapping contains an unresolved placeholder, ${pom.version}.  XML files which
use, for example 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.

View raw message