I answered my own question. Orion chokes when comparing nulls in the
database. It seems that Orion generates comparisons based on the primary
key, even when you do the ejb equivalent of a "select *". I fixed this by
using the true primary key that was being used in the database table,
instead of using something else (even though it is legal and works fine with
Weblogic). My company is looking for reasons to move from Weblogic, and the
only thing I could tell them is, "I'll get back to ya!". I would have
figured this out a week ago if Orion's team were kind enough to provide us
access to the classes it generated, but they figured we "don't need them".
Orion needs to change it's responsiveness to customer issues and questions,
or it should just go open-source and call it a day if they're going to use a
mailing-list as it's primary means of support.
Robert Smith
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
