[jboss-jira] [JBoss JIRA] (WFLY-13295) REST-AT inbound bridge is not activated for EJB without TransactionalManagement annotation

Ondrej Chaloupka (Jira) issues at jboss.org
Thu Mar 26 12:46:22 EDT 2020


Ondrej Chaloupka created WFLY-13295:
---------------------------------------

             Summary: 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


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.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list