I think we should include a version number in there. JUST in case in ActiveMQ 6.0 we decide to get radical with the xml configuration and make it not compatible with 5.0. We would not want the old 5.0 clients pulling down the xsd as the 6.0 clients.
Regards, Hiram On 6/15/07, James Strachan <[EMAIL PROTECTED]> wrote:
There has been a fair bit of discussion along with numerous JIRAs on this. http://www.nabble.com/Handling-XSDs-and-Spring-2-XML-processing-etc.-tf3921424s2354.html Going forward for 5.0 it would be nice to change the namespace to use Spring 2 namespace conventions (making it easier for users to grok the namespace & schema locations) along with reflecting the Apache ActiveMQ domain name; plus removing the version from the namespace URI. So I'm proposing to change the namespace http://activemq.org/config/1.0 to be http://activemq.apache.org/schema/core so that firstly it resolves to the index page of all XSD versions for the activemq-core module; then secondly so that its more like the spring naming convention. e.g. an actual schema location is http://activemq.apache.org/schema/core/activemq-core-4.1.1.xsd e.g. a Spring 2 XML would look like this... <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:amq="http://activemq.org/config/1.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd "> or using version numbers <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:amq="http://activemq.org/config/1.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core-4.1.1.xsd "> There is a minor downside in folks having to change a line of their activemq.xml; though it should make things much simpler for folks working with Spring 2 going forward so I think its well worth the minor pain. Here's my +1 -- James ------- http://macstrac.blogspot.com/
-- Regards, Hiram Blog: http://hiramchirino.com
