Issue 1654: Default constructor for Java values (obv-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: The OBV spec is not very clear about whether the Java class generated for an IDL value has a default (no-argument) constructor. A no-argument constructor is needed so that the Helper class can construct a value when demarshalling. However, it should be package-private in order to limit its visbility to the Helper class and not expose it to client code. This is also true for state fields declared as private in the IDL value type (which the spec currently states are mapped to private in Java). Resolution: Revised Text: Actions taken: July 9, 1998: received issue July 30, 1998: closed issue Discussion: End of Annotations:===== Return-Path: Date: Thu, 09 Jul 1998 14:49:58 +0100 From: Simon Nash Reply-To: nash@hursley.ibm.com Organization: IBM To: obv-rtf@omg.org Cc: issues@omg.org Subject: Default constructor for Java values The OBV spec is not very clear about whether the Java class generated for an IDL value has a default (no-argument) constructor. A no-argument constructor is needed so that the Helper class can construct a value when demarshalling. However, it should be package-private in order to limit its visbility to the Helper class and not expose it to client code. This is also true for state fields declared as private in the IDL value type (which the spec currently states are mapped to private in Java). Simon -- Simon C Nash, IBM Java Technology Centre, Hursley, UK MailPoint 146, x245156 Tel. 01962 815156 or +44-1962-815156 Internet: nash@hursley.ibm.com Notes mail: Simon Nash@ibmgb