urgent 3 level Inheritance problem
Hi All, we have class A, Class B extends A and has a super reference-descriptor to A, Class C extends B and has a super reference-descriptor to B when we retrieve an instance of C and update a field which is part of A class it doesn't work. I debugged OJB source and found out this happens because the AnonymousPersistentFieldForInheritance stores the references objects (like B and A) in a Map leading that The currentImage and the beforeImage in ObjectEnvlope are the same. is it possible to configure OJB not to store the references in a Map. Thanks Ziv. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: urgent 3 level Inheritance problem
Ziv Yankowitz wrote: is it possible to configure OJB not to store the references in a Map. Without going into your detailed question; I think you should be able to work around any problems by implementing equals and hashCode in your beans such that instance of A.equals(instance of B) or instance of A.eqauls(instance of C) etc never returns true. Regards, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: urgent 3 level Inheritance problem
Thanks for the response, I tried to implement the hashCode and equals and it still doesn't work, somehow the beforeImage and the currentImage are working with the same instance of the AnonymousPersistentFieldForInheritance object in map. Thanks Ziv -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 2:39 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Ziv Yankowitz wrote: is it possible to configure OJB not to store the references in a Map. Without going into your detailed question; I think you should be able to work around any problems by implementing equals and hashCode in your beans such that instance of A.equals(instance of B) or instance of A.eqauls(instance of C) etc never returns true. Regards, Martin - 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]
Re: urgent 3 level Inheritance problem
Ziv Yankowitz wrote: I tried to implement the hashCode and equals and it still doesn't work, somehow the beforeImage and the currentImage are working with the same instance of the AnonymousPersistentFieldForInheritance object in map. Silly me. Since your beans are not the objects stored in the Map, your definition of equals() does not matter. Sorry to give you false hope. ;) I hope that Jakob or others can help you with some details re the OJB implementation in that area. Regards, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: urgent 3 level Inheritance problem
Hi Ziv, it's a known issue that odmg-api does not support mapping classes on multiple joined tables (see release notes). I will add some improvements to odmg-api today (hope so ;-)) which seems to solve the problems with inheritance (expect the one that is known in PB-api). regards, Armin Ziv Yankowitz wrote: Thanks for the response, I tried to implement the hashCode and equals and it still doesn't work, somehow the beforeImage and the currentImage are working with the same instance of the AnonymousPersistentFieldForInheritance object in map. Thanks Ziv -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 2:39 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Ziv Yankowitz wrote: is it possible to configure OJB not to store the references in a Map. Without going into your detailed question; I think you should be able to work around any problems by implementing equals and hashCode in your beans such that instance of A.equals(instance of B) or instance of A.eqauls(instance of C) etc never returns true. Regards, Martin - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: urgent 3 level Inheritance problem
Hi Armin, so is there a way to avoid the caching of references even in the cost of performance? Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 3:19 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Hi Ziv, it's a known issue that odmg-api does not support mapping classes on multiple joined tables (see release notes). I will add some improvements to odmg-api today (hope so ;-)) which seems to solve the problems with inheritance (expect the one that is known in PB-api). regards, Armin Ziv Yankowitz wrote: Thanks for the response, I tried to implement the hashCode and equals and it still doesn't work, somehow the beforeImage and the currentImage are working with the same instance of the AnonymousPersistentFieldForInheritance object in map. Thanks Ziv -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 2:39 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Ziv Yankowitz wrote: is it possible to configure OJB not to store the references in a Map. Without going into your detailed question; I think you should be able to work around any problems by implementing equals and hashCode in your beans such that instance of A.equals(instance of B) or instance of A.eqauls(instance of C) etc never returns true. Regards, Martin - 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] - 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]
Re: urgent 3 level Inheritance problem
Ziv Yankowitz wrote: Hi Armin, so is there a way to avoid the caching of references even in the cost of performance? think this is not possible, because the caching of the references is the character of the anonymous fields. Armin Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 3:19 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Hi Ziv, it's a known issue that odmg-api does not support mapping classes on multiple joined tables (see release notes). I will add some improvements to odmg-api today (hope so ;-)) which seems to solve the problems with inheritance (expect the one that is known in PB-api). regards, Armin Ziv Yankowitz wrote: Thanks for the response, I tried to implement the hashCode and equals and it still doesn't work, somehow the beforeImage and the currentImage are working with the same instance of the AnonymousPersistentFieldForInheritance object in map. Thanks Ziv -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 2:39 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Ziv Yankowitz wrote: is it possible to configure OJB not to store the references in a Map. Without going into your detailed question; I think you should be able to work around any problems by implementing equals and hashCode in your beans such that instance of A.equals(instance of B) or instance of A.eqauls(instance of C) etc never returns true. Regards, Martin - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: urgent 3 level Inheritance problem
one last question then, if in AnonymousPersistentField i comment the putToFieldCache every thing seems to be working well, would you recommend I do it. since we have also stress our application and it seems that the RefernceMap is not cleared leading to OutOfMemory in the end. Thanks A Lot Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 3:32 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Ziv Yankowitz wrote: Hi Armin, so is there a way to avoid the caching of references even in the cost of performance? think this is not possible, because the caching of the references is the character of the anonymous fields. Armin Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 3:19 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Hi Ziv, it's a known issue that odmg-api does not support mapping classes on multiple joined tables (see release notes). I will add some improvements to odmg-api today (hope so ;-)) which seems to solve the problems with inheritance (expect the one that is known in PB-api). regards, Armin Ziv Yankowitz wrote: Thanks for the response, I tried to implement the hashCode and equals and it still doesn't work, somehow the beforeImage and the currentImage are working with the same instance of the AnonymousPersistentFieldForInheritance object in map. Thanks Ziv -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 2:39 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Ziv Yankowitz wrote: is it possible to configure OJB not to store the references in a Map. Without going into your detailed question; I think you should be able to work around any problems by implementing equals and hashCode in your beans such that instance of A.equals(instance of B) or instance of A.eqauls(instance of C) etc never returns true. Regards, Martin - 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] - 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] - 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]
Re: urgent 3 level Inheritance problem
Ziv Yankowitz wrote: one last question then, if in AnonymousPersistentField i comment the putToFieldCache every thing seems to be working well, would you recommend I do it. If all your tests pass ... try it. But I recommend to write tests to verify your improvement (as starting point you can use the test in the OJB test-suite ...odmg.InheritanceMultipleTableTest). Your changes will cause problems when you serialize the object, in this I assume case all anonymous field info is lost. Armin since we have also stress our application and it seems that the RefernceMap is not cleared leading to OutOfMemory in the end. Thanks A Lot Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 3:32 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Ziv Yankowitz wrote: Hi Armin, so is there a way to avoid the caching of references even in the cost of performance? think this is not possible, because the caching of the references is the character of the anonymous fields. Armin Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 3:19 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Hi Ziv, it's a known issue that odmg-api does not support mapping classes on multiple joined tables (see release notes). I will add some improvements to odmg-api today (hope so ;-)) which seems to solve the problems with inheritance (expect the one that is known in PB-api). regards, Armin Ziv Yankowitz wrote: Thanks for the response, I tried to implement the hashCode and equals and it still doesn't work, somehow the beforeImage and the currentImage are working with the same instance of the AnonymousPersistentFieldForInheritance object in map. Thanks Ziv -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 2:39 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Ziv Yankowitz wrote: is it possible to configure OJB not to store the references in a Map. Without going into your detailed question; I think you should be able to work around any problems by implementing equals and hashCode in your beans such that instance of A.equals(instance of B) or instance of A.eqauls(instance of C) etc never returns true. Regards, Martin - 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] - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: urgent 3 level Inheritance problem
Armin Waibel wrote: Hi Ziv, it's a known issue that odmg-api does not support mapping classes on multiple joined tables (see release notes). I will add some improvements to odmg-api today (hope so ;-)) which seems to solve the problems with inheritance (expect the one that is known in PB-api). checked in the changes in OJB_1_0_RELEASE branch. Inheritance based on mapping classes on multiple joined tables is now working with the odmg-api (expect the known issue in PB-api - see release-notes). Armin regards, Armin Ziv Yankowitz wrote: Thanks for the response, I tried to implement the hashCode and equals and it still doesn't work, somehow the beforeImage and the currentImage are working with the same instance of the AnonymousPersistentFieldForInheritance object in map. Thanks Ziv -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 2:39 PM To: OJB Users List Subject: Re: urgent 3 level Inheritance problem Ziv Yankowitz wrote: is it possible to configure OJB not to store the references in a Map. Without going into your detailed question; I think you should be able to work around any problems by implementing equals and hashCode in your beans such that instance of A.equals(instance of B) or instance of A.eqauls(instance of C) etc never returns true. Regards, Martin - 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] - 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]
