Let's say I'm writing an app to be used by bank auditors. The app's GUI
will be complicated and Swing-based with a plethora of widgets. The auditor
will be able to select a customer, and view their information and account
history: name, address, list of all transactions in the past year, etc.
etc. The auditor will also be able to edit some of the information, like
changing the amount that was deposited on a certain date or adding/deleting
transactions. Let's call the main object which is edited an AccountHistory.
It will contain all the data for the GUI, including, say, a List of
Transactions and pointers to other smaller objects.
Auditors charge a lot of money, and they're also very impatient. They might
be willing to wait a few seconds while a user's AccountHistory is loaded,
but once it's loaded they don't want to wait while network operations take
place. And, we don't want them sitting around, continually waiting for
things to load.
For instance, let's say the auditor flips back and forth between a
transaction that occurred in January and another transaction that occurred
in December. The auditor doesn't want a network operation to take place
each time they click on a transaction for more information. So, all of the
data must be on the client.
And, let's say that the GUI is very complicated. The contents of JList A
depends on whether JCheckBox B is checked, and which item is selected in
JList A determines the list which is shown in JList B, etc. etc. We don't
want a network operation to occur everytime the user selects an item in
JList A.
Also, let's say sometimes the auditors access the network over the
internet, and sometimes over a LAN. To make matters even more complicated,
let's say another machine (connected over the internet) wants to do bulk
operations on AccountHistorys. Like, get 100 AccountHistorys at one time,
look for certain patterns, and perhaps edit those AccountHistorys.
Given the (unchangeable) constraints listed above, what's the suggested way
to use entity beans in this situation?
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
