On 7 May 2010 16:48, Sorin S. <[email protected]> wrote:
> Hi,
> I was thinking we could change the virtualhosts.xml so that structures like:
>
> <queue>
> <name>test-queue</name>
> <test-queue>
> <exchange>test.direct</exchange>
> <durable>true</durable>
> </test-queue>
> </queue>
>
> which make the validation of the xml file cumbersome would be replaced with
> something like:
>
> <queue name="test-queue">
> <exchange>test.direct</exchange>
> <durable>true</durable>
> </queue>
Good idea,
I'm not sure what we can do about the initial elements in the
config.xml file, such as conf, work, prefix. These are arbitrary (and
optional) element names that are recognised by commons configuration
as being variables that will be interpolated through the rest of the
file. So, there could be an adk element that is referenced later as
${adk} and so on.
I guess you could go the same way as the queue and virtualhost tags,
and add a <property name="adk">whatever</property> element, but the
commons configuration variable interpolation would need re-written.
> With this, we can validate
> the whole configuration (config.xml + virtualhosts.xml) given that in
> config.xml we do not allow the definition of virtualhosts anymore but only a
> pointer to virtualhosts.xml file.
Remember that the virtualhosts element in config.xml is either a
pointer, or the equavalent of an embedded virtualhosts.xml file. This
can probably be easily sorted with namespaces, though?
Andrew.
--
-- andrew d kennedy ? edinburgh : +44 7941 197 134
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
