Subject | "ini-files" in Java |
---|---|
Author | Peder Skånning |
Post date | 2005-05-13T13:29:20Z |
Hi!
I am building a Java application as a frontend to a Firebird Database. The
ConnectionDescriptor is compiled into the binary, which is deployed with the
customer. In Win32 applications I usually store the ConnectionDescriptor in
an ini file or in registry, so the customer can cnange server or path
without a recompile of the application.
In my Java application i have tried to store the ConnectionDescriptor in a
text file "connection.txt", which I put in the same directory as the
application. I works if the path is not to tricky (spaces or volumes on UNC
like paths are tricky in Java).
Is there a standard way to store settigns like the registry in Java?
I have put the Connection and all the SQL in a dbClass. Durint
initialisation I replace the ConnectionDescriptor with the contents of
"connection.txt". However it is hard for me to do this replace before the
application tries to connect with the original ConnectionDescriptor. How do
I affect the creation order in the application? I build with jBuilder2005.
Thanks
Peder
[Non-text portions of this message have been removed]
I am building a Java application as a frontend to a Firebird Database. The
ConnectionDescriptor is compiled into the binary, which is deployed with the
customer. In Win32 applications I usually store the ConnectionDescriptor in
an ini file or in registry, so the customer can cnange server or path
without a recompile of the application.
In my Java application i have tried to store the ConnectionDescriptor in a
text file "connection.txt", which I put in the same directory as the
application. I works if the path is not to tricky (spaces or volumes on UNC
like paths are tricky in Java).
Is there a standard way to store settigns like the registry in Java?
I have put the Connection and all the SQL in a dbClass. Durint
initialisation I replace the ConnectionDescriptor with the contents of
"connection.txt". However it is hard for me to do this replace before the
application tries to connect with the original ConnectionDescriptor. How do
I affect the creation order in the application? I build with jBuilder2005.
Thanks
Peder
[Non-text portions of this message have been removed]