I need a little help with transaction scope as it applies to MDBs.
My original impression of MOM was that anything an MDB did as a result of a message you sent was totally independent of what you as the sender were doing.
But the spec suggests that the transaction context of a message sender can be propagated to the MDB. In fact, I'm having a hard time trying to figure out how to get a session EJB running under one transaction to send a "fire-and-forget" message to a queue so that the resulting MDB activity proceeds under a totally separate transaction which competes with the original transaction independently.
Could someone please take a second to clear this up for me ?
