The program must allow the user to specify the location of the database in both standalone and network mode and persist the db configuration details in suncertify.properties file. The application must read the properties file to determine the location of the db and display the data from the db.
Ray Dawson wrote:So do we place the location of the db file in the suncertify.properties file & read it from there or do we want the user to specify the location of the db file for first time & update that in the properties file ???
Ray Dawson wrote:is there anything else that we need to the properties file ???
SCJP (1.4 | 5.0), OCJP (6.0), OCMJD
Sean Keane wrote:
Will your properties file exist the first time a user runs the application?
Sean Keane wrote:
As per your instructions "persist the db configuration details". So you need to store all configuration information that a user can enter in your application. So that should be pretty straight forward? What configuration information can a user enter in your application?
Sean Keane wrote:
Andrew Monkhouse has a good example in his book of how to handle persisting the properties.
Ray Dawson wrote:
Sean Keane wrote:
Will your properties file exist the first time a user runs the application?
Yes, when it loads it has the link to the .db file, which the program reads to access the .db file.
Ray Dawson wrote:Configuration details as in what exactly ?
Ray Dawson wrote:
Where can I find it ?Sean Keane wrote:
Andrew Monkhouse has a good example in his book of how to handle persisting the properties.
SCJP (1.4 | 5.0), OCJP (6.0), OCMJD
Ray Dawson wrote:So what config details do I have to log anyways ? Cause I thought properties file was only for storing db locations
![]()
SCJP (1.4 | 5.0), OCJP (6.0), OCMJD
Sean Keane wrote:
Ray Dawson wrote:So what config details do I have to log anyways ? Cause I thought properties file was only for storing db locations
![]()
What configuration information do users need to enter in order to use (start up) your application?
SCJP (1.4 | 5.0), OCJP (6.0), OCMJD
Sean Keane wrote:When you run the application that you have created take a note of the configuration information required to enter in the GUI in order to start it. This is the information that you need to store in the properties file.
SCJP (1.4 | 5.0), OCJP (6.0), OCMJD
Sean Keane wrote:Does a user have to enter search details to start up your application?
Ray Dawson wrote:
Sean Keane wrote:Does a user have to enter search details to start up your application?
Yes!
SCJP (1.4 | 5.0), OCJP (6.0), OCMJD
Ray Dawson wrote:(I found no similar threads, so)
Ray Dawson wrote:
Sean Keane wrote:Does a user have to enter search details to start up your application?
Yes!
Roel De Nijs wrote:And how does your app know where to look for the database file (standalone mode) or for the network server (network client)?
SCJP (1.4 | 5.0), OCJP (6.0), OCMJD
Roel De Nijs wrote:
Ray Dawson wrote:What "other" things should be there in the properties file ??
What settings do you need for networking mode?
Ray Dawson wrote:So I really don't kow about the stuff required for networking
SCJP (1.4 | 5.0), OCJP (6.0), OCMJD
Ray Dawson wrote:As I said I haven't started working on networking mode as yet, as of now working on the standalone version only.
So I really don't kow about the stuff required for networking, hence other than the networking part am asking my first question again - What other things except the db location should i put in the properties file ?
Ray Dawson wrote:do we need to put in like say the locked data etc
SCJP (1.4 | 5.0), OCJP (6.0), OCMJD
Ray Dawson wrote:Lockd data = records which are booked
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |