Return-Path: Delivered-To: apmail-xml-commons-dev-archive@www.apache.org Received: (qmail 35744 invoked from network); 24 Sep 2003 14:52:19 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 24 Sep 2003 14:52:19 -0000 Received: (qmail 83556 invoked by uid 500); 24 Sep 2003 14:52:10 -0000 Delivered-To: apmail-xml-commons-dev-archive@xml.apache.org Received: (qmail 83536 invoked by uid 500); 24 Sep 2003 14:52:10 -0000 Mailing-List: contact commons-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list commons-dev@xml.apache.org Delivered-To: moderator for commons-dev@xml.apache.org Received: (qmail 19015 invoked from network); 24 Sep 2003 07:57:32 -0000 Message-ID: <3F714EC2.8080208@ispsoft.de> Date: Wed, 24 Sep 2003 09:58:58 +0200 From: Jochen Wiedmann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ias CC: commons-dev@xml.apache.org, xerces-j-dev@xml.apache.org, axis-dev@ws.apache.org, jaxme-dev@ws.apache.org Subject: Re: [PROPOSAL] javax.xml and javax.xml.namespace package to xml commons References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Ias wrote: > As far as I'm concerned, Axis and JaxMe uses them in common. On the other > hand, they are going to be under the umbrella of JAXP 1.3 API, which is now > on the stage of community review. What time schedule does JAXP 1.3 have? If I get you right, then the problem will be resolved by using JAXP 1.3, which most probably we will do all sooner or later. Depending on the time schedule I would prefer to leave the situation as it is (short schedule) or agree with you. Jochen