Marshall Schor wrote:
When Cas Views are made, another instance of CASImpl type is created,
and a great many of its fields are copied from the
base view.
How about an alternate design, which moves all of the fields being
copied into a new object that is shared by all CASImpls belonging to one
view? This would "document" much more clearly which things are shared,
and which ones aren't, and open the possibility of convenient updating
of the shared things (should that be necessary) without iterating
through all views.
Any objects to my making this change while I'm mucking around for the
JCas updates and the ClassLoader switching support (for PEARs)?
-Marshall
As long as you create something new that's called CASView(Impl), and leave the
base CAS in CASImpl, I'm all in favor. Just to be clear: what I don't want
is a new class called CASCommon or such, with CASImpl really implementing views.
--Thilo
