Re: Possible CollectionProxy bug?

2003-06-19 Thread Thomas Mahler 
confirmed and fixed!

Edson Carlos Ericksson Richter wrote:
Anyone can confirm that this is a bug or not?

Thanks,

Edson Richter
- Original Message - 
From: Edson Carlos Ericksson Richter [EMAIL PROTECTED]
To: OJB Users List [EMAIL PROTECTED]
Sent: Thursday, June 12, 2003 11:13 AM
Subject: Possible CollectionProxy bug?

I think I get RemovalAwareCollection working with proxied classes.

The method afterStore in CollectionProxy should not be:

public void afterStore(PersistenceBroker broker) throws
PersistenceBrokerException
{
  Collection c = getData();
  if( c instanceof ManageableCollection )
( ( ManageableCollection )c ).afterStore( broker );
}

Thomas, can you confirm this?

Thanks,

Edson Richter



- Original Message - 
From: onno [EMAIL PROTECTED]
To: OJB Users List [EMAIL PROTECTED]
Sent: Thursday, June 12, 2003 9:22 AM
Subject: Auto-delete woes

Long time no post but we found a strange behaviour in our app which
otherwise has been running fine.
it involves the auto-delete

we use

Broker.deleteByQuery(aQuery); //where the Query is just a 1 Primary Key from
an object.
This however doesn't seem to delete any linked objects (ie per defined in
auto-delete)
eg:

  Request (auto-everything == true ;)
 1-1 with a Interaction  (auto-everything == true ;)
   1-1 with a (Temp User) (auto-everything == true
;)
when we delete a request it gets deleted however the Interaction Object
sticks around and
needless to say also the Temp User.
Any logic error we do?

Greetz

Onno

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.488 / Virus Database: 287 - Release Date: 5/6/2003


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.489 / Virus Database: 288 - Release Date: 10/6/2003


-
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: Possible CollectionProxy bug?

2003-06-13 Thread Edson Carlos Ericksson Richter 
Anyone can confirm that this is a bug or not?

Thanks,

Edson Richter
- Original Message - 
From: Edson Carlos Ericksson Richter [EMAIL PROTECTED]
To: OJB Users List [EMAIL PROTECTED]
Sent: Thursday, June 12, 2003 11:13 AM
Subject: Possible CollectionProxy bug?


I think I get RemovalAwareCollection working with proxied classes.

The method afterStore in CollectionProxy should not be:


public void afterStore(PersistenceBroker broker) throws
PersistenceBrokerException
{
  Collection c = getData();

  if( c instanceof ManageableCollection )
( ( ManageableCollection )c ).afterStore( broker );

}


Thomas, can you confirm this?

Thanks,

Edson Richter




- Original Message - 
From: onno [EMAIL PROTECTED]
To: OJB Users List [EMAIL PROTECTED]
Sent: Thursday, June 12, 2003 9:22 AM
Subject: Auto-delete woes


Long time no post but we found a strange behaviour in our app which
otherwise has been running fine.

it involves the auto-delete

we use

Broker.deleteByQuery(aQuery); //where the Query is just a 1 Primary Key from
an object.

This however doesn't seem to delete any linked objects (ie per defined in
auto-delete)

eg:

  Request (auto-everything == true ;)
 1-1 with a Interaction  (auto-everything == true ;)
   1-1 with a (Temp User) (auto-everything == true
;)

when we delete a request it gets deleted however the Interaction Object
sticks around and
needless to say also the Temp User.

Any logic error we do?

Greetz

Onno


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.488 / Virus Database: 287 - Release Date: 5/6/2003



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.489 / Virus Database: 288 - Release Date: 10/6/2003



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Possible CollectionProxy bug?

2003-06-12 Thread Edson Carlos Ericksson Richter 
I think I get RemovalAwareCollection working with proxied classes.

The method afterStore in CollectionProxy should not be:


public void afterStore(PersistenceBroker broker) throws
PersistenceBrokerException
{
  Collection c = getData();

  if( c instanceof ManageableCollection )
( ( ManageableCollection )c ).afterStore( broker );

}


Thomas, can you confirm this?

Thanks,

Edson Richter




- Original Message - 
From: onno [EMAIL PROTECTED]
To: OJB Users List [EMAIL PROTECTED]
Sent: Thursday, June 12, 2003 9:22 AM
Subject: Auto-delete woes


Long time no post but we found a strange behaviour in our app which
otherwise has been running fine.

it involves the auto-delete

we use

Broker.deleteByQuery(aQuery); //where the Query is just a 1 Primary Key from
an object.

This however doesn't seem to delete any linked objects (ie per defined in
auto-delete)

eg:

  Request (auto-everything == true ;)
 1-1 with a Interaction  (auto-everything == true ;)
   1-1 with a (Temp User) (auto-everything == true
;)

when we delete a request it gets deleted however the Interaction Object
sticks around and
needless to say also the Temp User.

Any logic error we do?

Greetz

Onno


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.488 / Virus Database: 287 - Release Date: 5/6/2003



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]