> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Luke
> Taylor
> Sent: Thursday, January 31, 2002 9:32 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] TODO: client side interceptors
>
>
> olger Engels wrote:
>
> >
> > I'm glad to see, that jboss will support pluggable interceptors on the
> > client side, now. You can do cool things with that. Think of:
> >
> > ...
>
> >
>
> > o caching interceptor (for getters)
>
>
> How will that work in practice? Aren't the interceptors stateless,
> without being specific to a particular EJB/component instance?
>
Well, on the server side, the interceptor chain is uniquely attached to each
container. On the client side, you could have a unique interceptor
chain(instances in memory) attached to each and every proxy. I really like
this idea for EntityBeans. Could be kinda cool. Of course, we'd have to
expand on the metadata to describe this type of thing.
> > o invocation bundeling (send an array of method invocations and
> return an
> > array of results .. all that in one user transaction)
>
>
> I don't quite get that either - interceptors are meant to be transparent
> to the client code. So how could a client make multiple (sequential)
> invocations and have them bundled into a single request?
>
You're right here. EJBs have no asynchronous interface like CORBA object do.
Plus, in EJB the request is not exposed like in CORBA as well.
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
