]
Ondrej Chaloupka commented on WFLY-13295:
-----------------------------------------
Yes. The WildFly will include the test to check that the simple EJB without other
annotations ({{@TransactionAttribute}} in particular) will be enabling the inbound rts
bridge.
(the test is here
REST-AT inbound bridge is not activated for EJB without
TransactionalManagement annotation
------------------------------------------------------------------------------------------
Key: WFLY-13295
URL:
https://issues.redhat.com/browse/WFLY-13295
Project: WildFly
Issue Type: Bug
Components: Transactions
Affects Versions: 19.0.0.Final
Reporter: Ondrej Chaloupka
Assignee: Ondrej Chaloupka
Priority: Major
The REST-AT inbound bridge is activated per deployment. It's activated for a
deployment which contains a REST endpoint identified with `@Path` annotation where in the
same class has to be included either annotation `@Transactional` or
`@TransactionAttribute`.
The point is to activate the inbound bridge for deployments which contain a transactional
managed method (CDI or EJB) which can receive the txn context, ie. possibly a context of
REST-AT transaction as well.
The issue is that EJB beans are transactional by default. The EJB bean class does not
need to specify any `@TransactionalAttribute` to be already container managed (from txn
perspective) with attribute `REQUIRED`. Which means taking incoming txn context and will
work with it.