On Jun 20, 2011, at 2:23 AM, Ivan wrote: > Hi, > I am looking at some interceptor samples, and after investigating some > failures, it looks to me that the issue is caused by two different method > level OVERLOADED_METHOD, EXACT_METHOD. Per the interceptor specification, it > only defines three level method. class and default (aka. package in OpenEJB > codes).
I'm not sure that's entirely complete. If there's an overloaded interceptor binding that says 'excludeDefaultInterceptors=true' and specific method binding that says 'excludeDefaultInterceptors=false' than for that one method the default interceptors should be included and for the others with the same name but different arguments the default interceptors would not be excluded. > The second issue is that, the spec requires that the interceptor configured > in the deployment script must be invoked after those from annotations. Do we have a spec reference for that one? There were certainly no discussions of this in EJB 3.0 when we added interceptors, or rather there were and that's what <interceptor-order> is for. Are we only having issues with order? I.e. not in terms of our code, but in the strict terms that we are producing the right set of interceptors but they are stacked in the wrong order. Or are we having issues also where we are including the wrong interceptors as well? -David
