We are considering to allow the Bean Provider to specify additional methods in the
home interface in a future release of EJB.
What Ian proposes will be then the right solution.
Vlada
>
>Tim's third approach suffers from only one problem - lack of encapsulation.
>Clients need to know to ask different beans for summary and detail
>information, and the location of the data is held in two beans.
>
>A solution that addresses this is to allow class methods on Enterprise
>JavaBeans. These are similar to finders, but are allowed to return
>arbitrary information. Unfortunately the EJB spec does not support such a
>thing yet. I believe it should.
>
>Ian McCallion
>CICS Business Unit
>IBM Hursley
>[EMAIL PROTECTED]
>Tel: ++44-1962-818065
>Fax: ++44-1962-818069
>
>===========================================================================
>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".
>
>
===========================================================================
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".
