You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@uima.apache.org by "John David Osborne (Campus)" <oz...@uab.edu> on 2013/07/01 19:39:02 UTC
Re: Multiple References to an Array
Thanks Thilo, that was helpful.
Is this (1.0) the standard you were referring to?
http://docs.oasis-open.org/uima/v1.0/uima-v1.0.html
-John
On 6/20/13 7:09 AM, "Thilo Goetz" <tw...@gmx.de> wrote:
>On 06/19/2013 10: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
>>
>>
>
>The underlying reason is that the XMI datastructure we use
>for encoding arrays
>is not an "object" that you can refer to, while UIMA arrays
>_are_ objects you can refer to. So the array will not be
>serialized once, but many times in all the places it is
>referenced. When the CAS is unmarshalled, as many distinct
>arrays will be created, and you can't tell if two feature
>structures refer to the same array any more. If you don't
>mind that, you don't need to worry about this message.
>
>If you want to understand why UIMA is doing such a thing
>(and I'm not defending it, just explaining), you'll have
>to start digging into the OASIS standard.
>
>--Thilo
>
Re: Multiple References to an Array
Posted by Thilo Goetz <tw...@gmx.de>.
On 07/01/2013 07:39 PM, John David Osborne (Campus) wrote:
> Thanks Thilo, that was helpful.
>
> Is this (1.0) the standard you were referring to?
> http://docs.oasis-open.org/uima/v1.0/uima-v1.0.html
>
> -John
>
Yes.
>
> On 6/20/13 7:09 AM, "Thilo Goetz" <tw...@gmx.de> wrote:
>
>> On 06/19/2013 10: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
>>>
>>>
>>
>> The underlying reason is that the XMI datastructure we use
>> for encoding arrays
>> is not an "object" that you can refer to, while UIMA arrays
>> _are_ objects you can refer to. So the array will not be
>> serialized once, but many times in all the places it is
>> referenced. When the CAS is unmarshalled, as many distinct
>> arrays will be created, and you can't tell if two feature
>> structures refer to the same array any more. If you don't
>> mind that, you don't need to worry about this message.
>>
>> If you want to understand why UIMA is doing such a thing
>> (and I'm not defending it, just explaining), you'll have
>> to start digging into the OASIS standard.
>>
>> --Thilo
>>
>