[jira] [Commented] (UIMA-5573) uv3 change JCas feature slot initialization to be more lazy

[ https://issues.apache.org/jira/browse/UIMA-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168530#comment-16168530 ] Richard Eckart de Castilho commented on UIMA-5573: -- Awesome :) > uv3 change JCas feature

Build failed in Jenkins: UIMA-uimaFIT v3 » Apache UIMA uimaFIT - Examples #32

See -- [INFO] [INFO]

Build failed in Jenkins: UIMA-uimaFIT v3 #32

See -- [...truncated 151.54 KB...] Sep 15, 2017 7:15:02 PM org.apache.uima.internal.util.Misc addUrlsFromPath(257) WARNING: Skipping adding "[]" to URLs Sep 15, 2017 7:15:02 PM

Jenkins build is back to normal : UIMA-v3-sdk #226

See

Re: opinions, please, for a UV3 proposed change

How about dropping the "get"? Java Collections also does without. -- Richard > On 15.09.2017, at 16:16, Marshall Schor wrote: > > +1. New methods on CAS and JCas: > > getEmptyList(FloatList.class) > > getEmptyFloatList() > > etc. for the other 3 lists (integer, string, fs)

[jira] [Commented] (UIMA-5573) uv3 change JCas feature slot initialization to be more lazy

[ https://issues.apache.org/jira/browse/UIMA-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168289#comment-16168289 ] Marshall Schor commented on UIMA-5573: -- I found an approach that looks very promising. I tried it

[jira] [Created] (UIMA-5574) uv3 UIMA Exceptions constructors calling wrong super

Marshall Schor created UIMA-5574: Summary: uv3 UIMA Exceptions constructors calling wrong super Key: UIMA-5574 URL: https://issues.apache.org/jira/browse/UIMA-5574 Project: UIMA Issue Type:

[jira] [Created] (UIMA-5573) uv3 change JCas feature slot initialization to be more lazy

Marshall Schor created UIMA-5573: Summary: uv3 change JCas feature slot initialization to be more lazy Key: UIMA-5573 URL: https://issues.apache.org/jira/browse/UIMA-5573 Project: UIMA

Re: [jira] [Commented] (UIMA-5571) uv3 log4j bridge not handling multi-substitutable args vs throwable correctly

I don't think it does.   The fix might be somewhat complex, because several back-ends (log4j and java-util-logging) don't support message argument substitution when a throwable is being used. I'll have to see if I can figure out a suitable fix... Thanks. -Marshall On 9/15/2017 3:50 AM, Richard

Re: opinions, please, for a UV3 proposed change

+1.  New methods on CAS and JCas: getEmptyList(FloatList.class) getEmptyFloatList() etc. for the other 3 lists (integer, string, fs) getEmptyArray(FloatArray.class) getEmptyFloatArray()  etc. for the other 8 types (boolean, byte, short, integer, long, double, string, fs) -Marshall On

[jira] [Commented] (UIMA-5571) uv3 log4j bridge not handling multi-substitutable args vs throwable correctly

[ https://issues.apache.org/jira/browse/UIMA-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167479#comment-16167479 ] Richard Eckart de Castilho commented on UIMA-5571: -- SLF4J automatically detects if the

[jira] [Comment Edited] (UIMA-5571) uv3 log4j bridge not handling multi-substitutable args vs throwable correctly

[ https://issues.apache.org/jira/browse/UIMA-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167479#comment-16167479 ] Richard Eckart de Castilho edited comment on UIMA-5571 at 9/15/17 7:49 AM:

Re: opinions, please, for a UV3 proposed change

sounds good +1 Am 15.09.2017 um 09:47 schrieb Richard Eckart de Castilho: > The CAS could have a convenience method to fetch a zero-length instance, like > e.g. Collections.emptyList() which could return a shared instance. Users > caring > to optimize could use that without having to implement

Re: opinions, please, for a UV3 proposed change

The CAS could have a convenience method to fetch a zero-length instance, like e.g. Collections.emptyList() which could return a shared instance. Users caring to optimize could use that without having to implement their own code for managing a shared instance. Users relying on object identity