If you are talking about the scheduled delivery, hornetq already supports this. You can find an example in HornetQ that just illustrates that.
THe documentation seems to imply that support for stuff like repeating delivery every so often - think Quartz is not possible. At the very least this sort of functionality is not mentioned.
My original thoughts were about using Quartz to schedule and push stuff "job parameters" onto Queues which are then actioned by a listener, w/ te message being payload originally given to Quartz as job parameters. The problem w/ this idea is that there are in effect two systems w/ queues and listeners when an uber HornetQ with more sophisticated scheduling would remove the need for Quartz. If HornetQ did support this sort of scheduling then there would be no need for Quartz, everyone could switch to HornetQ as an almost perfect replacement.