[
https://issues.apache.org/jira/browse/UIMA-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889155#action_12889155
]
Thilo Goetz commented on UIMA-1839:
-----------------------------------
I think it's just a bug that should be fixed.
> String-subtype features can't be set to null?
> ---------------------------------------------
>
> Key: UIMA-1839
> URL: https://issues.apache.org/jira/browse/UIMA-1839
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.3
> Reporter: Adam Lally
> Priority: Minor
>
> If you try to set a string-subtype feature to null, you get a
> NullPointerException:
> java.lang.NullPointerException
> at java.lang.String.compareTo(String.java:1167)
> at java.lang.String.compareTo(String.java:92)
> at java.util.Arrays.binarySearch0(Arrays.java:2001)
> at java.util.Arrays.binarySearch(Arrays.java:1943)
> at org.apache.uima.cas.impl.CASImpl.ll_setStringValue(CASImpl.java:3203)
> at
> org.apache.uima.cas.impl.FeatureStructureImpl.setStringValue(FeatureStructureImpl.java:130)
> The documentation doesn't specifically address whether this is allowed, but
> my intuition was that it should be. For one thing, a string-subtype feature
> can have the value null when it is uninitialized, so why shouldn't I be able
> to explicitly set it to null?
> A simple way to replicate is to add the line
> fs.setStringValue(stringSetFeat, null);
> to the test case method StringSubtypeTest.testCas()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
