[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jacorb-bugs
Subject:    [jacorb-bugs] [Bug 486] New: Can't specify jacorb.properties
From:       bugzilla-daemon () inf ! fu-berlin ! de
Date:       2004-06-07 0:22:50
Message-ID: E1BX7uc-0001wf-00 () berners ! inf ! fu-berlin ! de
[Download RAW message or body]

http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=486

           Summary: Can't specify jacorb.properties location
           Product: JacORB
           Version: 2.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: ORB
        AssignedTo: gerald.brose@acm.org
        ReportedBy: king_ramen@yahoo.com
         QAContact: jacorb-bugs@lists.spline.inf.fu-berlin.de


The "cascading search" for jacorb.properties has always been problematic. 
Recent circumstances make it even worse.

I am doing cluster development, and to simplify my environment, I am using the 
same JAR files, classpath, etc. for all members.

I would like to have a separate jacorb.properties file for each cluster member, 
but the "detection" algoritm would force me to either:

1. Create a separate user account for each cluster member
2. Create separate launch directories for each member
3. Create separate directories for jacorb.properties and use different 
CLASSPATHS.

None of those solutions is as nice as simply passing:

-Djacorb.properties=/path/to/some/file/called/anything

to the JVM. Such a behavior should take precedence over the "automatic" 
detection algorithm as a way to allow people to specify unambiguously the 
location of the file.

The changes to code are minimal. Thank you for the great software and for 
considering this request!



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

[prev in list] [next in list] [prev in thread] [next in thread]