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

[Ondrej Chaloupka (Jira)]

    [ https://issues.redhat.com/browse/WFLY-13295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108246#comment-14108246 ] 

Ondrej Chaloupka commented on WFLY-13295:
-----------------------------------------

[~brian.stansberry] yes, agree. I created PR with the WFLY part and tests here: https://github.com/wildfly/wildfly/pull/13315

> 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)