Experts,
While you are thinking about David's proposal (as I hope you all do ;)
), here is another question: do we need to provide a standard way to
guarantee a single MDB instance running in a server instance? I do not
propose support for all other features available to the singleton
session beans, just a guarantee of a single MDB instance.
In GlassFish (RI) we had this request to support message ordering
processed by the MDB.
If you think that it is useful, we can add an attribute (e.g.
'isSingleton') to the @MessageDriven annotation that would default to
false for backward compatibility.
thanks,
-marina