Can anyone familiar with the JRMP invokers suggest how best to make them handle transaction contexts in a more flexible fashion.

The use case I'm interested in is where true distributed transactions are needed, rather than just client side control of transactions boundaries for tx that reside in the server.

Using the JBossTS JTS is possible where the transport is RMI/IIOP, since it has interceptors to handle the transaction propagation. That does not work with client side JRMP proxies for e.g. EJBs, since they are not aware of the JTS tx context on the client thread.

What is the best solution here? Ideally there should be some pluggable way of having the JRMP transport find the tx context on the client thread, serialize it and deserialize it on the server side.