LAO will cause the non-XA resource to be committed [b]first[/b] so for this to work the DB will need to be the non-XA one.
The XA protocol doesn't dictate order of prepare's or commit's of RMs, so any ability to do so would have to be defined in the JTA spec or be app.server specific (I have no idea what JTA or GF provides), but this might be a good way to go [b]if[/b] GF supports it.
[Message sent by forum member 'matterbury' (matterbury)]
http://forums.java.net/jive/thread.jspa?messageID=352497