On Nov 11, 2008, at 2:30 PM, Lachlan Deck wrote:
> Yeah and should you share that model in a framework/lib between more
> than one app it really needs to be optional.
I really don't see how you can make it "optional". Entity qualifier is
not optional by design. It is either mapped or not.
I have a solution in mind for the "library" case - smart mapping
overrides. So that a piece of shared mapping could be modified as
needed by the downstream users, with full reuse of the library
mapping. I started developing that as I needed to customize listeners
per project, but I am sure it can be put to good use in many other
cases.
If you need both qualified and unqualified entity in the same project,
then the more I think about it the more I am convinced that a solution
is to map this as two entities.
Andrus
This archive was generated by hypermail 2.0.0 : Tue Nov 11 2008 - 07:43:02 EST