Reference 1:1

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

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

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

Re: Reference 1:1

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

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

Re: Reference 1:1

://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

Re: Reference 1:1

: 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

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

Re: Reference 1:1

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

reference (1:1) and null

Hi! When retrieving a 1:1..0 mapping using proxies, after counting how many values has in the table, OJB should set the referenced object to NULL when counting is 0 (not setting the reference for a proxy that will give a NPE when trying to call a method). If the value set is a proxy (event if