|
From: Gavin K. <ga...@ap...> - 2002-10-13 16:13:35
|
> I think we should take the former option, one persister per class. Then > we should be able to add new Persisters at runtime. (And change the > field definitions of existing persisters) Okay, cool, but how are you going to do that without requiring a synchronized method each time we look up a ClassPersister (which happens very often)? I think you will need to think very carefully about the whole add/lookup dynamic ClassPersister issue. It seems to be a major departure from the current model that there is an immutable collection of immutable ClassPersisters. |