There's no change needed for the transaction attribute in the case of an inflowing tx context since TX_REQUIRED allows it. Originally the tx attributes were limited to TX_REQUIRED and TX_NOT_SUPPORTED because there were only JMS MDBs, and from a JMS API perspective transaction context does not flow from the message producer.
[Message sent by forum member 'ksak' (kenneth.saks_at_sun.com)]
http://forums.java.net/jive/thread.jspa?messageID=362640