thanks a lot for your reply..

Yeah, it cause weird behaviour when not handled in the expected chain.


2011/3/31 Dan Allen <dan.j.allen@gmail.com>
On Wed, Mar 30, 2011 at 11:19, Michael Schütz <michaelschuetz83@gmail.com> wrote:
Hi to all,

why is asynchronous interceptor "client-typed" ?

I believe the idea here is to defer the call to the EJB (as the type is only relevant when the interceptor is applied to an EJB). In fact, the client/server distinction is whether the interceptor is applied before delegating to the EJB proxy or whether the interceptor participates in the interceptor chain that's handled by the EJB container. So it's really a subtle concern.


Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597