Currently, as soon as the ejb-jar is deployed, the embedded MDB get active. When the user need to inhibit a JMS flow, he must undeploy the entire ejb-jar. It would be interesting to be able to inhibit a single MDB, eg. for maintenance purposes.

A possible implementation is to add a specific interceptor in charge of the flow diversion.
When the inhibition is enabled, the interceptor put the messages to a buffering queue
When the inhibition is disabled, the interceptor checks if there are some messages in the buffering queue. If yes it processes them, ie. calls the onMessage() method