Until now I have only used Compass to provide search functionality over a model persisted with an ORM in enterprise applications. The current annotations model works very well for that scenario.
A different scenario is a desktop application that would rather use a single store for search and storage where disks are slower and the memory available is more limited. RSSOwl is an example of such scenario, so I was considering replacing db4o and Direct Lucene with Compass.
In this scenario, I would prefer an annotations model that works similarly to the JPA one where simple elements that are not annotated are persisted automatically with decent defaults. This would be an additional mode that would have to be requested by the user, so it would not affect the more common use-case where Compass is used with an ORM.
Does this make sense or are there technical reasons for not doing it?