|I need a few clarifications on this. | |DO you mean you want to have Transaction be Externalizable? So that |Transaction upon externalization writes itself into the ObjectStream as a |TPC?
precisely yes, |If this is what you mean, it would require wrapping any Tyrex Transaction |object with a Proxy that would perform externalization? I am a bit yes, a proxy or a wrapper or extension or something. |confused here how would de-serialization happen? Just the same way, we are talking about a "static" field for the TPC exporter and importer. The TPC importer is in the readObject and creates a local transaction object. The design for the transaction right now barfs everywhere, the transport layer has to be aware of it (ugh!) when really the transport layer should only be aware of serializable objects. in fact just have the Transaction lookup the JNDI entry for exporter and importer, that would be super sweet... neatly packaged and confined. It sort of looks bad to have an absolute unified layer and interceptors and all the modern patterns at play and then a fat "if transaction Manager bla bla bla then bla bla bla" in the middle of your transport layers. Does this make sense? marcf |> _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
