Good question. The easiest solution is probably to change one of the EJB dups that looks
at annotations to also check for @Transactional and fail accordingly.
Sent from my iPhone
On Mar 28, 2015, at 11:56 AM, Eduardo Sant´Ana da Silva
<eduardo.santanadasilva(a)gmail.com> wrote:
I'm looking at this issue:
https://issues.jboss.org/browse/WFLY-4169
In the ejb-3_2 specification :
It is illegal to associate JTA transactional interceptors (see [8]) with Enterprise
JavaBeans. The EJB Container should fail deployment of such applications.[39]
@Transaction annotation was introduced in JTA 1.2,
As Narayana 5.0.0.M3 is now JTA 1.2 compliant, and it was introduced on Wildfly since
version WildFly 8.0.0.Beta1, what should be done?
Because this restriction could be removed in the future versions:
[39] This restriction may be removed in a future release of this specification
If this is needed, how to proceed? Should be done on Weld subsystem, something similar
with the annotations markers, just to log the problem or it will be more tricky, since the
deployment should be rolled back (by the specification)?
--
__________________________
Eduardo Sant'Ana da Silva
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev