Database control hangs in Workshop Tutorial !!!

Question

Hi,
I am using WLS 7.0.1.0/SP1 ( latest version ) with Workshop included, on Windows
XP Prof. In Workshop Tutorial, Step 3, the test hangs at the execution of
Applicant dbApplicant = bankruptciesDB.checkForBankruptcies(taxID);
I am asking if it is a known problem? There may be several reasons for this and
it is too expensive to investigate all of them:
1. Tutorial text misses a fragment describing special configuration for the Database
control
2. Tutorial is correct but default ( installation ) configuration of Database
control has bug(s)
3. A helper class, implementing BankruptciesDatabaseControl interface, is missed.
4. Implementation of Database control is buggy. What the magic happens when I
“SELECT TAXID, FIRSTNAME, LASTNAME, CURRENTLYBANKRUPT FROM BANKRUPTCIES WHERE
TAXID={taxID}”, i.e. only a sub-set of “Applicant” attributes in the query, and
how Database control ( using my interface method public Investigate.Applicant
checkForBankruptcies(String taxID) ) knows which database table field to map to
which Applicant” attribute ? [I suppose, creation of “Applicant” class is independent
from the database schema, isn’t it ?]
Thank you,
- Michael

Answer 1

Sure, I will send you the dump. Please, provide me with your e-mail.
As of column names, don’t you find it error-prone approach where a developer has
to “find” the names and type them into the code ? Since you are already deal with
a db adapter/controller, I suggest, the adapter has to read a db schema, gets
the column names and data types. In other words, I would expect in this case the
same functionality as provided by, e.g., TogetherSoft’s Control Center. It creates
Entity Beans out of the db schema and only then allows you to manipulate them.
Thank you and wait for your e-mail.
- Michael
"Anurag Pareek" <[email protected]> wrote:
Michael,
The names of the elements in the 'Applicant' class should match one-on-one
with the database column names in the corresponding table.
I guess you are using the default Pointbase database. Can you check whether
you were able to create successful connections to the Pointbase database
during server startup?
If the server is hanging at the statement you have mentioned, can you
take a
thread dump by using Ctrl->Break and email it to me.
Thanks,
Anurag
"Michael Poulin" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am using WLS 7.0.1.0/SP1 ( latest version ) with Workshop included,on
Windows
XP Prof. In Workshop Tutorial, Step 3, the test hangs at the executionof
Applicant dbApplicant = bankruptciesDB.checkForBankruptcies(taxID);
I am asking if it is a known problem? There may be several reasonsfor
this and
it is too expensive to investigate all of them:
1. Tutorial text misses a fragment describing special configurationfor
the Database
control
2. Tutorial is correct but default ( installation ) configuration ofDatabase
control has bug(s)
3. A helper class, implementing BankruptciesDatabaseControl interface,is
missed.
4. Implementation of Database control is buggy. What the magic happenswhen I
"SELECT TAXID, FIRSTNAME, LASTNAME, CURRENTLYBANKRUPT FROM BANKRUPTCIESWHERE
TAXID={taxID}", i.e. only a sub-set of "Applicant" attributes in thequery, and
how Database control ( using my interface method publicInvestigate.Applicant
checkForBankruptcies(String taxID) ) knows which database table fieldto
map to
which Applicant" attribute ? [I suppose, creation of "Applicant" class
is>independent>> from the database schema, isn't it ?
Thank you,
- Michael