objectbridge-developers — public list for developer issues

Re: [OJB-developers] Re: Problems with version 0.8.400

[David F. <dw...@la...>]

I've turned on the debugging, but don't see any problems there.  It appears 
to be some configuration problem of some kind.
If I take the same data and attempt to store it to the database after the 
failure, it stores it just fine.   I can store  other data
before this failure without any problem, so the difficulty is connected 
with something in the data that triggers a behavior
in OJB, but the next time I store the identical data, it works.     I'm not 
sure what to look for in the logging.  It is a
mystery to me as to why it works after the initial failure.

Dave
At 03:29 PM 5/17/2002 +0200, Thomas Mahler wrote:
>Hi David,
>
>Unfortunately I don't get enough information from the stacktrace to see 
>what's going wrong.
>
>can you please set the logging switches to debug on all loggers in 
>OJB.properties and provide me with a printout of the log. I hopeto get 
>more indepth information from that.
>
>cu,
>
>Thomas
>
>Matthew Baird wrote:
>
>>David,
>>I know it's a pain in the butt, but could you put together a test case that
>>shows the problem? If you do that and it's a bona fide bug, I'll add the
>>test case to the suite, and try to fix the bug. That way, you'll be
>>regression proof in the future.
>>Cheers,
>>Matthew
>>-----Original Message-----
>>From: David Forslund [mailto:dw...@la...] Sent: Thursday, May 16, 2002 
>>4:59 PM
>>To: obj...@li...
>>Subject: [OJB-developers] Re: Problems with version 0.8.400
>>I "upgraded" to version 0.8.400 but now have a problem I don't 
>>understand.  this was working fine with version 0.7.310.
>>There were a number of changes going to 400 but I don't see how they 
>>caused this behavior.  Several similar objects
>>were successfully stored in the database prior to this error, so it seems 
>>to be data dependent.
>>27129 [main] ERROR gov.lanl.Database.OJBDatabaseMgr  - insertElement: 
>>'gov.lanl.COAS.ObservationData
>>_@9e215b' name: 'null', error:
>>ojb.broker.PersistenceBrokerException
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
>>Impl.java:447)
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
>>305)
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
>>18)
>>          at 
>> gov.lanl.Database.OJBDatabaseMgr.insertElement(OJBDatabaseMgr.java:302)
>>          at 
>> gov.lanl.COAS.ObservationMgrImpl.add_observation(ObservationMgrImpl.java:648
>>)
>>          at 
>> gov.lanl.COAS.ObservationMgrImpl.<init>(ObservationMgrImpl.java:211)
>>          at 
>> gov.lanl.COAS.ObservationComponentImpl.init(ObservationComponentImpl.java:23
>>6)
>>          at 
>> gov.lanl.COAS.ObservationComponentImpl.main(ObservationComponentImpl.java:32
>>0)
>>Caused by: ojb.broker.PersistenceBrokerException
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
>>Impl.java:447)
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
>>305)
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
>>18)
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
>>Impl.java:438)
>>          ... 7 more
>>Caused by: ojb.broker.PersistenceBrokerException
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.storeReferences(PersistenceBrokerI
>>mpl.java:351)
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
>>303)
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
>>18)
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
>>Impl.java:438)
>>          ... 10 more
>>Caused by: java.lang.ArrayIndexOutOfBoundsException
>>          at
>>ojb.broker.accesslayer.JdbcAccess.getSqlTypePk(JdbcAccess.java:557)
>>          at 
>> ojb.broker.accesslayer.StatementManager.bindSelect(StatementManager.java:325
>>)
>>          at 
>> ojb.broker.accesslayer.JdbcAccess.materializeObject(JdbcAccess.java:326)
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
>>13)
>>          at 
>> ojb.broker.singlevm.PersistenceBrokerImpl.storeReferences(PersistenceBrokerI
>>mpl.java:344)
>>          ... 13 more
>>Any ideas?  Is it something to do with the cache?
>>Thanks,
>>Dave
>>
>>_______________________________________________________________
>>Have big pipes? SourceForge.net is looking for download mirrors. We supply
>>the hardware. You get the recognition. Email Us: ban...@so...
>>_______________________________________________
>>Objectbridge-developers mailing list
>>Obj...@li...
>>https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
>>_______________________________________________________________
>>Have big pipes? SourceForge.net is looking for download mirrors. We supply
>>the hardware. You get the recognition. Email Us: ban...@so...
>>_______________________________________________
>>Objectbridge-developers mailing list
>>Obj...@li...
>>https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
>>
>

Re: [REPOST] Re: [OJB-developers] Log4J subsystem beeing configured multiple times !

[Leandro R. S. C. <le...@ib...>]

On Fri, 2002-05-17 at 08:26, Thomas Mahler wrote:
> Hi Leandro,
> 
> I already answered this, but maybe it did not yet reach you
> 
> Leandro Rodrigo Saad Cruz wrote:
> 
> > On Wed, 2002-05-08 at 13:01, Leandro Rodrigo Saad Cruz wrote:
> > 
> >>Hi all.
> >>I noticed that Log4jLoggerImpl is configured for every Logger instance that it's
> >>created at LoggerFactory. Is it the intended behavior or can I change
> >>that and submit some patches to configure Log4J only once and use the
> >>same configuration for every instance of Log4JLoggerImpl ?
> 
> 
> feel free to change it this way! It's safe to sdo the config stuff only 
> once.

Ok.. I'll change that. I want to work on this next week or this weekend

> 
> cheers,
> 
> Thomas
> 
> 
> >>
> > 
> 
-- 
Leandro Rodrigo Saad Cruz
IT - Inter Business Tecnologia e Servicos (IB)
http://www.ibnetwork.com.br

Re: [OJB-developers] ojb in o'reilly book on struts

[Thomas M. <tho...@ho...>]

Hi Georg,

I did not know of this book. I just browsed through the chapter 6. I 
really like the presentation. I think they are following mostly the 
stuff Frido contributed in his using struts with OJB sample (to be found 
in the contrib package).

thanks for this interesting pointer,

Thomas

Georg Schneider wrote:

> Hi,
> 
> Maybe this is already known, but I thought I'd inform you:
> 
> There is a book coming out at O'Reilly about Jakarta Struts which is
> undergoing a public review process at theserverside.com, which means that
> chapters are downloadable for review as soon as they are finished.
> 
> There are already 6 chapters of the 21 planned available and the whole
> book evolves around one sample application, which will be some kind of
> shopping-cart application. The nice thing I found when reading chapter 6
> is that the author chose objectbridge as his persistence layer (ODMG Api)
> and goes into detail of how to integrate it into the application.
> 
> http://www.theserverside.com/resources/strutsreview.jsp?news3
> 
> Cheers
> 
> Georg
> 
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Objectbridge-developers mailing list
> Obj...@li...
> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
> 
> 
> 
> 

Re: [OJB-developers] Problems with "non-decomposed m:n-mappings"/ extents - has it been fixed?

[Jakob B. <jbr...@ho...>]

hi kim,

i cannot apply your patch, eclipse does not like it :(
please send me the complete file.
from what i can see sofar you get all pkFields from the class Descriptor and
then from there you go back to the ClassDescriptor to get the
table. i think you'll get the same table as many times as you have pkFields,
does this make sense ?

jakob

----- Original Message -----
From: "Kim Altintop" <ki...@de...>
To: "Jakob Braeuchi" <jbr...@ho...>;
<obj...@li...>
Sent: Friday, May 17, 2002 3:12 PM
Subject: Re: [OJB-developers] Problems with "non-decomposed m:n-mappings"/
extents - has it been fixed?


> Hi Jakob,
>
> unless I didn't check out the wrong branch (ojb-1-0) your fix IS included
> in .400. However, it didn't work out for me but - hooray! - I tracked it
> down: ojb.broker.singlevm.PersistenceBrokerImpl::getMtoNQuery is not
> accumulating table/field information correctly (i.e.,
> cld.getFullTableName() always returns null here).
>
> I made a small workaround which seems to do the job for me. Attached is
the
> patch - maybe you could check this and tell me if I'm right (I didn't run
> the test suite against this yet). I could supply a small test case that
> illustrates the issue if needed.
>
> Regards,
> Kim
>
>
> --On 5/17/2002 7:57 AM +0200 Jakob Braeuchi <jbr...@ho...> wrote:
>
> > hi kim,
> >
> > i made a quick fix for m:n with extents on May 3. and a fix for m:n path
> > expressions on May 8 but i think they are not in .400.
> >
> > jakob
> >
> > ----- Original Message -----
> > From: "Kim Altintop" <ki...@de...>
> > To: <obj...@li...>
> > Sent: Thursday, May 16, 2002 3:02 PM
> > Subject: [OJB-developers] Problems with "non-decomposed m:n-mappings"/
> > extents - has it been fixed?
> >
> >
> >> Hi all,
> >>
> >> while porting my app over to work with OJB I ran into the following
> > problem:
> >> if I got a CollectionDescriptor like this one
> >>
> >>  <CollectionDescriptor id="2">
> >>    <cdfield.name>foos</cdfield.name>
> >>    <items.class>MyFooInterface</items.class>
> >>    <inverse_fk_descriptor_ids>666</inverse_fk_descriptor_ids>
> >>    <indirection_table>aggregate2interface</indirection_table>
> >>
<fks_pointing_to_this_class>aggregate_id</fks_pointing_to_this_class>
> >>    <fks_pointing_to_items_class>foo_id</fks_pointing_to_items_class>
> >>  </CollectionDescriptor>
> >>
> >> where - as you can see - the items.class is pointing to an interface
> > (could
> >> as well be an abstract class), that is, a class is not itself mapped to
a
> >> table but solely consists of extent classes, OJB seems to have problems
> >> finding the correct table(s) for the extent classes (yes it DOES
realize
> >> that is has to look for extents). I believe that the problem is similar
> >> to the one described here:
> >>
> >> http://sourceforge.net/mailarchive/message.php?msg_id=1502546
> >>
> >> One reply to this post says that a "quick fix" has been submitted.
> > However,
> >> I couldn't get the .400 release to work ("[DEFAULT] ERROR:
> > FIELDDESCRIPTOR:
> >> Can't find member dMapId in ojb.odmg.collections.DMapEntry")...
> >>
> >> I'm now wondering if I should a) wait for the next release, b) pull my
> > hair
> >> out on getting .400 to work or c) fiddle around with a CVS version
> >> because the "quick fix" isn't applicable to my problem...?
> >>
> >> Thanks in advance for any directions!
> >>
> >> Kim
> >>
> >> _______________________________________________________________
> >>
> >> Have big pipes? SourceForge.net is looking for download mirrors. We
> >> supply the hardware. You get the recognition. Email Us:
> >> ban...@so...
_______________________________________________
> >> Objectbridge-developers mailing list
> >> Obj...@li...
> >> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
> >>
>
>

[OJB-developers] EqualToColumnCriteria an Aliases

[Jakob B. <jbr...@ho...>]

hi oleg,

we need a clear definition for EqualToColumnCriteria when used with aliases.
imho the table name must be replaced by the alias, but i think the column
name should stay untouched.

ie: PERSON.FIRSTNAME  -> Ax.FIRSTNAME

the current version of SqlManager also tries to translate the column name
and if it can't find a fielddescriptor it keeps the original name.
this leads to SqlExceptions because the table has an alias and the where
statement uses the table name:

SELECT DISTINCT
A0.id,A0.vorname,A0.name,A0.adresse,A0.gebDat,A0.test,A0.isBoss,A0.entryDate
,A0.idPartner FROM tabPerson A0 WHERE A0.id = tabPerson.id

the correct form of this really useless SQL should be:

... FROM tabPerson A0 WHERE A0.id = A0.id

maybe we need an EqualToFieldCriteria where both table and field name are
translated ?

jakob

Re: [OJB-developers] Re: Problems with version 0.8.400

[Thomas M. <tho...@ho...>]

Hi David,

Unfortunately I don't get enough information from the stacktrace to see 
what's going wrong.

can you please set the logging switches to debug on all loggers in 
OJB.properties and provide me with a printout of the log. I hopeto get 
more indepth information from that.

cu,

Thomas

Matthew Baird wrote:

> David,
> 
> I know it's a pain in the butt, but could you put together a test case that
> shows the problem? If you do that and it's a bona fide bug, I'll add the
> test case to the suite, and try to fix the bug. That way, you'll be
> regression proof in the future.
> 
> Cheers,
> Matthew
> 
> -----Original Message-----
> From: David Forslund [mailto:dw...@la...] 
> Sent: Thursday, May 16, 2002 4:59 PM
> To: obj...@li...
> Subject: [OJB-developers] Re: Problems with version 0.8.400
> 
> I "upgraded" to version 0.8.400 but now have a problem I don't 
> understand.  this was working fine with version 0.7.310.
> There were a number of changes going to 400 but I don't see how they caused 
> this behavior.  Several similar objects
> were successfully stored in the database prior to this error, so it seems 
> to be data dependent.
> 
> 27129 [main] ERROR gov.lanl.Database.OJBDatabaseMgr  - insertElement: 
> 'gov.lanl.COAS.ObservationData
> _@9e215b' name: 'null', error:
> ojb.broker.PersistenceBrokerException
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
> Impl.java:447)
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
> 305)
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
> 18)
>          at 
> gov.lanl.Database.OJBDatabaseMgr.insertElement(OJBDatabaseMgr.java:302)
>          at 
> gov.lanl.COAS.ObservationMgrImpl.add_observation(ObservationMgrImpl.java:648
> )
>          at 
> gov.lanl.COAS.ObservationMgrImpl.<init>(ObservationMgrImpl.java:211)
>          at 
> gov.lanl.COAS.ObservationComponentImpl.init(ObservationComponentImpl.java:23
> 6)
>          at 
> gov.lanl.COAS.ObservationComponentImpl.main(ObservationComponentImpl.java:32
> 0)
> Caused by: ojb.broker.PersistenceBrokerException
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
> Impl.java:447)
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
> 305)
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
> 18)
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
> Impl.java:438)
>          ... 7 more
> Caused by: ojb.broker.PersistenceBrokerException
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.storeReferences(PersistenceBrokerI
> mpl.java:351)
> 
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
> 303)
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
> 18)
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
> Impl.java:438)
>          ... 10 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException
>          at
> ojb.broker.accesslayer.JdbcAccess.getSqlTypePk(JdbcAccess.java:557)
>          at 
> ojb.broker.accesslayer.StatementManager.bindSelect(StatementManager.java:325
> )
>          at 
> ojb.broker.accesslayer.JdbcAccess.materializeObject(JdbcAccess.java:326)
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
> 13)
>          at 
> ojb.broker.singlevm.PersistenceBrokerImpl.storeReferences(PersistenceBrokerI
> mpl.java:344)
> 
>          ... 13 more
> 
> Any ideas?  Is it something to do with the cache?
> 
> Thanks,
> 
> Dave
> 
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Objectbridge-developers mailing list
> Obj...@li...
> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Objectbridge-developers mailing list
> Obj...@li...
> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
> 
> 
> 
> 

Re: [OJB-developers] Problems with "non-decomposed m:n-mappings"/ extents - has it been fixed?

[Kim A. <ki...@de...>]

Hi Jakob,

unless I didn't check out the wrong branch (ojb-1-0) your fix IS included
in .400. However, it didn't work out for me but - hooray! - I tracked it
down: ojb.broker.singlevm.PersistenceBrokerImpl::getMtoNQuery is not
accumulating table/field information correctly (i.e.,
cld.getFullTableName() always returns null here).

I made a small workaround which seems to do the job for me. Attached is the
patch - maybe you could check this and tell me if I'm right (I didn't run
the test suite against this yet). I could supply a small test case that
illustrates the issue if needed.

Regards,
Kim


--On 5/17/2002 7:57 AM +0200 Jakob Braeuchi <jbr...@ho...> wrote:

> hi kim,
> 
> i made a quick fix for m:n with extents on May 3. and a fix for m:n path
> expressions on May 8 but i think they are not in .400.
> 
> jakob
> 
> ----- Original Message -----
> From: "Kim Altintop" <ki...@de...>
> To: <obj...@li...>
> Sent: Thursday, May 16, 2002 3:02 PM
> Subject: [OJB-developers] Problems with "non-decomposed m:n-mappings"/
> extents - has it been fixed?
> 
> 
>> Hi all,
>> 
>> while porting my app over to work with OJB I ran into the following
> problem:
>> if I got a CollectionDescriptor like this one
>> 
>>  <CollectionDescriptor id="2">
>>    <cdfield.name>foos</cdfield.name>
>>    <items.class>MyFooInterface</items.class>
>>    <inverse_fk_descriptor_ids>666</inverse_fk_descriptor_ids>
>>    <indirection_table>aggregate2interface</indirection_table>
>>    <fks_pointing_to_this_class>aggregate_id</fks_pointing_to_this_class>
>>    <fks_pointing_to_items_class>foo_id</fks_pointing_to_items_class>
>>  </CollectionDescriptor>
>> 
>> where - as you can see - the items.class is pointing to an interface
> (could
>> as well be an abstract class), that is, a class is not itself mapped to a
>> table but solely consists of extent classes, OJB seems to have problems
>> finding the correct table(s) for the extent classes (yes it DOES realize
>> that is has to look for extents). I believe that the problem is similar
>> to the one described here:
>> 
>> http://sourceforge.net/mailarchive/message.php?msg_id=1502546
>> 
>> One reply to this post says that a "quick fix" has been submitted.
> However,
>> I couldn't get the .400 release to work ("[DEFAULT] ERROR:
> FIELDDESCRIPTOR:
>> Can't find member dMapId in ojb.odmg.collections.DMapEntry")...
>> 
>> I'm now wondering if I should a) wait for the next release, b) pull my
> hair
>> out on getting .400 to work or c) fiddle around with a CVS version
>> because the "quick fix" isn't applicable to my problem...?
>> 
>> Thanks in advance for any directions!
>> 
>> Kim
>> 
>> _______________________________________________________________
>> 
>> Have big pipes? SourceForge.net is looking for download mirrors. We
>> supply the hardware. You get the recognition. Email Us:
>> ban...@so... _______________________________________________
>> Objectbridge-developers mailing list
>> Obj...@li...
>> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
>> 

Re: [OJB-developers] PersistenceBrokerServlet again

[Thomas M. <tho...@ho...>]

Hi Joachim,

Joa...@tp... wrote:

> Hy,
> 
> it's me again. I've just finished the first version of the 
> PersistenceBrokerServlet that passes all JUnit tests.


fine !

> It still stumble 
> sometimes (have to take a closer look at that), but it works. Now I'm 
> searching for anyone who is willing to experiment with OJB running via a 
> HTTP connection. 


I'll give it a try!

Setup on the OJB-side is easy (just use 
> http://server/path/servlet instead of server\:2001 for servers in 
> OJB.properties), the Servlet-part not so (no documentation yet, but anyone 
> who worked with servlets before should be able to work it out). I dont 
> want to check this in, until someone tried it and tells me that it doesn't 
> detonate his computer and doesn't turn his neighbours into aliens as well 
> (take a close look at that last one, I got some suspicious code in there).


don't be shy! I'm always checkin in untested and suspicious code ;-)

 
> The attached zip file contains all java files that I changed and should be 
> unziped into src/java of a current CVS-version of OJB.
> 
> btw, it seems that I'm the only one who is working on the C/S-part of OJB,


The last thing I did, was building a ServerConsole that can be used for 
remote administration of a OJB server. But I did not work on the 
internals for quite some time.

 
> is noone using this feature?


AFAIK most people are using the singlevm mode only. For most scenarios 
this will be sufficient.

> I think it'd need some redesign. I think that 
> it wouldn't be necessary to parse the repository on both the client and 
> the server, as the clients fetches quite some info from the server (as an 
> alternative we could find a way how to let both parse it and just assume 
> that the other side knows the same as we do).


Mhh, I once removed all references to DescriptorRepository from 
PersistenceBroker client. AFAIK there is no reading of the repository on 
the client side. That's why I introduced methods like 
getDescriptorFor(Class c) into the PB interface!

If the repository *is* parsed on the client it is a bug !!!

> I don't really feel 
> comfortable to approach such a redesign without someone to check my ideas 
> for sanity 


feel free to discuss any further issues regarding c/s mode directly with me.

>( I got no problems withing living with my design-decisions, 
> but I want others to find it useable as well ;-)
>


cheers,

Thomas

 
> regards
> Joachim Sauer
> 
> 

[OJB-developers] ojb in o'reilly book on struts

[Georg S. <ge...@me...>]

Hi,

Maybe this is already known, but I thought I'd inform you:

There is a book coming out at O'Reilly about Jakarta Struts which is
undergoing a public review process at theserverside.com, which means that
chapters are downloadable for review as soon as they are finished.

There are already 6 chapters of the 21 planned available and the whole
book evolves around one sample application, which will be some kind of
shopping-cart application. The nice thing I found when reading chapter 6
is that the author chose objectbridge as his persistence layer (ODMG Api)
and goes into detail of how to integrate it into the application.

http://www.theserverside.com/resources/strutsreview.jsp?news3

Cheers

Georg

Re: [OJB-developers] Problem with java.util.List not being stored.

[Thomas M. <tho...@ho...>]

Hi travis,


tr...@th... wrote:

> I'm having a problem with a List I have in one of my classes, not being stored to the db.  I just modified the tutorial app adding a List to the Product class.  And a new Use case to add things to that list. 
> 
> When I do it and then list the products, the access rights are stored in the object, and i assume this is because the object is cached.  But when close the app and open it again, the List data is gone.  
> 
> Has anyone had this issue before.  I've set it up in repository_user.xml as this.
> 
> <CollectionDescriptor id="11">
>          <cdfield.name>accesses</cdfield.name>
>          <items.class>com.spaceprogram.users.UserItemAccess</items.class>
>          <inverse_fk_descriptor_ids>4</inverse_fk_descriptor_ids>
>       </CollectionDescriptor>
> 
> But still no saves.  


If you are using the PersistenceBroker API (and not the ODMG API!) you 
have to tell the broker to perform cascading updates and deletes for 
associations.

You'll find the required settings for you CollectionDescriptor in 
tutorial3.html !!!

HTH,

Thomas


> 
> I've even added another use case that just queries all UserItemAccess and lists those, but nothing comes up.  That's why i assume that it's not being stored.  Any help would be appreciated.
> 
> Travis 
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Objectbridge-developers mailing list
> Obj...@li...
> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
> 
> 
> 
> 

[OJB-developers] Build: can't select database

[Jakob B. <jbr...@ho...>]

hi,

i'm trying to setup ojb for msaccess and i enabled msaccess in =
build.properties.
but whenever i start buil prepare-testdb it always uses hsqldb.

...
D:\Java\eclipse_0502\workspace\ojb-1-0>build prepare-testdb
Buildfile: build.xml

prepare-testdb:

project-sql-classpath:
     [echo] +------------------------------------------+
     [echo] |                                          |
     [echo] | Generating SQL for YOUR Turbine project! |
     [echo] | Woo hoo!                                 |
     [echo] |                                          |
     [echo] +------------------------------------------+
[torque-sql] Using contextProperties file: =
D:\Java\eclipse_0502\workspace\ojb-1-0\build.properties
[torque-sql] Using classpath
[torque-sql] Generating to file =
D:\Java\eclipse_0502\workspace\ojb-1-0\target\src\sql\report.ojbtest.sql.=
generation
[torque-sql] Resolver: used database.dtd from =
org.apache.torque.engine.database.transform package
[torque-sql] Resolver: used database.dtd from =
org.apache.torque.engine.database.transform package
[torque-sql] Resolver: used database.dtd from =
org.apache.torque.engine.database.transform package
[torque-sql] Resolver: used database.dtd from =
org.apache.torque.engine.database.transform package

project-create-db-classpath:
     [echo]
      driver=3D"org.hsqldb.jdbcDriver"
      url=3D"jdbc:hsqldb:target/test/OJB"
      userid=3D"sa"
      password=3D""

[torque-create-db] Using classpath
[torque-create-db] Generating to file =
D:\Java\eclipse_0502\workspace\ojb-1-0\target\src\sql\create-db.sql
....

what's wrong ?

jakob

[OJB-developers] MSAccess problem with multiple non nested joins

[Jakob B. <jbr...@ho...>]

hi oleg,

msaccess has a problem with multiple non nested joins without parentheses:

this query has two NOT NESTED joins, one to tabKonto the other to
tabTelefon:

SELECT DISTINCT
A0.id,A0.vorname,A0.name,A0.adresse,A0.gebDat,A0.test,A0.isBoss,A0.entryDate
,A0.idPartner,A2.tel_nr FROM tabPerson A0 INNER JOIN tabTelefon A2 ON
A0.id=A2.idPerson INNER JOIN tabKonto A1 ON A0.id=A1.idPerson WHERE
(A1.saldo>?) AND A2.tel_nr LIKE ? ORDER BY 10

msaccess can not handle this (Syntax error) , because it needs parentheses
around the first join:
[Microsoft][ODBC Microsoft Access Driver] Syntaxfehler (fehlender Operator)
in Abfrageausdruck 'A0.id=A2.idPerson INNER JOIN tabKonto A1 ON
A0.id=A1.idPerson'.

SELECT DISTINCT
A0.id,A0.vorname,A0.name,A0.adresse,A0.gebDat,A0.test,A0.isBoss,A0.entryDate
,A0.idPartner,A2.tel_nr FROM (tabPerson A0 INNER JOIN tabTelefon A2 ON
A0.id=A2.idPerson) INNER JOIN tabKonto A1 ON A0.id=A1.idPerson WHERE
(A1.saldo>?) AND A2.tel_nr LIKE ? ORDER BY 10

NESTED joins are handled correctly by msaccess! this query has a join from
tabKonto to tabPerson and then to tabTelefon:

SELECT DISTINCT A0.id,A0.idPerson,A0.nummer,A0.saldo FROM tabKonto A0 INNER
JOIN (tabPerson A1 INNER JOIN tabTelefon A2 ON A1.id=A2.idPerson) ON
A0.idPerson=A1.id WHERE A2.tel_nr LIKE ?

greetings jakob

Re: [OJB-developers] Problems with "non-decomposed m:n-mappings"/ extents - has it been fixed?

[Jakob B. <jbr...@ho...>]

hi kim,

i made a quick fix for m:n with extents on May 3. and a fix for m:n path
expressions on May 8 but i think they are not in .400.

jakob

----- Original Message -----
From: "Kim Altintop" <ki...@de...>
To: <obj...@li...>
Sent: Thursday, May 16, 2002 3:02 PM
Subject: [OJB-developers] Problems with "non-decomposed m:n-mappings"/
extents - has it been fixed?


> Hi all,
>
> while porting my app over to work with OJB I ran into the following
problem:
> if I got a CollectionDescriptor like this one
>
>  <CollectionDescriptor id="2">
>    <cdfield.name>foos</cdfield.name>
>    <items.class>MyFooInterface</items.class>
>    <inverse_fk_descriptor_ids>666</inverse_fk_descriptor_ids>
>    <indirection_table>aggregate2interface</indirection_table>
>    <fks_pointing_to_this_class>aggregate_id</fks_pointing_to_this_class>
>    <fks_pointing_to_items_class>foo_id</fks_pointing_to_items_class>
>  </CollectionDescriptor>
>
> where - as you can see - the items.class is pointing to an interface
(could
> as well be an abstract class), that is, a class is not itself mapped to a
> table but solely consists of extent classes, OJB seems to have problems
> finding the correct table(s) for the extent classes (yes it DOES realize
> that is has to look for extents). I believe that the problem is similar to
> the one described here:
>
> http://sourceforge.net/mailarchive/message.php?msg_id=1502546
>
> One reply to this post says that a "quick fix" has been submitted.
However,
> I couldn't get the .400 release to work ("[DEFAULT] ERROR:
FIELDDESCRIPTOR:
> Can't find member dMapId in ojb.odmg.collections.DMapEntry")...
>
> I'm now wondering if I should a) wait for the next release, b) pull my
hair
> out on getting .400 to work or c) fiddle around with a CVS version because
> the "quick fix" isn't applicable to my problem...?
>
> Thanks in advance for any directions!
>
> Kim
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Objectbridge-developers mailing list
> Obj...@li...
> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
>

[OJB-developers] Problem with java.util.List not being stored.

[<tr...@th...>]

I'm having a problem with a List I have in one of my classes, not being stored to the db.  I just modified the tutorial app adding a List to the Product class.  And a new Use case to add things to that list. 

When I do it and then list the products, the access rights are stored in the object, and i assume this is because the object is cached.  But when close the app and open it again, the List data is gone.  

Has anyone had this issue before.  I've set it up in repository_user.xml as this.

<CollectionDescriptor id="11">
         <cdfield.name>accesses</cdfield.name>
         <items.class>com.spaceprogram.users.UserItemAccess</items.class>
         <inverse_fk_descriptor_ids>4</inverse_fk_descriptor_ids>
      </CollectionDescriptor>

But still no saves.  

I've even added another use case that just queries all UserItemAccess and lists those, but nothing comes up.  That's why i assume that it's not being stored.  Any help would be appreciated.

Travis 

RE: [OJB-developers] Re: Problems with version 0.8.400

[David F. <dw...@la...>]

The test I'm seeing it in is fairly complicated so it isn't easy to isolate 
to a test.  I don't
even know if it is a bug.  I was hoping the tracebacks might shed a clue as 
to where to look.

Thanks,

Dave
At 05:52 PM 5/16/2002 -0700, Matthew Baird wrote:
>David,
>
>I know it's a pain in the butt, but could you put together a test case that
>shows the problem? If you do that and it's a bona fide bug, I'll add the
>test case to the suite, and try to fix the bug. That way, you'll be
>regression proof in the future.
>
>Cheers,
>Matthew
>
>-----Original Message-----
>From: David Forslund [mailto:dw...@la...]
>Sent: Thursday, May 16, 2002 4:59 PM
>To: obj...@li...
>Subject: [OJB-developers] Re: Problems with version 0.8.400
>
>I "upgraded" to version 0.8.400 but now have a problem I don't
>understand.  this was working fine with version 0.7.310.
>There were a number of changes going to 400 but I don't see how they caused
>this behavior.  Several similar objects
>were successfully stored in the database prior to this error, so it seems
>to be data dependent.
>
>27129 [main] ERROR gov.lanl.Database.OJBDatabaseMgr  - insertElement:
>'gov.lanl.COAS.ObservationData
>_@9e215b' name: 'null', error:
>ojb.broker.PersistenceBrokerException
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
>Impl.java:447)
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
>305)
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
>18)
>          at
>gov.lanl.Database.OJBDatabaseMgr.insertElement(OJBDatabaseMgr.java:302)
>          at
>gov.lanl.COAS.ObservationMgrImpl.add_observation(ObservationMgrImpl.java:648
>)
>          at
>gov.lanl.COAS.ObservationMgrImpl.<init>(ObservationMgrImpl.java:211)
>          at
>gov.lanl.COAS.ObservationComponentImpl.init(ObservationComponentImpl.java:23
>6)
>          at
>gov.lanl.COAS.ObservationComponentImpl.main(ObservationComponentImpl.java:32
>0)
>Caused by: ojb.broker.PersistenceBrokerException
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
>Impl.java:447)
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
>305)
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
>18)
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
>Impl.java:438)
>          ... 7 more
>Caused by: ojb.broker.PersistenceBrokerException
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.storeReferences(PersistenceBrokerI
>mpl.java:351)
>
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
>303)
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
>18)
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
>Impl.java:438)
>          ... 10 more
>Caused by: java.lang.ArrayIndexOutOfBoundsException
>          at
>ojb.broker.accesslayer.JdbcAccess.getSqlTypePk(JdbcAccess.java:557)
>          at
>ojb.broker.accesslayer.StatementManager.bindSelect(StatementManager.java:325
>)
>          at
>ojb.broker.accesslayer.JdbcAccess.materializeObject(JdbcAccess.java:326)
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
>13)
>          at
>ojb.broker.singlevm.PersistenceBrokerImpl.storeReferences(PersistenceBrokerI
>mpl.java:344)
>
>          ... 13 more
>
>Any ideas?  Is it something to do with the cache?
>
>Thanks,
>
>Dave
>
>
>_______________________________________________________________
>
>Have big pipes? SourceForge.net is looking for download mirrors. We supply
>the hardware. You get the recognition. Email Us: ban...@so...
>_______________________________________________
>Objectbridge-developers mailing list
>Obj...@li...
>https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
>
>_______________________________________________________________
>
>Have big pipes? SourceForge.net is looking for download mirrors. We supply
>the hardware. You get the recognition. Email Us: ban...@so...
>_______________________________________________
>Objectbridge-developers mailing list
>Obj...@li...
>https://lists.sourceforge.net/lists/listinfo/objectbridge-developers

RE: [OJB-developers] Re: Problems with version 0.8.400

[Matthew B. <ma...@so...>]

David,

I know it's a pain in the butt, but could you put together a test case that
shows the problem? If you do that and it's a bona fide bug, I'll add the
test case to the suite, and try to fix the bug. That way, you'll be
regression proof in the future.

Cheers,
Matthew

-----Original Message-----
From: David Forslund [mailto:dw...@la...] 
Sent: Thursday, May 16, 2002 4:59 PM
To: obj...@li...
Subject: [OJB-developers] Re: Problems with version 0.8.400

I "upgraded" to version 0.8.400 but now have a problem I don't 
understand.  this was working fine with version 0.7.310.
There were a number of changes going to 400 but I don't see how they caused 
this behavior.  Several similar objects
were successfully stored in the database prior to this error, so it seems 
to be data dependent.

27129 [main] ERROR gov.lanl.Database.OJBDatabaseMgr  - insertElement: 
'gov.lanl.COAS.ObservationData
_@9e215b' name: 'null', error:
ojb.broker.PersistenceBrokerException
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
Impl.java:447)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
305)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
18)
         at 
gov.lanl.Database.OJBDatabaseMgr.insertElement(OJBDatabaseMgr.java:302)
         at 
gov.lanl.COAS.ObservationMgrImpl.add_observation(ObservationMgrImpl.java:648
)
         at 
gov.lanl.COAS.ObservationMgrImpl.<init>(ObservationMgrImpl.java:211)
         at 
gov.lanl.COAS.ObservationComponentImpl.init(ObservationComponentImpl.java:23
6)
         at 
gov.lanl.COAS.ObservationComponentImpl.main(ObservationComponentImpl.java:32
0)
Caused by: ojb.broker.PersistenceBrokerException
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
Impl.java:447)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
305)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
18)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
Impl.java:438)
         ... 7 more
Caused by: ojb.broker.PersistenceBrokerException
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeReferences(PersistenceBrokerI
mpl.java:351)

         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1
303)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
18)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBroker
Impl.java:438)
         ... 10 more
Caused by: java.lang.ArrayIndexOutOfBoundsException
         at
ojb.broker.accesslayer.JdbcAccess.getSqlTypePk(JdbcAccess.java:557)
         at 
ojb.broker.accesslayer.StatementManager.bindSelect(StatementManager.java:325
)
         at 
ojb.broker.accesslayer.JdbcAccess.materializeObject(JdbcAccess.java:326)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:3
13)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeReferences(PersistenceBrokerI
mpl.java:344)

         ... 13 more

Any ideas?  Is it something to do with the cache?

Thanks,

Dave


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: ban...@so...
_______________________________________________
Objectbridge-developers mailing list
Obj...@li...
https://lists.sourceforge.net/lists/listinfo/objectbridge-developers

[OJB-developers] Re: Problems with version 0.8.400

[David F. <dw...@la...>]

I "upgraded" to version 0.8.400 but now have a problem I don't 
understand.  this was working fine with version 0.7.310.
There were a number of changes going to 400 but I don't see how they caused 
this behavior.  Several similar objects
were successfully stored in the database prior to this error, so it seems 
to be data dependent.

27129 [main] ERROR gov.lanl.Database.OJBDatabaseMgr  - insertElement: 
'gov.lanl.COAS.ObservationData
_@9e215b' name: 'null', error:
ojb.broker.PersistenceBrokerException
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBrokerImpl.java:447)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1305)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:318)
         at 
gov.lanl.Database.OJBDatabaseMgr.insertElement(OJBDatabaseMgr.java:302)
         at 
gov.lanl.COAS.ObservationMgrImpl.add_observation(ObservationMgrImpl.java:648)
         at 
gov.lanl.COAS.ObservationMgrImpl.<init>(ObservationMgrImpl.java:211)
         at 
gov.lanl.COAS.ObservationComponentImpl.init(ObservationComponentImpl.java:236)
         at 
gov.lanl.COAS.ObservationComponentImpl.main(ObservationComponentImpl.java:320)
Caused by: ojb.broker.PersistenceBrokerException
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBrokerImpl.java:447)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1305)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:318)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBrokerImpl.java:438)
         ... 7 more
Caused by: ojb.broker.PersistenceBrokerException
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeReferences(PersistenceBrokerImpl.java:351)

         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:1303)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:318)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeCollections(PersistenceBrokerImpl.java:438)
         ... 10 more
Caused by: java.lang.ArrayIndexOutOfBoundsException
         at ojb.broker.accesslayer.JdbcAccess.getSqlTypePk(JdbcAccess.java:557)
         at 
ojb.broker.accesslayer.StatementManager.bindSelect(StatementManager.java:325)
         at 
ojb.broker.accesslayer.JdbcAccess.materializeObject(JdbcAccess.java:326)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java:313)
         at 
ojb.broker.singlevm.PersistenceBrokerImpl.storeReferences(PersistenceBrokerImpl.java:344)

         ... 13 more

Any ideas?  Is it something to do with the cache?

Thanks,

Dave

[OJB-developers] Re: SqlStatement

[Oleg N. <on...@uk...>]

Hi Jakob,

On Thursday 16 May 2002 08:52, Jakob Braeuchi wrote:
> i have a problem with ms-access (to support it is an ojb feature) and joins
> using the current version of SqlStatement.
>
> SELECT DISTINCT A0.id,A0.idPerson,A0.nummer,A0.saldo FROM tabKonto A0 INNER
> JOIN tabPerson A1 ON A0.idPerson=A1.id INNER JOIN tabTelefon A2 ON
> A1.id=A2.idPerson WHERE (A0.saldo>?) AND A2.tel_nr LIKE ?
>
> this is perfect for mysql but ms-access needs ( ) around nested joins :
>
> SELECT DISTINCT A0.id,A0.idPerson,A0.nummer,A0.saldo FROM (tabKonto A0
> INNER JOIN tabPerson A1 ON A0.idPerson=A1.id) INNER JOIN tabTelefon A2 ON
> A1.id=A2.idPerson WHERE (A0.saldo>?) AND A2.tel_nr LIKE ?
>
> i've attached a fixed SqlStatement that works with mysql and ms-access, but
> i've NOT tested it with hsql and others.
> could you please have a look at it ?
The way you insert parenthesis doesn't look natural for me, 
it doesn't express the tree structure of joins :)
I'd prefer to return to the original way and to use join syntax without 
parenthesis for HSQL and MySQL only. 
I've committed my verion. Please, let me know what you think.

> when tryinig to understand your code, i saw that you make heavy use of
> instance variables.
> this is undoubtably perfect for performance, but i think it will complicate
> future refactorings.
> i prefer parameter passing (ie: for stmt in appendTableWithJoins()  ).
I agree, actually I usually prefer to use parameter passing and I tell to 
others the same things that you told to me :)
And BTW I am not sure that instance variables are better for performance :)
I just tried to make the source code as simple as possible.
I will remove several instance variables.

Thanks,
 Oleg

RE: [OJB-developers] Problems with "non-decomposed m:n-mappings"/ extents - has it been fixed?

[Matthew B. <ma...@so...>]

So the dMapId isn't javabean conformant because (looking at the code) they
check if the second character is an upper case, and then decide whether or
not to change the case, so as to not mess up things like UUID or JCA. I'm
not sure I have a better solution :)

It is, however on my list of things to fix. Probably a week from now.

I think the default reply is to the person directly instead of the list, no
deep secret.

Cheers,
Matthew

-----Original Message-----
From: Kim Altintop [mailto:ki...@de...] 
Sent: Thursday, May 16, 2002 9:57 AM
To: Matthew Baird
Subject: RE: [OJB-developers] Problems with "non-decomposed m:n-mappings"/
extents - has it been fixed?

Hi Matthew,

thanks for replying.
You're (kind of) right: after configuring OJB to use the
PersistentFieldPropertyImpl (wasn't able to use this with the .375), .400
seems to work (kind of). However, there is still an error when OJB starts
up:

[DEFAULT] ERROR: did not find property ojb.odmg.collections.DMapEntry.dMapId

but it seems as if OJB doesn't care...
Btw.: why do you think dMapId isn't javabeans comformant? Is it because it
starts with only _one_ lowercase letter?

Anyway, I could work out that my problem wasn't solved with .400 - I hope
that I can figure out what exactly is going wrong and then post a bug
report.

Thank you!

Kim
P.S.: I'm wondering why you guys always reply to me personally instead of
replying to the list. Any deeper secret behind this? ;-)


--On 5/16/2002 8:23 AM -0700 Matthew Baird <ma...@so...>
wrote:

> Kim, are you using getters and setters for mapping rather than mapping to
> the direct field?
> 
> If so, dMapId is not a javabean conformant name.
> 
> I can fix this, but I'm not sure it's your problem.

[OJB-developers] Problems with "non-decomposed m:n-mappings"/ extents - has it been fixed?

[Kim A. <ki...@de...>]

Hi all,

while porting my app over to work with OJB I ran into the following problem:
if I got a CollectionDescriptor like this one

 <CollectionDescriptor id="2">
   <cdfield.name>foos</cdfield.name>
   <items.class>MyFooInterface</items.class>
   <inverse_fk_descriptor_ids>666</inverse_fk_descriptor_ids>
   <indirection_table>aggregate2interface</indirection_table>
   <fks_pointing_to_this_class>aggregate_id</fks_pointing_to_this_class>
   <fks_pointing_to_items_class>foo_id</fks_pointing_to_items_class>
 </CollectionDescriptor>

where - as you can see - the items.class is pointing to an interface (could
as well be an abstract class), that is, a class is not itself mapped to a
table but solely consists of extent classes, OJB seems to have problems
finding the correct table(s) for the extent classes (yes it DOES realize
that is has to look for extents). I believe that the problem is similar to
the one described here:

http://sourceforge.net/mailarchive/message.php?msg_id=1502546

One reply to this post says that a "quick fix" has been submitted. However,
I couldn't get the .400 release to work ("[DEFAULT] ERROR: FIELDDESCRIPTOR:
Can't find member dMapId in ojb.odmg.collections.DMapEntry")...

I'm now wondering if I should a) wait for the next release, b) pull my hair
out on getting .400 to work or c) fiddle around with a CVS version because
the "quick fix" isn't applicable to my problem...?

Thanks in advance for any directions!

Kim

[OJB-developers] reversedb uses jakarta-regexp instead of gnu-regexp

[Florian B. <bf...@fl...>]

Hi,

just modified reversedb to use jakarta-regexp instead of gnu-regexp. There
are no other references to the gnu-regexp library other than from reversedb,
so I am going to remove this library from CVS.

I'm going to change the license header in the reversedb package now.

best regards,
Florian

[OJB-developers] SqlStatement

[Jakob B. <jbr...@ho...>]

hi oleg,

i have a problem with ms-access (to support it is an ojb feature) and joins
using the current version of SqlStatement.

SELECT DISTINCT A0.id,A0.idPerson,A0.nummer,A0.saldo FROM tabKonto A0 INNER
JOIN tabPerson A1 ON A0.idPerson=A1.id INNER JOIN tabTelefon A2 ON
A1.id=A2.idPerson WHERE (A0.saldo>?) AND A2.tel_nr LIKE ?

this is perfect for mysql but ms-access needs ( ) around nested joins :

SELECT DISTINCT A0.id,A0.idPerson,A0.nummer,A0.saldo FROM (tabKonto A0 INNER
JOIN tabPerson A1 ON A0.idPerson=A1.id) INNER JOIN tabTelefon A2 ON
A1.id=A2.idPerson WHERE (A0.saldo>?) AND A2.tel_nr LIKE ?

i've attached a fixed SqlStatement that works with mysql and ms-access, but
i've NOT tested it with hsql and others.
could you please have a look at it ?

when tryinig to understand your code, i saw that you make heavy use of
instance variables.
this is undoubtably perfect for performance, but i think it will complicate
future refactorings.
i prefer parameter passing (ie: for stmt in appendTableWithJoins()  ).
just my 0.02 CHF

jakob

----- Original Message -----
From: "Oleg Nitz" <on...@uk...>
To: <obj...@li...>
Sent: Wednesday, May 15, 2002 10:23 PM
Subject: Re: [OJB-developers] Re:


> Hi Jakob,
>
> I made the HSQL syntax the default, it seems to be okay for all RDBMS
except
> for Oracle and Sybase.
>
> Regards,
>  Oleg
>
> On Wednesday 15 May 2002 18:42, Jakob Braeuchi wrote:
> > hi oleg,
> >
> > yes the changed order of joins solves the problem in mysql.
> >
> > jakob
> >
> >

Re: [OJB-developers] Re:

[Oleg N. <on...@uk...>]

Hi Jakob,

I made the HSQL syntax the default, it seems to be okay for all RDBMS except 
for Oracle and Sybase.

Regards,
 Oleg

On Wednesday 15 May 2002 18:42, Jakob Braeuchi wrote:
> hi oleg,
>
> yes the changed order of joins solves the problem in mysql.
>
> jakob
>
>
> ----- Original Message -----
> From: "Oleg Nitz" <on...@uk...>
> To: <obj...@li...>
> Sent: Wednesday, May 15, 2002 9:42 AM
>
> Subject: [OJB-developers] Re:
> > Hi Jakob,
> >
> > Is you version of MySQL okay with the query
> >
> > SELECT DISTINCT A0.id,A0.idPerson,A0.nummer,A0.saldo FROM
> >   (tabPerson A1 INNER JOIN tabTelefon A2 ON A1.id=A2.idPerson)
> >   INNER JOIN tabKonto A0 ON A0.idPerson=A1.id
> >   WHERE A2.tel_nr LIKE ?
> >
> > I can change the order of joins, no problem.
> >
> > The alternative SQL92 syntax is used in HSQL, you could try it with
> > MySQL, just append
> >
> >     public byte getJoinSyntaxType()
> >     {
> >         return HSQL_JOIN_SYNTAX;
> >     }
> >
> > to PlatformMySQLImpl.java
> >
> > Regards,
> >  Oleg
> >
> > On Wednesday 15 May 2002 08:59, Jakob Braeuchi wrote:
> > > hi oleg,
> > >
> > > i have a problem with the new SqlStatement:
> > >
> > > [ojb.broker.accesslayer.SqlGenerator] DEBUG: SQL: SELECT DISTINCT
> > > A0.id,A0.idPerson,A0.nummer,A0.saldo FROM tabKonto A0 INNER JOIN
>
> (tabPerson
>
> > > A1 INNER JOIN tabTelefon A2 ON A1.id=A2.idPerson) ON A0.idPerson=A1.id
> > > WHERE A2.tel_nr LIKE ?
> > >
> > > this produces a syntax error in mysql : syntax error near (tabPerson A1
> > > INNER JOIN....
> > >
> > > the query i execute is the following:
> > >
> > > Query query;
> > > Criteria crit;
> > > crit = new Criteria();
> > > crit.addEqualTo("inhaber.telefone.nummer", "031%");
> > > query = new QueryByCriteria(Konto.class, crit, true);
> > > showResult(broker.getCollectionByQuery(query));
> > >
> > > jakob
> >
> > _______________________________________________________________
> >
> > Have big pipes? SourceForge.net is looking for download mirrors. We
> > supply the hardware. You get the recognition. Email Us:
> > ban...@so... _______________________________________________
> > Objectbridge-developers mailing list
> > Obj...@li...
> > https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Objectbridge-developers mailing list
> Obj...@li...
> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers

Re: [OJB-developers] Re:

[Jakob B. <jbr...@ho...>]

hi oleg,

yes the changed order of joins solves the problem in mysql.

jakob


----- Original Message -----
From: "Oleg Nitz" <on...@uk...>
To: <obj...@li...>
Sent: Wednesday, May 15, 2002 9:42 AM
Subject: [OJB-developers] Re:


> Hi Jakob,
>
> Is you version of MySQL okay with the query
>
> SELECT DISTINCT A0.id,A0.idPerson,A0.nummer,A0.saldo FROM
>   (tabPerson A1 INNER JOIN tabTelefon A2 ON A1.id=A2.idPerson)
>   INNER JOIN tabKonto A0 ON A0.idPerson=A1.id
>   WHERE A2.tel_nr LIKE ?
>
> I can change the order of joins, no problem.
>
> The alternative SQL92 syntax is used in HSQL, you could try it with MySQL,
> just append
>
>     public byte getJoinSyntaxType()
>     {
>         return HSQL_JOIN_SYNTAX;
>     }
>
> to PlatformMySQLImpl.java
>
> Regards,
>  Oleg
>
> On Wednesday 15 May 2002 08:59, Jakob Braeuchi wrote:
> > hi oleg,
> >
> > i have a problem with the new SqlStatement:
> >
> > [ojb.broker.accesslayer.SqlGenerator] DEBUG: SQL: SELECT DISTINCT
> > A0.id,A0.idPerson,A0.nummer,A0.saldo FROM tabKonto A0 INNER JOIN
(tabPerson
> > A1 INNER JOIN tabTelefon A2 ON A1.id=A2.idPerson) ON A0.idPerson=A1.id
> > WHERE A2.tel_nr LIKE ?
> >
> > this produces a syntax error in mysql : syntax error near (tabPerson A1
> > INNER JOIN....
> >
> > the query i execute is the following:
> >
> > Query query;
> > Criteria crit;
> > crit = new Criteria();
> > crit.addEqualTo("inhaber.telefone.nummer", "031%");
> > query = new QueryByCriteria(Konto.class, crit, true);
> > showResult(broker.getCollectionByQuery(query));
> >
> > jakob
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Objectbridge-developers mailing list
> Obj...@li...
> https://lists.sourceforge.net/lists/listinfo/objectbridge-developers
>

[OJB-developers] Re:

[Oleg N. <on...@uk...>]

Hi Jakob,

Is you version of MySQL okay with the query

SELECT DISTINCT A0.id,A0.idPerson,A0.nummer,A0.saldo FROM 
  (tabPerson A1 INNER JOIN tabTelefon A2 ON A1.id=A2.idPerson)  
  INNER JOIN tabKonto A0 ON A0.idPerson=A1.id
  WHERE A2.tel_nr LIKE ?

I can change the order of joins, no problem.

The alternative SQL92 syntax is used in HSQL, you could try it with MySQL,
just append

    public byte getJoinSyntaxType()
    {
        return HSQL_JOIN_SYNTAX;
    }

to PlatformMySQLImpl.java

Regards,
 Oleg

On Wednesday 15 May 2002 08:59, Jakob Braeuchi wrote:
> hi oleg,
>
> i have a problem with the new SqlStatement:
>
> [ojb.broker.accesslayer.SqlGenerator] DEBUG: SQL: SELECT DISTINCT
> A0.id,A0.idPerson,A0.nummer,A0.saldo FROM tabKonto A0 INNER JOIN (tabPerson
> A1 INNER JOIN tabTelefon A2 ON A1.id=A2.idPerson) ON A0.idPerson=A1.id
> WHERE A2.tel_nr LIKE ?
>
> this produces a syntax error in mysql : syntax error near (tabPerson A1
> INNER JOIN....
>
> the query i execute is the following:
>
> Query query;
> Criteria crit;
> crit = new Criteria();
> crit.addEqualTo("inhaber.telefone.nummer", "031%");
> query = new QueryByCriteria(Konto.class, crit, true);
> showResult(broker.getCollectionByQuery(query));
>
> jakob