Hi!
In EJB1.1 deploymentdescriptors one can use the "ejb-ref" element to
define links to other EJB's which makes it easier to code the EJB which
should reference the other EJB. In the docs it is stated that the
referenced EJB must be either in the same ejb-jar, or at least in the
same application unit.
But, is there really any technical reason why this couldn't be pointing
to an EJB of another server, even from another vendor. For example, the
DD of a bean deployed in server A by vendor X could have a link to a
bean in server B by vendor Y by simply having the EJB-reference
"java:comp/env/ejb/Foo" point to the JNDI name
"Y://somehost.com/ejb/Foo". Is there any technical reasons that make
this hard to do? I do realize that server A must of course have network
communication classes of server B, and tx and security propagation would
be problems, etc., so this behaviour should probably not be mandated in
the spec, but is there really anything that prevents this service from
server A? I mean, it's really nothing more than a convenient way for the
first bean to access the second, and it would increase the portability
quite a lot.
Any comments?
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
