MultipleVFSParsingDeployer on HornetQ

[clebert.suconic]

@Ales,

You have created a MultipleVFSParsingDeployer on the HornetQ's branch.

For other's reference:

http://anonsvn.jboss.org/repos/jbossas/branches/Branch_Hornet_Temporary_2/hornetq-int/src/main/java/org/jboss/as/integration/hornetq/deployers/HornetQConfigMultiParserDeployer.java

. It's all good.. but I was wondering if it wouldn't be possible to make it to have multiple prefixes. (that is *hornetq-configuration.xml or *hornetq-queues.xml).

Of course first thing I tried was to make the names expressions.. but that doesn't work.

I had in the past tried to do the accept manually.. and that's when I decided moving to multiple instances of the deployments.

This is just desirable. If that's more than 15 minutes work.. just forget it. (We don't have prefixes on hornetq standalone anyway).

[alesj]

This would mean we need to handle multiple suffixes matching multiple names.

It's definitely doable, and you're welcome to contribute, but unfortunately it's not < 15min work. ;-)

If this is what you eventually need, you can go back to your previous 2-copy deployers.

As that is not wrong, specially when you're targeting suffix matching,

but in your current case I saw you're actually matching exact names, hence I changed it to multi deployers.

Multi deployers are mostly meant for merging metadata, as in the case of RAR metadata.

e.g. ra.xml + jboss-ra.xml --> common/single RAR metadata

[alesj]

If this is what you eventually need, you can go back to your previous 2-copy deployers.

As that is not wrong, specially when you're targeting suffix matching,

Thinking about it a bit more, just noticed you need to be careful here not to override the attachment info.

e.g.

* you're matching -a.xml and -b.xml

* deployment contains both files; foo-a.xml and bar-b.xml

* both will be put under Configuration.class attachment key (by default)

* override of info

--> meaning you need to override the attachmentKey property on the deployer