I would go for annotation as this is consistent with what we have till now and more clear for a user just by looking at the entity. If we need a way to override that "default" during assembly we can add the method later on.
On Thu, Aug 28, 2008 at 11:19 AM, Rickard Öberg <[EMAIL PROTECTED]> wrote: > Alin Dreghiciu wrote: >> Do you mean a method that you can use during assembly so you can >> specify if the entity is indexed based on your use case? > > Either that or an annotation that can be put on the entity permanently. > > /Rickard > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
