JDK-8049375 : Extend how the org.omg.CORBA.ORB handles the search for orb.properties
  • Type: Sub-task
  • Component: other-libs
  • Sub-Component: corba:orb
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-07-05
  • Updated: 2017-05-17
  • Resolved: 2017-02-09
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 10 JDK 9
10Fixed 9 b157Fixed
Related Reports
Relates :  
JDK-8177668 - extend how RMI-IIOP handles search for orb.properties
Relates :  
JDK-8175177 - org/omg/CORBA/OrbPropertiesTest.java changes JDK under test
Relates :  
JDK-8174665 - Release Note: Extend the search path for the org.omg.CORBA.ORB orb.properties file
Description
org.omg.CORBA.ORB specifies the search order to locate the ORB and this includes searching ${java.home/lib/orb.properties.

This bug asks that the OMG specifications be checked to see if this is specified by OMG or whether this is just normative text in the Java SE specification. If this is not mandated by OMG then this bug asks that the reference be downgraded to non-normative or just removed.

It would also be used to get some sense as to whether customers or developers create orb.properties in the lib directory. If this is common then it may be necessary to provided a supported means to do this by allowing the properties file to exist in the proposed top-level "conf" directory.
Comments
I think we should at least try to change the class description for step 5 to say that the ORB configuration is picked up from a JDK specific location. We should also consider allowing the configuration in the conf directory and include an @implNote for this.
04-08-2016
if the standard location of the orb.properties file is changed there is probably a knock on effect to other 3rd party ORBs. For example JacORB http://www.jacorb.org/releases/3.0/ProgrammingGuide.pdf page 16. The fact that corba is no longer ootb enabled lends itself to reducing it compliance or making subtle changes, such as, locating orb.properties in ${java.home}/conf, if that is what is desired or required. I think this sub task is complete, n'es pas?
04-08-2016
could use a symbolic link to properties in ${java.home}/lib, if that's a CORBA compliance issue. I presume the desire is to have properties in conf directory
08-09-2015
Thanks for the reference to IDL to Java Language Mapping specification. One thing that I note is that the ORB javadoc has an expanded list of ways to locate the ORB properties, including "hardcoded default behavior". It might not be worth it but we could change the hardcoded default behavior to look in ${java.home}/lib/orb.properties and have it be the preferred way for cases where someone really needs this. Ideally we could drop looking in ${java.home}/lib but this may be required to claim OMG complication (have we anyway to check this?). Also I'd like to explore dropping the references to lib from the javadoc, it's not clear how much freedom we have to change the javadoc.
16-10-2014
one reference found in the IDK to Java Language Mapping version 1.3 formal-08-01-11.pdf 4.21.9.2 orb.properties file The orb.properties file is an optional file. The search order for the file is: 1.The user���s home directory, given by the user.home system property. 2.The <java-home>/lib directory, where <java-home> is the value of the System property java.home. It consists of lines of the form <property-name>=<property-value>. See Table 4.3 for a list of the property names and values that are recognized by ORB.init. Any property names not in this list shall be ignored by ORB.init(). The file may also contain blank lines and comment lines (starting with #), which are ignored. the properties file could be relocated and a symbolic link retained in the lib directory ?
16-10-2014
Mark - would you be able to check the OMG specs to see if the lib directory is required? We are moving all user editable configuration from lib to conf as part of the modular image effort.
16-10-2014
It should be noted that we examined this issue as part of JEP 162 but we unable to determine at the time if searching ${java.home}/lib was mandated by the OMG specs or not.
05-07-2014