Annotation on configuration entities that it should not be indexed. And this annotation could be applied also to other entities types that should not be indexed. Maybe even be allowed to mark the type as not indexed and also on individual property/association.
On Thu, Aug 28, 2008 at 9:44 AM, Rickard Öberg <[EMAIL PROTECTED]> wrote: > Hey, > > I've been changing the way the indexing system gets updates from the > EntityStore. Instead of having a specific SideEffect there's a new > generic EntityStoreListener facility, with a SideEffect on the > EntityStore that notifies *all* interested parties. Indexing is one > thing, but backups, replication, management and logging are other > possible uses. > > One problem I'm hitting though is that if this is "always on", then it > means that MemoryEntityStoreService always gets indexed, and when it is > used for configurations this becomes a problem. Basically, a change will > trigger the indexing, which will attempt to load/create the config for > the indexing, which will use the EntityStore, which will trigger the > indexing, and then this loops until OutOfMemory. > > I'm not sure about the best way to get around this. First of all, should > configurations be stored in an EntityStore that is not indexed? That > would be the easiest way to do it. If not, and MemoryEntityStoreService > is always indexed, then the question is how to structure the assembly so > that configurations are not unintentionally indexed. I can't figure out > right now how to assemble the app properly so that this works. Any ideas > are most welcome. > > /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
