This one time, at band camp, Werner Guttmann said:
WG>I am a bit confused right now. Just using plain SQL, I can successfully verify that
WG>the foreign keys in the underlying table for the Account object are populated.
WG>
WG>I just had a look at the source code of ClassMolder.java, and that's what I found:
WG>
WG>// lazy loading for object (hollow object) is not support in
WG>// this version. Warns user if lazy loading is specified.
WG>if ( _fhs[i].isLazy() )
WG> System.err.println( "Warning: Lazy loading of object is not yet support!" );
WG>
WG>Could somebody please be so kind and explain to me what a *hollow* object is in this
WG>context ? As it looks that hgis might be the problem.
This is exactly where the exception is thrown. Like I said, I *think* a hollow
object is one that contains nothing possibly like so:
Foo foo;
Bar bar;
db.begin();
foo = new Foo();
foo.setId( 1 );
foo.setName( "Foo" );
bar = new Bar();
foo.setBar( bar );
db.create( foo );
db.commit();
This is only from memory, so I can't be sure this description is correct.
I'd like to see your client code and your mapping descriptor to see what
you're doing that is causing this exception to be thrown.
Also, the FAQ item I sent you yesterday is, in fact, incorrect. Just
yesterday I checked in an updated version of the JDO examples that
contains a working many-to-many relationship. The test is not complete,
it still needs to be cleaned up and the marshalling bug is not yet
fixed. At any rate, take a look at the example and compare it to what
you're trying to do.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
