-
Key: JAV2I12-30
-
Legacy Issue Number: 1591
-
Status: closed
-
Source: Anonymous
-
Summary:
Summary: This item arises from the Java-to-IDL Mapping RFP, but is also of
concern to the IDL-to-Java RTF because it affects the IDL-to-Java
mapping.When adding support for idlToJava generated Stubs to
"InputStream.read_Object(java.lang.Class clz)" we ran into a small
problem while writing the code. Initially we used "clz.newInstance()"
to create an instance of the Stub object. The problem here is the
Stub does not have a default constructor, so newInstance throws an
exception. We added a default constructor to the stub and everything
worked fine. The question is: should we add a default constructor to
the stubs generated by idlToJava or should we use reflection(cost??) to
invoke the one constructor that is already a member of the stub class?I propose that we state in the spec that a default constructor is
required on all generated Stubs. -
Reported: JAV2I 1.0b1 — Mon, 29 Jun 1998 04:00 GMT
-
Disposition: Resolved — JAV2I 1.0
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
JAV2I12 — Default Constructor for Stubs
- Key: JAV2I12-30
- OMG Task Force: Java to IDL December 2000 RTF