In our OWBEjbInterceptor, we have a disconnect between how
@AroundInvoke and @PostConstruct/@PreDestroy are handled.
In the former, we only call the ejb containers ic.proceed() when we
fall off the end of our own ic.proceed() -- this seems good because it
means the last 299 interceptor called proceed, allowing the biz method
to run.
But for the lifecycle (PostConstruct, PreDestroy) callbacks, we call
the ejb containers ic.proceed() no matter what the 299 interceptors
did (e.g. did not call through 299 ic.proceed to the bottom) -- in the
OpenWebBeansEJBInterceptor itself. Shouldn't this behave like
@AroundInvoke and only call the EJB one when we fall off the bottom of
our own invocation context?
--
Eric Covener
cove...@gmail.com
