HornetQ will pick up any hornetq-jms.xml it finds on the classpath and loads it.
Thanks for the reply. Taking my standalone use case into account, I have a config directory with my configuration (and namely hornetq-jms.xml). Should I add a separate directory and add it to the classpath to have this feature working?
Also, say I create this directory and I want to deploy 3 or 4 configurations coming from different systems: how do I do this since the file must be named "hornetq-jms.xml" ?
you will have to manage separate configurations per instance
Would that be possible that HornetQ loads "*-hornetq-jms.xml" instead? That way, for one particular hornetQ instance, I could add foo-hornetq-jms.xml and bar-hornetq-jms.xml" in its configuration directory and get the modularity I'd like.
We use hornetq in development and development teams have differents destinations. Some team members are working in multiple teams. It would be great if we could give them a config file that they have to drop in their config folder and have everything working. Right now, they have to patch a single file and it's a bit painful.
not presently im afraid. feel free to raise a jira to add the functionality however it wouldnt have a very high priority. Alternatively you could get one of your development teams to implement it and contribute to the community.