FYI, this test case is going to be invaluable to you:
org.apache.openejb.core.stateless.StatelessInterceptorTest
I wrote that up before we had the corresponding itests. It was
invaluable to me when writing the original binding processing code.
It doesn't have the situation described in OPENEJB-583, but it could
be added so you'd have a small isolated unit test to walk through with
a debugger.
-David
On Dec 27, 2007, at 6:37 AM, Jacek Laskowski (JIRA) wrote:
[ https://issues.apache.org/jira/browse/OPENEJB-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on OPENEJB-583 started by Jacek Laskowski.
Problems excluding default interceptor
--------------------------------------
Key: OPENEJB-583
URL: https://issues.apache.org/jira/browse/OPENEJB-583
Project: OpenEJB
Issue Type: Bug
Components: interceptors
Affects Versions: 3.0-beta-1
Reporter: Prasad Kashyap
Assignee: Jacek Laskowski
Fix For: 3.0-beta-2
http://www.nabble.com/forum/ViewPost.jtp?post=10271166&framed=y&skin=2756
This problem exists uniformly for both annotation specified and DD
specificied interceptors
If you try to exclude a class from default interceptors, the
lifecycle events are excluded but some of the business methods are
not.
When a @ExcludeDefault is specified at the class level, default
interceptors are excluded only for those business methods that do
not have a @ExcludeClass specified on them.
If a business method has a @ExcludeClass specified on it, it
ignores the @ExcludeDefault specified for the whole class (either
by annotation or xml).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
