[jboss-jira] [JBoss JIRA] (WFLY-4169) Wildfly doesn't fail on deployment EJB with CDI @Transactional

[Carlo de Wolf (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055711#comment-13055711 ] 

Carlo de Wolf commented on WFLY-4169:
-------------------------------------

Technically speaking using Transactional interceptors on EJBs *is* allowed. See https://java.net/projects/javaee-spec/lists/jsr342-experts/archive/2013-03/message/23

The truth is that nobody wanted to figure out the impact of having JTA interceptors and CMT interceptors in place.
So you could for example use BMT and JTA interceptors.

I think this may need to become a configuration option.

> Wildfly doesn't fail on deployment EJB with CDI @Transactional
> --------------------------------------------------------------
>
>                 Key: WFLY-4169
>                 URL: https://issues.jboss.org/browse/WFLY-4169
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 8.2.0.Final
>            Reporter: Kamil Żbikowski
>
> When javax.transaction. at Transactional CDI is put on EJB application is able to be correctly deployed on the server. According to JSR345 it should not be possible. ??It is illegal to associate JTA transactional interceptors \[8\] with Enterprise JavaBeans. The EJB  Container should fail deployment of such applications.??



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)