JAV2I12 — stub classes can violate licensing and package sealing

Summary: Placing generated stub classes in the package in which the interface is defined
is flawed for a few reasons:

1) It can violate license agreements (e.g., Jini uses remote interfaces, and
if an RMI-IIOP stub is generated from one of the core Jini interfaces
the license agreement will be violated since a new public class
will be added to the core).

2) Placing generated classes in the same package as the remote interface
definition will not be possible if the package is sealed.

If an interface is public, such generated classes could be placed in a
sub-package of a CORBA-specific package, for example,
org.omg.CORBA.stub.java.rmi._Remote_Stub.