Experts,
Please let me and Jeremy know if you agree that such shortcuts in the
ejb-jar.xml deployment descriptor are useful to be added.
thanks,
-marina
-------- Original Message --------
Subject: [ejb-spec issues] [JIRA] Commented: (EJB_SPEC-49) Add new
method-intf type to deployment descriptor for transactional lifecycle
interceptors
Date: Mon, 14 May 2012 13:56:20 +0000 (GMT+00:00)
From: jrbauer (JIRA) <jira-no-reply_at_java.net>
Reply-To: issues_at_ejb-spec.java.net
To: issues_at_ejb-spec.java.net
[
http://java.net/jira/browse/EJB_SPEC-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=339606#action_339606 ]
jrbauer commented on EJB_SPEC-49:
---------------------------------
To further clarify -
In particular, the new method-intf type would be useful with wild-carding since it let's you scope to a specific interface type. For example, to set NotSupported for the lifecycle methods without affecting other interfaces:
<container-transaction>
<method>
<ejb-name>MySession</ejb-name>
<method-intf>LifecycleInterceptor</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
> Add new method-intf type to deployment descriptor for transactional lifecycle interceptors
> ------------------------------------------------------------------------------------------
>
> Key: EJB_SPEC-49
> URL: http://java.net/jira/browse/EJB_SPEC-49
> Project: ejb-spec
> Issue Type: Improvement
> Affects Versions: 3.2
> Reporter: jrbauer
>
> Given that lifecycle callbacks of singleton and stateful bean interceptors can now run within container managed transactions, I think we need to add a new method-intf type to the possible values of the container-transaction->method definition in the DD. The current values do not provide the ability to specifically target transaction attributes to this style of interceptor via the DD. The name "LifecycleInterceptor" seems a good fit. Thoughts?
> I've seen at least one location in Javadoc that provides the list of possible meta-inf values, so at least one, maybe more, updates would be needed there as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira