if (featOkTst && casFeat_xxxx == null)
JCas.throwFeatMissing("xxxx, "cas-type-name-for-xxxx");
These calls are in pre-existing JCas cover classes. I guess we're
planning to have new JCas cover classes generated
(unless we put in a layer to make the old ones work - they would be
tying into classes named "com.ibm.etc.").
I already have a utility that does the appropriate search-and-replace
operations on user code to migrate it from IBM UIMA to Apache UIMA.
I'd like that to also work on JCas cover classes. It takes care of
the com.ibm -> org.apache change, for sure. If other changes can be
handled by simple search and replace, we can easily add those as ell.
So I can change JCasGen to generate a ref to JCasImpl.etc. instead of
JCas.etc.
if( featOkTst && casFeat_xxxx == null)
JCasImpl.throwFeatMissing("xxxx, "cas-type-name-for-xxxx");
Does this sound like the right idea?
I like using JCasUtil rather than JCasImpl for this, as you suggested
in your other email. This change is easy enough to make with search
and replace.
-Adam
