Jacek Laskowski wrote:
On 1/15/07, Raj Saini <[EMAIL PROTECTED]> wrote:
I feel, it would more depend on the component developer. For example,
she/he may choose to have default (package private) access modifier if
test classes are going to reside in the same package.
I've been thinking along those lines. As dependency annotation are to
configure a EJB component's state, there should be a way to do alike
outside the container. Tests may reside in the same package as the
classes they test, but in general if the EJBs are to be run outside
the container, they will miss some initializations.
I understand your point. Having public methods on bean class should not
be a problem. Since these methods are not part of the business
interface, they wont be accessible to the component clients.
Thanks,
Raj
Jacek
