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

[Brian Stansberry (Jira)]

     [ https://issues.redhat.com/browse/WFLY-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFLY-13295:
------------------------------------
    Fix Version/s: 20.0.0.Final


[~ochaloup] I put a 20.0.0.Final Fix Version on this just because I assume the linked PR is in the version now in master and it sounded like you've written the intended test case.

> 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
>             Fix For: 20.0.0.Final
>
>
> 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)