The enterprise bean must not attempt to define a class in a package.
I think this statement is rather about the Reflection API or something like that...
With the
Java Reflection API it's possible to do many "nasty", unusual things. For instance: accessing private class members! (Dependency injection is heavily based on this.)
This statement you've quoted (actually the EJB-container contract) prohibits some of these functions for the developer(bean provider).
That's why:
This function (defining a class in a package)
is reserved for the EJB container. Allowing the enterprise bean to perform this function would create a security hole. Correct me if I'm wrong!
Andor N�meth
[ August 07, 2007: Message edited by: Andor Nemeth ]