Thanks Marshall, So if I understand correctly there *may* be a single annotator in my application with an inappropriate setting in the descriptor for multiple ReferencesAllowed?
If I can't sort it out that way I will look into modifying the serialization code to give an informative warning, because I am really generating a large number of these messages and I don't want to change my log level. -John On 6/20/13 8:47 AM, "Marshall Schor" <[email protected]> wrote: >Please read >http://uima.apache.org/d/uimaj-2.4.0/references.html#ugr.ref.xmi.array_and >_list_features. >This explains details of this and why it might be important (or not) in >your >application. > >I think that by changing the setting of "multipleReferencesAllowed" you >can tell >the XMI serializer to serialize arrays in a manner which respect object >identity. > >Finding out which array is exhibiting this would take patching the XMI >serializer code which issues the warning. If you do a patch and attach >it to a >Jira issue ( https://issues.apache.org/jira/browse/UIMA ), we'll take a >look at >incorporating an impovement to the warning message being produced. > >-Marshall > > >On 6/19/2013 4:14 PM, John David Osborne (Campus) wrote: >> Does anybody know what the underlying reason that this WARNING is >>generated? >> >> WARNING: Warning: multiple references to an array. Reference identity >>will not be preserved in XMI. >> 6/19/13 2:22:12 PM - 11: >>org.apache.uima.cas.impl.XmiCasSerializer$XmiCasDocSerializer.reportWarni >>ng(211): >> >> Specifically, how do I figure out which references to which array and >>why is this a problem? (I actually don't care about generating the XMI, >>but I think when I deploy an AS service it automatically tries to write >>and or instantiate some XMI). >> >> -John >> >> >
