It is common for many to name their beans in the following fashion:
Foo.java - base interface, used by both bean interface and bean
implementation classes to ensure compile time safety.
FooBean.java - bean interface class
FooHome.java - bean's home interface
FooImpl.java - beam implementation class.
The Home interface is then found in/or near the root of the jndi context
of the server that contains it. This is fine for a small population of
interfaces. But what do you do when the number grows? What sorts of
policies have been used for larger numbers of deployed beans.
I could imagine using something that includes the company name and the
goal of the bean. (This would be redundant to some degree because this
is already part of the package.) But that would not work well if you
are trying to implement a "well known" interface for an application
assembler.
Do you use a locator / activator behavior to create an aggregation on
top of something that is really flat?
Thanks for your thoughts on this,
don.
===========================================================================
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".
