observer & observable

[Mary John]

Hi all

In Andrew's book, server window and related configuration options Gui
implement the observer and observable. I wanted to find out if this is
necessary as per the requirements (my assignment is B&S) and it mentions
that
" All configuration should be via a GUI and should be persistent between runs ". It also mentions about using suncertify.properties for persisting
config.

Are most of you using observer? if so, did you choose to do so because of
any must requirements in the assignment? I want to keep it simple just meeting the requirements.

Thanks
Mary

[Roberto Perillo]

Hey, Mary.

No, it is not necessary, not at all. I was thinking about implementing an observer to the main application GUI; when the database state changes (I'm using cache), all clients are notified. But it is not really necessary, so what I did is, when the user tries to book a room, all records being displayed are refreshed.
About the persistence between runs, it means that, when the user enters the information relevant to the application initialization, these information must be recorded in a file called suncertify.properties, which must be in the current working directory (System.getProperty("user.dir")). The next time the user starts the application, these information must be retrieved from the suncertify.properties file and fill the input fields automatically.
Hope this helps.
[ May 14, 2008: Message edited by: Roberto Perillo ]

[Mary John]

Thanks very much Roberto, for the details.
It was very helpful. So I am going forward with the simple approach.

Mary