On 12/11/06, Thilo Goetz <[EMAIL PROTECTED]> wrote:
What about addFsToIndexes()? I would assume that should live where getIndexRepository() lives.
Yes, I forgot we added that. It would also be only on the view.
It would be nice to change that so they're not actually there (I think that's what you're suggesting).
Right.
Let me see if I understand the proposal that's on the table. There is a core set of APIs that both the view and the container will have, such as createFS() and that whole family of methods. Then there's a bunch of sofa-related stuff and getIndexRepository() which is only defined on views. Finally, there's some view management stuff (such as createView()) that will only be defined on the container. Please let me know if I've misunderstood.
That's the proposal. However, I'm not 100% sure if I think we should really do this, since it seems like it will be disruptive to users. There's a lot to be said for having a simple search-and-replace script that can do the IBM UIMA -> Apache UIMA migration, that works at least for common cases. If we split the CAS interface apart, this would be hard to do. -Adam
