We have had issues with dependency ordering with separate files.
it should however work if you're using the single file.
Maybe it's a bug, and it's probably fixed on trunk now.
I did perform a build from the trunk and it is fixed. I can now direct expired messages to my custom queue. Does anyone when the next production release of HornetQ is estimated to be?
P.S. The depenency ordering with separate files is still an issue. I had to include all my queues and settings in the core XML files (i.e. configuration / jms) rather than having them my own. So is this a known bug that is somehwere in the issue tracking system somewhere? I would like to watch it so I know when it's resolved.
I wasn't able to find any information on how to upgrade HornetQ on JBoss 6.0. So I upgraded HornetQ with the latest <trunk> version by copying the following files from the hornetq/build/jars folder to the following JBoss folders:
I was not however able to find the following file in the hornetq <trunk> release:
If anyone knows whether or not I upgraded the HornetQ libraries correctly on JBoss 6.0, please let me know.
Any assistance would be greatly appreciated.