[
https://issues.apache.org/activemq/browse/AMQ-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38849
]
Hiram Chirino commented on AMQ-1016:
------------------------------------
You have to realized that the namspace is used by the default xbean application
that is used to load the stand alone broker. And Yes that IS working.
So we change the namespace, then all the existing configuration files out there
would stop working as the xbean loader would no longer work.
> 4.1 RC1: META-INF/spring.schemas refers to building user
> "file:/Users/chirino/"
> -------------------------------------------------------------------------------
>
> Key: AMQ-1016
> URL: https://issues.apache.org/activemq/browse/AMQ-1016
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: n/a
> Reporter: Endre Stølsvik
> Assigned To: Hiram Chirino
> Priority: Minor
> Fix For: 4.2.0
>
>
> Referring to the 4.1 RC1 posted by Hiram Chirino Oct 06, here:
> http://www.nabble.com/ActiveMQ-4.1-RC-1-tf2397970.html#a6686974
> The META-INF file spring.schemas have the single line.
> "http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd"
> Notice "file:/" and "Users/chirino". Referring to
> org.springframework.beans.factory.xml.PluggableSchemaResolver's javadoc:
> "schema-location should also be a schema file in the classpath", and that
> no-one can tell what structure I will have on my fs, this must be wrong. In
> addition, I most probably won't have a user name "chirino".
> PS: In addition, the doc at
>
> http://www.activemq.org/site/how-do-i-embed-a-broker-inside-a-connection.html
> refers as such:
> xmlns:amq="http://activemq.org/config/1.0";
> .. and ..
> xsi:schemaLocation="http://activemq.org/config/1.0
> http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd";
> Wouldn't it be nice if this was put at a better place than such a
> snapshot-build URI? It could be put where it will reside when 4.1 actually is
> out, w/o anyone being to angry about changes during the finalization period,
> I personally believe.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
