> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Charlie Alfred
> Unless I'm mistaken this approach gets you a one-way interaction: VB makes
> synchronous calls to EJB.
No, you're right.
> 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.
This is actually part of a broader consideration than just contacting COM on
the server side, and while it doesn't represent the majority of what customers
are doing right now, I can definitely see the point in having an EJB making COM
calls to perform its business logic.
However, specifying a EJB to COM mapping would only address part of the
problem. After COM, EJBs will need to do some other fancy stuff not anticipated
by the norm, and we will be back to square zero.
I guess my point is that the most flexible way to address this problem would be
to have means to relax the JNI restriction on beans, but I wonder if this can
be done through the standard or if it's just better to let each EJB vendor have
their own proprietary way of doing that...
--
Cedric
http://beust.com/cedric
===========================================================================
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".
