yes there are a 1000 places that will benefit from client side interceptors
and Invocation as return. Also some clustering/failover and batching of
invocations (from Paul and Eric)
consider it done
marcf
___
Jboss-development mailing list
[EMAIL PRO
see my previous mail, this is a sub-set of the client side interceptor work
I want to do
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Jung
|, Dr. Christoph
|Sent: Monday, February 18, 2002 12:21 AM
|To: 'Jboss-Development ([EMAIL PROTECTED])'
|This raises an issue of adding payload not only to the Invocation itself
|but to the return from Invocation. Say we can introduce InvocationResult
|which can contain arbitrary payload along with the actual result of the
|invocation or exceptions that occured during invocation. Stripping the
|payl
Dr.
In clustering, I also have a need to piggyback information with the
invocation result. InvocationResult sounds like a good thing. My memory is
failing, but I think CORBA does the same.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jung
> ,
Hi,
(I currently have very little time, so here are just a
few thoughts. I may not have time to enter a discussion
about this.)
But what if something bad happens?
In your scenario, assume that Bean B updates a resource
in the context of transaction T'. This means that
transactional locks are h
