> Sanjeev Kumar wrote:
>
> > I believe that EJB1.1 does not have a provision for multiple interfaces
> > to a bean. This is where the CORBA Component Model (CCM) had shown some
> > initiative. [The last time I checked, the CCM working group was actively
> > working to provide inter-operability with exisiting EJB spec.]
>
> There is nothing in the spec that prevent having multiple interface for the same
> bean implementation.
That is not correct. The XML-DTD specifies that a bean can only have one
remote interface.
> You can deploy multiple beans that will use the same implementation. This has
> also the advantage of having the possibilty to specify different deployement
> option for each of the interfaces to the bean.
.. and the disadvantages of having several pools with the same
implementation (inefficient), and in the case of EntityBeans you may
have the same identity alive in several instances (thus inconsistencies
may occur).
> What you can also do is create multiple interfaces and make your remote
> interface implements all these interfaces. As long as all the methods in the
> interfaces respect the EJB specification, there is absolutly no problem.
This is recommended for EJB1.1. Whether this will change in EJB2.0 (COM+
and CORBA3 supports this..) or not we will see, but I cannot see any
technical reasons why it wouldn't be allowed. Does anyone know of any
gotchas with having several interfaces? Oh yeah, almost forgot, one of
the interfaces will have to be marked as primary, since the return type
from create and find methods is not Object but the remote interface.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
