Database Reference
In-Depth Information
A different reason for why you might want to place these setting in a properties file and read them
from there is to make handling an upgrade to the JVM easier. When the path to java.exe changes from
the jdk1.6.0_24 directory to the jdk1.6.0_28 directory, you only need to edit the properties file. This
presumes that it is easier to edit a text file on all your client computers than it is to recompile the code
and distribute a new jar file to all. That might be a personal preference.
One argument against recompiling is the possibility of introducing errors in the process, but I have
never seen that happen just from the compilation process, and perhaps we want to recompile our
classes in order to gain from any efficiency provided by the updated compiler. Maybe this is a personal
preference based on experience or standard practice.
Note
When the new Runtime Process starts, the Login Dialog will be instantiated again with the new application
identity. That will result in a new prompt for entry of a two-factor authentication code—one specific to the
selected application.
Connection String Editor
You can see in Figure 12- 8 that all the elements of an Oracle connection string are represented by text
fields on the Edit Application Connections screen,
EditAppConns
. We provide two functional buttons
there: one to add the newly described connection to the list, and one to save the list to the Oracle
database.
When we select the button to add the connection to our list, the Update Connection String button, it
only updates the local list; it does not store the new/updated connection string in the database. After
editing or adding connections to the local list, select the
Save List
button to update the database.
Figure 12-8.
Edit Application Connections functional screen
