We need to fire local transaction events from the jms resource adapter.

This is not a trivial change since there is currently no easy way for the JmsSession class
to work out when the transaction started and whether it is a local transaction.
There is no explicit start of transaction in JMS.

It probably needs a modfication to getSession() as this is the most obvious point
where work is first done in a new transaction after the commit/rollback on the session.