Earlier on a colegue of mine posted a "note of frustration" on findAll(). I
think i have found the reason.
Reason:
If you wrongly map the entity fields against the database,
mismatches in the entity bean will make orion do strange things. Try map a
sql char(1) to a java char :) When i remapped those to Strings all finder
methods worked just fine.
Symptome:
All finder methods returning Collections fail until you reget the
result as many times as there are rows in your search criteria. When you get
the data all primary key fields will report null.
Software used:
- Orion1.0RC1 and RC2
- JDK1.3 Release
- Sybse 11.5.1 with stored procedure upgrade for 12.0 so JDBC works
properly
- JConnect 5.2 and 4.2
Bug:
Orion don't catch datatype mapping errors like char -> char(1) that
should be String -> char(1), and the result is hassardous and very hard to
find bugs.
Thanks for a great product so far, now im just waiting for network
deployment possability (hint hint) :)
Med vennlig hilsen
Klaus Myrseth
Senior system consultant
Exense ASA
