Return-Path: Delivered-To: apmail-ws-general-archive@www.apache.org Received: (qmail 62010 invoked from network); 1 May 2005 23:44:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 May 2005 23:44:23 -0000 Received: (qmail 37639 invoked by uid 500); 1 May 2005 23:45:46 -0000 Delivered-To: apmail-ws-general-archive@ws.apache.org Received: (qmail 37582 invoked by uid 500); 1 May 2005 23:45:46 -0000 Mailing-List: contact general-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: general@ws.apache.org list-help: list-unsubscribe: List-Post: Delivered-To: mailing list general@ws.apache.org Received: (qmail 37563 invoked by uid 99); 1 May 2005 23:45:46 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from mail.opensource.lk (HELO squid.cmb.ac.lk) (202.51.147.3) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 01 May 2005 16:45:46 -0700 Received: from [192.168.0.103] ([203.94.84.117]) by squid.cmb.ac.lk (8.12.9/8.12.9) with ESMTP id j41Nq3E4025404; Mon, 2 May 2005 05:52:06 +0600 (LKT) (envelope-from sanjiva@opensource.lk) Subject: Re: RFC: ws-commons From: Sanjiva Weerawarana To: general@ws.apache.org Cc: dims@apache.org In-Reply-To: <4275289C.7040200@gmail.com> References: <4274BBDA.3030807@gmail.com> <19e0530f05050105303bae111c@mail.gmail.com> <1114963335.32308.6.camel@localhost.localdomain> <4275289C.7040200@gmail.com> Content-Type: text/plain Organization: Lanka Software Foundation Date: Mon, 02 May 2005 05:27:10 +0600 Message-Id: <1114990030.32308.37.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Sun, 2005-05-01 at 21:06 +0200, Jochen Wiedmann wrote: > That's something we have discussed in the past. It is of course > reasonable and desirable. However, it is not as trivial as one might > think, particularly because the JAXB specification extends XML Schema > with scopes, that XMLBeans doesn't even know about. If these could be > added to the XMLBeans schema parser, then my guess would be that JaxMe > could use another schema parser relatively easy. Yuck, I'm absolutely against extending XSD in any way ... its a big enough beast as it is!!! Maybe Sun felt the need to extend it to fit it with Java better but that's wrong and way too damned Java centric for me. With Axis2's WSDL2 we're designing it to be used for multiple target languages from the outset and hence any Java-favoring XSD extensions are a definite no-no. > Problem is, I'd definitely spend no work in that direction, because > JaxMe clearly needs other things done first. Can we take the base interfaces for the XSD model from JaxMe (and XMLBeans) and create a set of interfaces in ws-commons? The key question is whether you guys and the XMLBeans guys are willing to be implementing (and extending to make JAXB happy) those interfaces .. if yes then maybe Axis2 folks can try to find some resources to help you get that done. (Dasarath was threatening to do his own "simple" XSD model .. maybe all that positive energy can be focused on a good thing instead ;-) Sanjiva.