Both iBATIS and Hibernate support a rich object model. You don't have to map
foreign key fields in a database to primitive type fields, such as String or
Integer, on business objects. You an specify in iBATIS mapping files that
these fields are used to create "complex properties" as iBATIS document
WAS 6.0 uses JDK 1.4 doesn't it? Does iBATIS require JDK 1.5? I doubt it,
but thought I'd mention it.
I attended a NFJS conference that past weekend where Ted Neward said that
WAS has a very complicated classloader structure. I had a problem recently
with static variables in a class that worked f
Looks like another option is to keep track of the changes
with something like the Unit Of Work pattern in Patterns of Enterprise
Architecture, by Martin Fowler. I'm thinking I'll try that
route.
Nathan
From: Nathan Ward [mailto:[EMAIL PROTECTED]
Sent: Monday, October 09,
faster. Is that right?
Nathan
Nathan Ward
ResQSoft, Inc.
703.861.9103
www.resqsoft.com
I would consider appealing to authority figures by summarizing points from
current books that describe the problems with EJBs and especially entity
EJBs with specific references to books in case they actually care to read it
themselves. I believe the first or second chapter of POJOs in Action has
s
uot;Alert" table that has a wf_trans_id field, where the
wf_trans_id field is nine character field that is the primary key of the
WorkflowTransaction table. An Alert may or may not have an associated
WorkflowTransaction. In which case, we have found that the wf_trans_id field is
has nine charac
