I just checked in support for configurable message flows within Moksha. Out of the box, Moksha does not require an AMQP broker, and will work using the STOMP protocol through Orbited's built-in MorbidQ message broker.
I created the high-level idea of a "Topic" within Moksha, which allows applications/consumers/widgets to listen and send messages to them, without having to care about the underlying message protocol or broker.
To add support for an AMQP broker, all you have to do is add the following line to your configuration file (tested with Qpid and RabbitMQ):
amqp_broker = guest/guest@localhost
The MokshaHub will then automatically connect up to your AMQP broker, and will consume all messages from it, forwarding them to the STOMP broker, which will then be consumed by the users web browser.
I'll throw together some documentation for this shortly...
Cheers,
luke