EJB Programing Restrictions ----------------------------- The enterprise bean must not attempt to define a class in a package. This function is reserved for the EJB Container. Allowing the enterprise bean to perform this function would create a security hole.
Could you explain in detail, because i am confused.
Originally posted by Seenu R: "Allowing the enterprise bean to perform this function would create a security hole."
It was this statement that convinced me that it was talking about "defining a class in a package" at runtime - by generating the JVM bytecodes in memory and then attempting to load the class - this would bypass any safeguards present in the J2EE deployment/verifier tools.
You're not going crazy. You're going sane in a crazy word. Find comfort in this tiny ad:
a bit of art, as a gift, the permaculture playing cards