Return-Path: X-Original-To: apmail-commons-user-archive@www.apache.org Delivered-To: apmail-commons-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 21E87F1D0 for ; Tue, 30 Apr 2013 16:14:19 +0000 (UTC) Received: (qmail 80576 invoked by uid 500); 30 Apr 2013 16:14:17 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 80479 invoked by uid 500); 30 Apr 2013 16:14:17 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 80471 invoked by uid 99); 30 Apr 2013 16:14:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Apr 2013 16:14:17 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lars.francke@gmail.com designates 209.85.210.43 as permitted sender) Received: from [209.85.210.43] (HELO mail-da0-f43.google.com) (209.85.210.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Apr 2013 16:14:11 +0000 Received: by mail-da0-f43.google.com with SMTP id h21so314546dal.16 for ; Tue, 30 Apr 2013 09:13:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=84GLxlE4Q5zEsXVlRc+LtPj1cuMecfQUB+JPb5qBoEM=; b=DtOcgtL1dmtb2weKeX7ac/TuMtaFwL8tFllMlUB3JNTOanzJEyXKsLT/EqSBEXwT20 8sqp3YPTcFghbG+QD4KGIqu3iA6FdpRFfb+wjIdEDG49uzekl72zZijIHs6eD3ec+lLz X5jX8Zem1TGADF5n5yjZ9LE7sWycFgqdsQ187+pr+07IR4v6rh5t3iJa0PupEC2GYN+v UvnxZIGaMgu1V3+3Oaak5M4jHIf5lY4t1qry005/NW4D+4lVfQhxAVDsLbEUa2In+43G 6GLzpdQB3YXmhVozCinxc/LFaSm3kcIgFRp65NHXXsA/uMYgMs3Xa8wVFu064sLyW+HW BOEw== X-Received: by 10.68.91.131 with SMTP id ce3mr77084152pbb.46.1367338430063; Tue, 30 Apr 2013 09:13:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.226.195 with HTTP; Tue, 30 Apr 2013 09:13:09 -0700 (PDT) From: Lars Francke Date: Tue, 30 Apr 2013 18:13:09 +0200 Message-ID: Subject: [digester] Annotations handled multiple times To: user@commons.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm using the Digester Annotations and everything works pretty well (looking forward to 3.3 for DIGESTER-174). We have a model where we share a "contact" class and have that annotated with an @ObjectCreate.List because it can live under multiple different elements and a tree-like structure where the top level element contains other elements that in turn have "contacts". Here's a simplified version of the schema: A(/a) has B(/a/b) A(/a) has C(/a/c) B has D(/a/b/d + /a/c/d) C has D(/a/b/d + /a/c/d) The problem now is that the AnnotationHandler processes the D element multiple times because it's being reached through multiple branches of the "tree", thus creating multiple instances of the ObjectCreateRule which are all fired and obviously screw up the stack. To me this seems like a bug and the AnnotationHandlers should check if they have already visited an element. I'm happy to file a JIRA but I wasn't sure if this might not be intended behavior for some reason I don't understand yet. Also: I might be completely wrong in my diagnosis of this problem. Any help is greatly appreciated. Cheers, Lars --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@commons.apache.org For additional commands, e-mail: user-help@commons.apache.org