> Cedric Beust said:
>
> That would be an extremely complex specification to come up with, and I believe
> it would be overkill. A better approach IMO is to wrap your EJBs in a thin COM
> layer, thus making them full COM citizens. We have that today and quite a few
> customers are already using Visual Basic to access EJBs.
>
> --
> Cedric
>
Unless I'm mistaken this approach gets you a one-way interaction: VB makes
synchronous calls to EJB.
What if you want to allow an existing EJB to initiate a call into an existing
COM object? Or, if you want to make an asyncronous call from a COM object
into the COM-EJB wrapper, return immediately, then make an async callback
to the original COM object when the call is complete.
I can see ways to do the above using JNI; however, JNI access is prohibited
by the 1.1 EJB spec. And it sure seems like overkill to have to stick a JMS
layer in the middle.
Or am I missing something?
Charlie Alfred
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
