Re: Fwd: Using a non-existent collection inside a query

2004-01-10 Thread Jakob Braeuchi
hi edson, [EMAIL PROTECTED] wrote: hi edson, frankly, i'm still confused... Sorry... I think I don't have sufficient english skills to make more clear... i understand that collection-proxies do not seem to help because of the way you built your gui :( Thanks, I think you had some

Re: Fwd: Using a non-existent collection inside a query

2004-01-10 Thread edson . richter
i saw the sample code you posted some days ago. now it's clear how you do it. The first step ;-) ojb needs this field (better: the collection referenced by this field) to handle the m:n-implementors in case of an m:n-relationship. That's just the case. If I use the artifact of

Re: Fwd: Using a non-existent collection inside a query

2004-01-10 Thread Jakob Braeuchi
hi edson, [EMAIL PROTECTED] wrote: i saw the sample code you posted some days ago. now it's clear how you do it. The first step ;-) ojb needs this field (better: the collection referenced by this field) to handle the m:n-implementors in case of an m:n-relationship. That's just the case.

Re: Fwd: Using a non-existent collection inside a query

2004-01-10 Thread edson . richter
i do not see where this happens ? Here (note: the if(!true.equals( bellow is in my patched version of OJB that is working fine): ... private void storeCollections(Object obj, Vector vecCds) throws PersistenceBrokerException { // get all members of obj that are collections and

Re: Fwd: Using a non-existent collection inside a query

2004-01-10 Thread edson . richter
Interesting is that this code is right (will only occur if cds.getCascadeStore() returns true): private void storeCollectionObject(CollectionDescriptor cds, Object otherObject) { // if cascade store: store associated object if (cds.getCascadeStore()) {

Re: Fwd: Using a non-existent collection inside a query

2004-01-10 Thread edson . richter
Really, executing again withou my patch, I've seen that is not the keys, but the field it self. Sorry... The line getting in trouble is Object col = cds.getPersistentField().get(obj); because there is no persistent field at all. I'm a bit lost in too much code, techs, newbie

Re: Fwd: Using a non-existent collection inside a query

2004-01-09 Thread edson . richter
hi edson, frankly, i'm still confused... Sorry... I think I don't have sufficient english skills to make more clear... i understand that collection-proxies do not seem to help because of the way you built your gui :( Thanks, I think you had some experiences (some good, some bad) with

Re: Fwd: Using a non-existent collection inside a query

2004-01-08 Thread Jakob Braeuchi
Edson Carlos Ericksson Richter wrote: (sorry, was a momentary lapse of reason when I clicked the send button). Hi! I'm facing a problem: I've a nice piece of sofware that load modules at runtime. Mostly, each module has their own .xml file with necessary configuration. So, there are no

Re: Fwd: Using a non-existent collection inside a query

2004-01-07 Thread Armin Waibel
Hi Edson, do you have a test case to show the problem? This would be helpful to test your new feature or to find another solution. regards, Armin Edson Carlos Ericksson Richter wrote: (sorry, was a momentary lapse of reason when I clicked the send button). Hi! I'm facing a problem: I've a

Fwd: Using a non-existent collection inside a query

2004-01-06 Thread Edson Carlos Ericksson Richter
(sorry, was a momentary lapse of reason when I clicked the send button). Hi! I'm facing a problem: I've a nice piece of sofware that load modules at runtime. Mostly, each module has their own .xml file with necessary configuration. So, there are no problem here. But imagine that I've a

Using a non-existent collection inside a query

2004-01-05 Thread Edson Carlos Ericksson Richter
Hi! I'm facing a problem: I've a nice piece of sofware that load modules at runtime. Mostly, each module has their own .xml file with necessary configuration. So, there are no problem here. But imagine that I've a customer_repository.xml, that references a quite large table (let's say 100.000,