It appears that your design uses the bean to delegate all method request to the
dependent object. In other words, your client never directly accesses the
dependent objects. If this is the case, then there is no reason for your bean
and dependent objects to implement the same interface. The bean can have the
same method names and parameters as the dependent object (for consistency), but
they would be different methods since the bean throws the RemoteException and
the dependent objects do not. It may not appear to be perfect OO solution but
so what? Beans are not OO constructs they are inter-process components with
special considerations.
--
Richard Monson-Haefel
EJB Expert for jGuru.com
( http://www.jguru.com )
Author of Enterprise JavaBeans
Published by O'Reilly & Associates
( http://www.ejbnow.com )
===========================================================================
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".
