Yes piggybacking works too: we do that with interposition in JTS.
Jonathan Halliday wrote:
It's hard to do lazily when all the communication is top down - there is no mechanism for the child to call up to the parent to register. You'd have to piggyback the registration on the return leg of a top down call rather than initiating a new bottom up one for it. That's roughly one of the reasons I'm preferring to build the remoting transport around the jta rather than the jts. For example, the replay completion recovery model in jts won't work with remoting either - it needs the top down xa recovery scan model instead.