Poor error message

Question

I've just fixed a mistake which would have been easier to spot with a
better error message.
I'm using kodo 2.2.4 with jboss-tomcat 2.4.4 and DB2 on Windows XP.
I have an object model which looks something like this:
ItemImpl contains a collection of AttributeImpl which contains a
collection of HistoryItem
My concrete classes are Letter, which extends ItemImpl, StringAttribute,
and CodeAttribute, which extend AttributeImpl, and StringHistoryItem and
CodeHistoryItem which extend HistoryItem.
My mistake was to forget to mention CodeAttribute in package.jdo.
The result was that jboss threw a transaction rollback exception on
commit, but with no explanatory error message at all.
Tom

Answer 1

Tom-
We do a lot of exception wrapping: did you try to call
JDOException.getNestedThrowables() and examine them? I am guessing that
there would be a decent error message in there somewhere.
Having to do this is a tedious process, but it will be solved when we
release our version that supports JDO 1.0 (JDO 1.0's JDOException class
automatically prints out all nested exceptions).
Tom Davies <[email protected]> wrote:
I've just fixed a mistake which would have been easier to spot with a
better error message.
I'm using kodo 2.2.4 with jboss-tomcat 2.4.4 and DB2 on Windows XP.
I have an object model which looks something like this:
ItemImpl contains a collection of AttributeImpl which contains a
collection of HistoryItem
My concrete classes are Letter, which extends ItemImpl, StringAttribute,
and CodeAttribute, which extend AttributeImpl, and StringHistoryItem and
CodeHistoryItem which extend HistoryItem.
My mistake was to forget to mention CodeAttribute in package.jdo.
The result was that jboss threw a transaction rollback exception on
commit, but with no explanatory error message at all.
Tom--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com
Kodo Java Data Objects Full featured JDO: eliminate the SQL from your code