Yes, I was using Spring 3.0. (I didn't notice until you mentioned it that
the ActiveMQ distribution is using Spring 2.5.6. I guess somewhere between
the two the parsing started paying attention to the schema. When I switched
over to the spring jars that came with the distribution, it worked fin
I wrote a tiny bit of code intending to experiment with starting up an
ActiveMQ instance inside a web application (with the intention of eventually
using an "in the VM" configuration). I'm using ActiveMQ version 5.3.0, and
Java 1.6.0_17.
To start with, I simply tried to start an instance program
