On 2010-07-06 16.58, Maik Böhne wrote:
So I would also like to vote for a change to the assembly api, so that
we can define on which circumstance an entity will play a defined
role.
It feels natural to define that an entity in context xyz should play
the roles a,b,c and in a different one it should be d and e.
Just to make sure we know what the options are:
1) With the current setup you could create a AppFooEntity that extends
DomainFooEntity and adds the roles as mixins. You would go to
AppFooEntity and see all the roles in all the contexts. A one-stop-shop
for "how can I use DomainFooEntity in my contexts".
With the assembly version you'd have DomainFooEntity as before, with
data, and then each context would say "for each entity in the app
implementing data interface X, add role Y". So the information about
what roles an entity plays would be located near the context rather than
near the entity.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
