Re: Reference 1:1
Hi Ziv, which version of OJB do you use? Which sequence-manager? regards, Armin Ziv Yankowitz wrote: Hi, I have a case where Class B extends A and B contains a reference descriptor with the following definition reference-descriptor name=super when I update fields in which belong to Class A on instance of type B they are not updated. from looking at the Ojb source I see in class ObjectEnvelope method markReferenceElements that only the Identity of the references object is compared and not the complete reference object, if I understand correctly the identity contains only the pk's. can someone please explain what can be done? Thanks Ziv. - 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: Reference 1:1
ojb version 1.0.3 about the serquence-manager we use org.apache.ojb.broker.util.sequence.SequenceManagerNextValImpl Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 4:10 PM To: OJB Users List Subject: Re: Reference 1:1 Hi Ziv, which version of OJB do you use? Which sequence-manager? regards, Armin Ziv Yankowitz wrote: Hi, I have a case where Class B extends A and B contains a reference descriptor with the following definition reference-descriptor name=super when I update fields in which belong to Class A on instance of type B they are not updated. from looking at the Ojb source I see in class ObjectEnvelope method markReferenceElements that only the Identity of the references object is compared and not the complete reference object, if I understand correctly the identity contains only the pk's. can someone please explain what can be done? Thanks Ziv. - 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: Reference 1:1
Ziv Yankowitz wrote: ojb version 1.0.3 about the serquence-manager we use org.apache.ojb.broker.util.sequence.SequenceManagerNextValImpl run some tests (..odmg.InheritanceMultipleTableTest) with SequenceManagerHighLowImpl the tests pass (expect one known issue), with SequenceManagerNextValImpl I got some additional errors. Created a bug report http://issues.apache.org/jira/browse/OJB-25 regards, Armin Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 4:10 PM To: OJB Users List Subject: Re: Reference 1:1 Hi Ziv, which version of OJB do you use? Which sequence-manager? regards, Armin Ziv Yankowitz wrote: Hi, I have a case where Class B extends A and B contains a reference descriptor with the following definition reference-descriptor name=super when I update fields in which belong to Class A on instance of type B they are not updated. from looking at the Ojb source I see in class ObjectEnvelope method markReferenceElements that only the Identity of the references object is compared and not the complete reference object, if I understand correctly the identity contains only the pk's. can someone please explain what can be done? Thanks Ziv. - 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: Reference 1:1
Did You encountered with the problem I'm describing and if so is there a way I can bypass the problem? Thanks Ziv -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 5:19 PM To: OJB Users List Subject: Re: Reference 1:1 Ziv Yankowitz wrote: ojb version 1.0.3 about the serquence-manager we use org.apache.ojb.broker.util.sequence.SequenceManagerNextValImpl run some tests (..odmg.InheritanceMultipleTableTest) with SequenceManagerHighLowImpl the tests pass (expect one known issue), with SequenceManagerNextValImpl I got some additional errors. Created a bug report http://issues.apache.org/jira/browse/OJB-25 regards, Armin Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 4:10 PM To: OJB Users List Subject: Re: Reference 1:1 Hi Ziv, which version of OJB do you use? Which sequence-manager? regards, Armin Ziv Yankowitz wrote: Hi, I have a case where Class B extends A and B contains a reference descriptor with the following definition reference-descriptor name=super when I update fields in which belong to Class A on instance of type B they are not updated. from looking at the Ojb source I see in class ObjectEnvelope method markReferenceElements that only the Identity of the references object is compared and not the complete reference object, if I understand correctly the identity contains only the pk's. can someone please explain what can be done? Thanks Ziv. - 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: Reference 1:1
Ziv Yankowitz wrote: Did You encountered with the problem I'm describing and if so is there a way I can bypass the problem? No, I detected a different problem caused by PK setting problems. With SequenceManagerHighLowImpl the update-test pass. Have a look at InheritanceMultipleTableTest. http://cvs.apache.org/viewcvs.cgi/db-ojb/src/test/org/apache/ojb/odmg/InheritanceMultipleTableTest.java?rev=1.1.2.4view=markup regards, Armin Thanks Ziv -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 5:19 PM To: OJB Users List Subject: Re: Reference 1:1 Ziv Yankowitz wrote: ojb version 1.0.3 about the serquence-manager we use org.apache.ojb.broker.util.sequence.SequenceManagerNextValImpl run some tests (..odmg.InheritanceMultipleTableTest) with SequenceManagerHighLowImpl the tests pass (expect one known issue), with SequenceManagerNextValImpl I got some additional errors. Created a bug report http://issues.apache.org/jira/browse/OJB-25 regards, Armin Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 4:10 PM To: OJB Users List Subject: Re: Reference 1:1 Hi Ziv, which version of OJB do you use? Which sequence-manager? regards, Armin Ziv Yankowitz wrote: Hi, I have a case where Class B extends A and B contains a reference descriptor with the following definition reference-descriptor name=super when I update fields in which belong to Class A on instance of type B they are not updated. from looking at the Ojb source I see in class ObjectEnvelope method markReferenceElements that only the Identity of the references object is compared and not the complete reference object, if I understand correctly the identity contains only the pk's. can someone please explain what can be done? Thanks Ziv. - 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: Reference 1:1
Ziv Yankowitz wrote: Did You encountered with the problem I'm describing and if so is there a way I can bypass the problem? Did you anything exotic (e.g. creation of class-descriptor at runtime)? Armin Thanks Ziv -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 5:19 PM To: OJB Users List Subject: Re: Reference 1:1 Ziv Yankowitz wrote: ojb version 1.0.3 about the serquence-manager we use org.apache.ojb.broker.util.sequence.SequenceManagerNextValImpl run some tests (..odmg.InheritanceMultipleTableTest) with SequenceManagerHighLowImpl the tests pass (expect one known issue), with SequenceManagerNextValImpl I got some additional errors. Created a bug report http://issues.apache.org/jira/browse/OJB-25 regards, Armin Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 4:10 PM To: OJB Users List Subject: Re: Reference 1:1 Hi Ziv, which version of OJB do you use? Which sequence-manager? regards, Armin Ziv Yankowitz wrote: Hi, I have a case where Class B extends A and B contains a reference descriptor with the following definition reference-descriptor name=super when I update fields in which belong to Class A on instance of type B they are not updated. from looking at the Ojb source I see in class ObjectEnvelope method markReferenceElements that only the Identity of the references object is compared and not the complete reference object, if I understand correctly the identity contains only the pk's. can someone please explain what can be done? Thanks Ziv. - 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: Reference 1:1
Yes we are creating class-descriptor at runtime, could this cause the problem? -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 5:49 PM To: OJB Users List Subject: Re: Reference 1:1 Ziv Yankowitz wrote: Did You encountered with the problem I'm describing and if so is there a way I can bypass the problem? Did you anything exotic (e.g. creation of class-descriptor at runtime)? Armin Thanks Ziv -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 5:19 PM To: OJB Users List Subject: Re: Reference 1:1 Ziv Yankowitz wrote: ojb version 1.0.3 about the serquence-manager we use org.apache.ojb.broker.util.sequence.SequenceManagerNextValImpl run some tests (..odmg.InheritanceMultipleTableTest) with SequenceManagerHighLowImpl the tests pass (expect one known issue), with SequenceManagerNextValImpl I got some additional errors. Created a bug report http://issues.apache.org/jira/browse/OJB-25 regards, Armin Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 4:10 PM To: OJB Users List Subject: Re: Reference 1:1 Hi Ziv, which version of OJB do you use? Which sequence-manager? regards, Armin Ziv Yankowitz wrote: Hi, I have a case where Class B extends A and B contains a reference descriptor with the following definition reference-descriptor name=super when I update fields in which belong to Class A on instance of type B they are not updated. from looking at the Ojb source I see in class ObjectEnvelope method markReferenceElements that only the Identity of the references object is compared and not the complete reference object, if I understand correctly the identity contains only the pk's. can someone please explain what can be done? Thanks Ziv. - 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: Reference 1:1
Ziv Yankowitz wrote: Yes we are creating class-descriptor at runtime, could this cause the problem? yep (if you add ClassDescriptor instances by hand), have a look in RepositoryXmlHandler#checkThis and #endDocument() methods. These intransparent methods do some needed initialization stuff. First I will try to move this methods to ClassDescriptor using lazy initialization at runtime, then I will try to fix the problem with different SequenceManager. regards, Armin -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 5:49 PM To: OJB Users List Subject: Re: Reference 1:1 Ziv Yankowitz wrote: Did You encountered with the problem I'm describing and if so is there a way I can bypass the problem? Did you anything exotic (e.g. creation of class-descriptor at runtime)? Armin Thanks Ziv -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 5:19 PM To: OJB Users List Subject: Re: Reference 1:1 Ziv Yankowitz wrote: ojb version 1.0.3 about the serquence-manager we use org.apache.ojb.broker.util.sequence.SequenceManagerNextValImpl run some tests (..odmg.InheritanceMultipleTableTest) with SequenceManagerHighLowImpl the tests pass (expect one known issue), with SequenceManagerNextValImpl I got some additional errors. Created a bug report http://issues.apache.org/jira/browse/OJB-25 regards, Armin Thanks Ziv. -Original Message- From: Armin Waibel [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 4:10 PM To: OJB Users List Subject: Re: Reference 1:1 Hi Ziv, which version of OJB do you use? Which sequence-manager? regards, Armin Ziv Yankowitz wrote: Hi, I have a case where Class B extends A and B contains a reference descriptor with the following definition reference-descriptor name=super when I update fields in which belong to Class A on instance of type B they are not updated. from looking at the Ojb source I see in class ObjectEnvelope method markReferenceElements that only the Identity of the references object is compared and not the complete reference object, if I understand correctly the identity contains only the pk's. can someone please explain what can be done? Thanks Ziv. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
