OJB will be the default persistence model within Jetspeed 2 and all my current posts have been spawned by my implementing of OJB in Jetspeed 2. I recently converted the entire object model from Castor to OJB (still in progress). So, you will probably be seeing more posts from me in the near future;)
*===================================* * Scott T Weaver������������������� * * Jakarta Jetspeed Portal Project�� * * [EMAIL PROTECTED] * *===================================* � > -----Original Message----- > From: Thomas Mahler [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2003 1:47 AM > To: OJB Users List > Subject: Re: extents and mapping inheritence > > Hi Scott, > > Weaver, Scott wrote: > > Is there anyway I can remove the mapping for B entirely. It > > implements the interface AB and extends A. That should be good > > enough for OJB. However, when I try this, I get class B is not > > persistence capable. > > > > The reason I want to do this is B is a special case that may or may > > not be used and we would prefer to keep it out of the OJB mappings > > and rely entirely on dealing with AB and/or A. > > If you are using B instances you *must* provide a class-descriptor for > B. OJB prints out the message you see when you try to call persistence > operations on aclass that is not defined in the repository. > > Scott, I have one question regarding Jetspeed. I heared that there have > been discussions to use OJB within Jetspeed. > Are you working on this? Or do you anything about this topic? > > cheers, > Thomas > > > > > > > *===================================* * Scott T Weaver > > * * Jakarta Jetspeed Portal Project * * [EMAIL PROTECTED] > > * *===================================* > > > > > > > > > >> -----Original Message----- From: Weaver, Scott > >> [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2003 3:21 PM To: > >> 'OJB Users List' Subject: RE: extents and mapping inheritence > >> > >> Thanks Jakob. > >> > >> I Guess I'll have to use ENTITY references instead. Do you have > >> any other work-arounds I might try? > >> > >> Thanks again, *===================================* * Scott T > >> Weaver * * Jakarta Jetspeed Portal Project * * > >> [EMAIL PROTECTED] * > >> *===================================* > >> > >> > >> > >> > >>> -----Original Message----- From: Jakob Braeuchi > >>> [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2003 3:03 PM To: > >>> OJB Users List Subject: Re: extents and mapping inheritence > >>> > >>> hi scott, > >>> > >>> ojb does not support inheritence of field- and > >>> relationship-descriptors. but there are some discussions going on > >>> regarding this feature. > >>> > >>> hth jakob > >>> > >>> Weaver, Scott wrote: > >>> > >>> > >>>> Is there anyway to have a class-descriptor inherit the mappings > >>>> of a > >>> > >>> previously defined class-descriptor? > >>> > >>>> Example: > >>>> > >>>> AB is an interface. A implements AB and B extends A. > >>>> > >>>> <class-descriptor class="AB" > <extent-class class-ref="A" /> > >>>> <extent-class class-ref="B" /> </class-descriptor> > >>>> > >>>> > >>>> <class-descriptor class="A" table="AB"> <field-descriptor > >>>> name="id"column="ID" jdbc-type="INTEGER" primarykey="true" > >>>> autoincrement="true" /> <field-descriptor name="name" > >>>> column="NAME" jdbc-type="VARCHAR"/> </class-descriptor> > >>>> > >>>> The question: How can define the class-descriptor for B > >>>> without having > >>> > >>> to copy the identical mappings from A? > >>> > >>>> I tried using the "extends" attribute of class-descriptor on > >>>> hunch > >> > >> that's > >> > >>> what it was for, however, no dice. > >>> > >>>> There has got to be a simple way to accomplish this, however, I > >>>> have > >> > >> yet > >> > >>> to find it. > >>> > >>>> Using 1.0rc3. > >>>> > >>>> Thanks, *===================================* * Scott T Weaver > >>>> * * Jakarta Jetspeed Portal Project * * [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]
