Dan, thanks a lot for your reply..
Yeah, it cause weird behaviour when not handled in the expected chain. Michael 2011/3/31 Dan Allen <[email protected]> > On Wed, Mar 30, 2011 at 11:19, Michael Schütz > <[email protected]>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 > > -- > Dan Allen > Principal Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://www.google.com/profiles/dan.j.allen#about > http://mojavelinux.com > http://mojavelinux.com/seaminaction > >
_______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
