Hi Brian,
sounds strange, do you use the anonymous keys in a 1:1 or 1:n relation? Which version do you use? Have you tried latest from CVS?
Can you describe me detailed a test case to reproduce the problem?
regards, Armin
Brian Latimer wrote:
I have many persistent objects that contain references to other persistent objects.
I am fairly certain that I have the mapping set up properly, but, the auto-retrive doesn't seem to cascade down my objects if they use anonymous keys. That is unless I use proxies; in which case the objects get loaded correctly when methods are called. So I can get the results I want, but I don't necessarily want to use proxies.
Let's say for instance class A contains an instance of class B and B has an instance of class C.
If I do not use anonymous keys, but instead put the foreign keys in the classes, everything will auto-load when I call a getCollectionByCriteria(classA). Thus when I call a method on a class C contained within any given instance of class A from my collection everything works.
If I then change ONLY one thing, and add access="anonymous" to a foreign key field, the cascade seems to fail and class C will show up as null.
If I then again change ONLY one thing and add proxy="dynamic" to class A, the method call against class C will again function properly when called (as I would expect it to)
Is this the expected behavior, that anonymous keys do not auto-retrieve all the way in a collection, or should my anonymous keys auto-retrieve all the way down the class structure?
any help would be appreciated. If needed, I can post code and repository files, but I was hoping to describe the problem clearly enough to avoid that.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
