I would like ask for enhancing documentation in guide Developing EJB Applications of chapter 1.5.4. Transaction Behavior of EJB Invocations and section Server to Server Invocations.

Current text is not fully correct but it heavily depends on newly created section defined by JBEAP-2780.

• It should be said that transaction context is propagated with remote ejb call automatically. This is partly what sentence Transaction attributes for distributed JBoss EAP applications need to be handled in a way as if the application is called on the same server. but the statement is a bit clumsy. It's ok to say that for incoming call from remote EAP server the transaction attribute will be handled in the same way as for local ejb calls.
• sentence To discontinue a transaction, the destination method must be marked REQUIRES_NEW using different interfaces. is not fully true as NOT_SUPPORTED would bring discontinuing txn as well. I would rather omit this sentence as whole.

Now this section should contain more information in general.

• for sure it should reference how to call server to server with ejb remoting - JBEAP-2780
• it should talk about how to call server to server with iiop (if not later covered by JBEAP-2780)

Information on this could be found party on quickstarts. There are some information about this at:

• on IIOP jts README of https://github.com/wildfly/quickstart/tree/10.x/jts-distributed-crash-rec
• on ejb remoting and jta: https://github.com/wildfly/quickstart/tree/10.x/ejb-multi-server

To said something in general - transaction context is propagated transparently when called remote jboss eap (either with iiop or ejb remoting). When creating new bean as receiver of call then it behaves the same way as any other bean. When want to call remote bean then special configuration is needed.