From dev-return-11779-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Thu Mar 03 19:03:38 2005 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 9867 invoked from network); 3 Mar 2005 19:03:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 3 Mar 2005 19:03:38 -0000 Received: (qmail 48453 invoked by uid 500); 3 Mar 2005 19:03:34 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 48390 invoked by uid 500); 3 Mar 2005 19:03:33 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 48376 invoked by uid 99); 3 Mar 2005 19:03:33 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from smtp105.mail.sc5.yahoo.com (HELO smtp105.mail.sc5.yahoo.com) (66.163.169.225) by apache.org (qpsmtpd/0.28) with SMTP; Thu, 03 Mar 2005 11:03:32 -0800 Received: from unknown (HELO ?192.168.1.5?) (david?jencks@66.93.38.137 with plain) by smtp105.mail.sc5.yahoo.com with SMTP; 3 Mar 2005 19:03:30 -0000 Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Message-Id: <725640795d51b7e90a28c6b2a1e9e7c2@yahoo.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: dev@geronimo.apache.org From: David Jencks Subject: Moving to xmlbeans v2 Date: Thu, 3 Mar 2005 11:03:29 -0800 X-Mailer: Apple Mail (2.619.2) X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I have geronimo running with xmlbeans v 2. I discovered 3 problems in xmlbeans v2, one a blocker, for which I submitted a bug report and patch http://issues.apache.org/jira/browse/XMLBEANS-116 The other two problems have fairly simple workarounds. Advantages of v2: 1. bug in namespace of reference to group fixed, simplifying our plan schemas for env references 2. bug in unique key constraints fixed, allowing us to use the spec ws-client schema unmodified 3. better handling of any elements, simplifying code in service-builder for xml-attributes that uses an any element. I would like to move to v2 as soon as possible to avoid trying to maintain my patched version. choices: 1. Move now, using a privately built copy of xmlbeans including my patch. 2. Move as soon as XMLBEANS-116 is fixed in xmlbeans source using a snapshot we build (unless xmlbeans is providing snapshots) 3. Move when the next beta including XMLBEANS-116 is released. Comments? I'd prefer 1, 2, and 3 in that order. thanks david jencks