Document change of form of exception provided from server to client when transaction failure occurs

Please document different behavior (enhancement) of exception propagation for transaction failure in EAP 7.1 in comparison to EAP 6.4/7.0.

EAP 7.1 brings different behavior of exception propagation from server to client when transaction failure occurs.

This came with the introduction of wfly transaction client which handle exceptions differently.

EAP 6.4/7.0 just takes exception as it is, serializes it and pass it over the wire to the client. When the client does not have the Exception class on its classpath it gets CNFE.
The EAP 7.1 solves this issue by introducing exception org.wildfly.common.rpc.RemoteExceptionCause which is known to the client as it's from jboss/wildfly library. Server clone the origin exception to this new one and puts all field of the original exception to string form and add them to Exception's message. Then server passes only exceptions of type RemoteExceptionCause to the client.