[#COR-1604] Activation decision is being taken upon field type instead of actual type

db4o Core

Activation decision is being taken upon field type instead of actual type

Created: 01/Apr/09 12:51 PM Updated: 14/Jul/09 12:57 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

7.9.88

Time Tracking:

Original Estimate:

Not Specified

Remaining Estimate:

Not Specified

Time Spent:

1.08h

Peers:	Adriano Verona
Order:	3
Iteration:	89
Resolution Date:	07/Apr/09 12:58 PM
Labels:
Participants:	Adriano Verona and Carl Rosenberger
Number of Attachments:	0
Number of Comments:	1

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Adriano Verona - 01/Apr/09 01:54 PM

The fix was to change FieldMetadata#cascadeActivation() to use the class metadata for the concrete object instead of the handler (that is based on the field type)