Hi, Are there any plans to support UIMA 3 CAS-transported custom Java objects in JCasGen? The current TypeSystem description XML that it consumes doesn’t allow specifying these fields, but could we imagine some way of encoding this into the XML, so that the JGasGen could make use of it?
We are using the Gradle build system and a third party JCasGen plugin for Gradle to generate our types, and everything is automated through the build system. Additionally we use IDEA instead of Eclipse in our development, so we can’t use any of the Eclipse plugins either. We have on several occasions considered to manually craft some of our types, but we have so far been reluctant to go down that path, although it isn’t necessarily such a big deal, especially since it seems to be simpler with UIMA 3. CAS-transported custom Java objects could be a compelling reason for us to consider this again, since we have a number of cases where this would yield some performance improvements and simplify our code. We also want to specify shared interfaces that type system types implement, since that will allow us to make better use of Java generics with them. Yet, I believe most of this could also be achieved using the JCasGen with a few extensions to the type system description, but I don’t know how fixed that is. I can imagine that it is easy to make changes that has wide implications on the API, which is not the intention here, but I am thinking more of some extensions that otherwise would be ignored by all other framework components. I don’t expect everything to be generated either, e.g. some elements like serialisers and interfaces could be implemented externally and then referenced in the type system description for use by JCasGen. Cheers Mario ________________________________ Disclaimer: This email and any files transmitted with it are confidential and directed solely for the use of the intended addressee or addressees and may contain information that is legally privileged, confidential, and exempt from disclosure. If you have received this email in error, please notify the sender by telephone, fax, or return email and immediately delete this email and any files transmitted along with it. Unintended recipients are not authorized to disclose, disseminate, distribute, copy or take any action in reliance on information contained in this email and/or any files attached thereto, in any manner other than to notify the sender; any unauthorized use is subject to legal prosecution.
