Ole, I never realized this until I was working on the client interceptors yesterday late at night. Our transaction object requires an external person to serialize itself. Namely the extraction of the transaction propagation context is done outside the transaction itself.
This is a problem as it means that whoever is doing the serialization (in our case the JRMPInvoker layers) MUST know about the TM and that means we need to set the transaction monitor on them somehow. It works. If however we set the static entry on the Transaction implementation then the writeObject(Stream) call could take care of it own serialization (by getting the TPC and replacing the Tx by the TPC on the stream and that would be that... I think it would be a bit more self contained from a design standpoint. This lack of containment becomes very apparent as I put an interceptor layout on top of the client layers, not a biggy just FYI marcf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
