I noticed a fairly obscure EJB programming restriction today that I
didn't know existed since the appserver I use doesn't enforce it:
"An Enterprise bean must not define a class in a package, as this is a
function reserved for the container for security reasons."
This exists both in EJB1.1 and EJB2.0 spec. I'm not sure about EJB 1.0.
1) Why is this a security risk?
2) Does any appserver out there actually enforce it?
3) Why hasn't anybody ever complained about this on this list?
4) If enforced, how do you manage a large scale EJB project?
Frank Sauer
The Technical Resource Connection
Tampa, FL
http://www.trcinc.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".
