Haroon Rafique wrote:
Now my question to you is "what is the most convenient file structure which will let me meet my above-stated requirements?"
So, far I have thought of (and discounted):
1. ResourceBundle (since it will not keep the original order)
Likely candidates are:
1. custom code to read a .properties file which maintains the order (something along the lines of using getResourceAsStream() - have to think about locales).
2. Use Digester to read XML data (have to think about locales).
I'm pretty certain some of you must have run into this problem beforehand.
Can I call upon your experience to provide me with some input or point out something obvious that I may have missed?
Obligatory Monty Python quotation: "What's wrong with a Kiss, boy?" Why not just grab it in the cron job and serialize it to a file using plain old Java serialization? Or, failing that, using the new-fangled 1.4 XML encoding? This sort of thing is very well handled by the VM (and serialization has been stable/consistently stored for several years now), so why create extra work for yourself?
Admittedly, it might be nice to use a full caching system to control how often things go to the database using your DAO system for hte rest of the model, but if you're already working fine with this model why not just keep it but use some type of built-in serialization?
Kirk Wylie M7 Corporation
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
