openejb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jack Cai <>
Subject Re: Propagating extra context information in remote EJB calls
Date Tue, 10 Nov 2009 15:21:04 GMT
Thanks David! I did try CORBA interceptors and it works well with RMI/IIOP
calls, exactly what I want. Unfortunately OpenEJB does not use the IIOP
library that comes with JDK, so intercepting IIOP calls cannot intercept
remote OpenEJB calls.

What I want to propagate is actually a simple ID string.


On Fri, Nov 6, 2009 at 10:43 AM, David Jencks <>wrote:

> AFAIK openejb does not propagate transaction context.  I thought about it
> for corba a long time ago but I have never found anyone who actually wants
> distributed transactions so never made the time to implement it.
> With Corba I believe you can add client and server interceptors and tack
> whatever info you want onto the request, but I found it a difficult
> programming model to understand.
> What context information do you want to transmit?
> thanks
> david jencks
> On Oct 29, 2009, at 4:15 AM, Jacek Laskowski wrote:
>  On Thu, Oct 29, 2009 at 10:16 AM, Jack Cai <> wrote:
>>  1. At the client side, intercept the client call before it's sent out,
>>> and
>>> attach some extra context information with the call;
>>> 2. At the server side, intercept the business method call before the
>>> method
>>> is actually executed, so that I can retrieve the extra context
>>> information
>>> coming with the call and set it into the server thread's context.
>>> I need to transparently do this for all EJBs. I was hoping I could do the
>>> trick only once in the code, instead of having to take care of all EJBs
>>> (e.g., use AOP to specify to intecept each invidiual remote interface).
>>> So in a word, I guess this is pretty much the same as how
>>> transaction/security context gets propagated today. Does this make more
>>> sense now?
>> Nope :] I still don't know what exactly you'd like to add to a call.
>> Yet, you're right that OpenEJB adds some additional data for security
>> and tx mgmt, but I don't think it was exposed for public consumption.
>> Jacek
>> --
>> Jacek Laskowski
>> Notatnik Projektanta Java EE -

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message