Return-Path: X-Original-To: apmail-uima-user-archive@www.apache.org Delivered-To: apmail-uima-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AC8D0105C9 for ; Mon, 1 Jul 2013 17:52:35 +0000 (UTC) Received: (qmail 38861 invoked by uid 500); 1 Jul 2013 17:52:35 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 38508 invoked by uid 500); 1 Jul 2013 17:52:33 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 38329 invoked by uid 99); 1 Jul 2013 17:52:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jul 2013 17:52:32 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [138.26.5.57] (HELO uabexch1.ad.uab.edu) (138.26.5.57) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jul 2013 17:52:25 +0000 Received: from UABEXMB5.ad.uab.edu ([169.254.6.105]) by uabexch1.ad.uab.edu ([138.26.5.57]) with mapi id 14.03.0123.003; Mon, 1 Jul 2013 12:52:03 -0500 From: "John David Osborne (Campus)" To: "user@uima.apache.org" Subject: Re: Multiple References to an Array Thread-Topic: Multiple References to an Array Thread-Index: Ac5tKagai1W+pbILQR+Js9f8obwg/gAvOgiAAidHjgA= Date: Mon, 1 Jul 2013 17:52:03 +0000 Message-ID: In-Reply-To: <51C307DB.6070105@schor.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.4.130416 x-originating-ip: [138.26.5.24] Content-Type: text/plain; charset="us-ascii" Content-ID: <030FFC066D0C834B847494CE9ADC9C77@mail.ad.uab.edu> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org 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" wrote: >Please read >http://uima.apache.org/d/uimaj-2.4.0/references.html#ugr.ref.xmi.array_and >_list_features.=20 >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.=20 > >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 >> >> >