Gilles and others,
You mention the Data Access Beans, which are probably not an option in our
application.
What are some of the alternatives? I have built a set of beans that support
relatively
stable files for our system. I doubt I did this optimally. In our case, I
used a keys to data
values. I also included an expired flag. The first person to hit a file will
load the data.
If a table changes, the expired flag is set. This data does not change very
often at all
(most files have been in production with no data changes for over 5 years). I
did have
to make an assumption that is OK for now that as long as you are authorized to
the
application you are authorized to this master file type data.
I can see some drawbacks to my design particularly with larger files. The
largest
in this case is only about 3000 records. So far that has not been a problem,
but
it would be nice to have a more selective cache. Another problem would be if
it becomes necessary to lock down individual files. Most of these beans
support
custom tags used in the user interface that uses Struts to control the view.
David Morris
>>> Gilles.DUCRET@lloydsbank.ch 07/02/01 01:27AM >>>
...I suggest you to use the Data Access Beans provided by IBM. They have
caching features allowing you to read the result set even if
it is closed (In fact you don't read the resultset, but a cache object
containing the result).
Gilles
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---
