Hello, I want to use Spring 2.0.1, Lingo 1.3 with ActiveMQ 4.1-final. After several hours of trying to get it work (and reading tons of XSD / schema problem threads in this forum) I'd like to ask, if there's any working configuration out there?
My test-configuration is very simple: <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:amq="http://activemq.org/config/1.0" xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd "> <!-- ... --> <amq:broker useJmx="false"> <amq:transportConnectors> <amq:transportConnector uri="tcp://localhost:0" /> </amq:transportConnectors> <amq:persistenceAdapter> <amq:kahaPersistenceAdapter dir="/tmp/kahastore" maxDataFileLength="104857600"/> </amq:persistenceAdapter> </amq:broker> <amq:queue id="queue" physicalName="TEST.QUEUE"/> <amq:connectionFactory id="jmsFactory" brokerURL="vm://localhost"/> <!-- ... --> </beans> Depending on which version of the activemq.xsd I use, I get those errors: activemq.xsd from 4.1.0 release: Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was found starting with element 'amq:persistenceAdapter'. No child element is expected at this point. activemq.xsd from 4.1 branch (pre-4.1.1): org.xml.sax.SAXParseException: cvc-complex-type.2.4.b: The content of element 'amq:transportConnector' is not complete. One of '{"http://activemq.org/config/1.0":broker, "http://activemq.org/config/1.0":brokerInfo, "http://activemq.org/config/1.0":discoveryAgent, "http://activemq.org/config/1.0":messageAuthorizationPolicy, "http://activemq.org/config/1.0":server, "http://activemq.org/config/1.0":taskRunnerFactory, WC[##other:"http://activemq.org/config/1.0"]}' is expected. ActiveMQ might have a very high quality code base, but the current situation of changing / unstable XSD files (even for released versions!) is a nightmare. I have never seen an open source project where it is so extremly hard to get it work. Some months ago I tried the 4.1 snapshots and got them to work but unfortunately there were some serious kaha persistence problems (the storage crashed regularily). Now, the situation (with a 4.1-final) is worse - not even the simplest example-configurations seem to work - this really sucks! Don't get me wrong! I'd like to help to improve the situation, but actually I'm not having a single starting point. It would be really wonderful if - The XSD changes only for new major version - Every major ActiveMQ release gets an immutable XSD that is located at a stable URL - The XSD and the configuration examples kept in sync Best regards Oliver -- View this message in context: http://www.nabble.com/Is-any-working-%27Spring-2.0.1-%2B-Lingo-1.3-%2B-ActiveMQ-4.1-final%27-configuration-out-there--tf3127903.html#a8666552 Sent from the ActiveMQ - User mailing list archive at Nabble.com.