I have figured out that you can also create multiple *-hornet1-configuration.xml files. Each of these can be sparsely populated. So I can create a separte *-hornetq-configuration.xml file for each individual queue that just contains a <security-settings> element. This works. However, it does create an unfortunate dual point of maintenance for the queue definition and the associated security config in separate files. However, it is functional.
Just checking, but do you mean you can define something like group1-hornetq-jms.xml, group2-hornetq-jms.xml, and group3-hornet-jms.xml and hornetq will load them each? Do you need to configure anything else differently to load the seperate hornetq-jms.xml files? Or am I totally mis-reading these posts?
Yes, you can have group1-hornetq-jms.xml, group2-hornetq-jms.xml and group3-hornetq-jms.xml files to define the various queues/topics you want for each group. You can also have group1-hornetq-configuration.xml, group2-hornetq-configuration.xml and group3-hornetq-configuration.xml files to define specific <security-settings> for the addresses you creates in the former files.
All will be picked up as based upon these names without any additional configuration.