Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 44342 invoked from network); 21 Aug 2002 06:11:54 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 21 Aug 2002 06:11:54 -0000 Received: (qmail 106 invoked by uid 97); 21 Aug 2002 06:12:31 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 90 invoked by uid 97); 21 Aug 2002 06:12:30 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 78 invoked by uid 98); 21 Aug 2002 06:12:30 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D632F1C.4080305@yahoo.com> Date: Wed, 21 Aug 2002 07:11:40 +0100 From: Paul Hammant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020722 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: DTD compat -- red herring? References: <005b01c24783$f9da0ce0$ac00a8c0@Gabriel> <200208200012.52084.peter@apache.org> <3D61000B.9090306@apache.org> <200208200059.12009.peter@apache.org> <3D613327.5060807@apache.org> <3D619DB1.3040506@apache.org> <3D61E2EF.4050706@yahoo.com> <3D6253CB.7040607@apache.org> <3D630CF9.60403@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Stephen >> This is possible without including any reference or depedency on >> Merlin providing we settle the.xinfo DTD. I would like at add another >> couple of points: >> >> 5) utilities enabling component migration >> >> One of the problems I have had to deal with concerning existing >> components are references to things like BlockContext. Merlin can >> work around this through its context management system. A >> container >> indepedent solution called GenericBlockContext was added to the >> Phoneix CVS. This seemed the correct thing to do as opposed to >> creating a Phoenix depedency in the Merlin CVS. >> >> The original contribution is under the Phoenix CVS (Attic). >> org/apache/avalon/phoenix/tools/export/GenericBlockContext. >> >> Are there any objections/issues to bringing this class back into >> action? > > > > As nobody has objected to this I'll go ahead an re-commit > GenericBlockContext. I for one would like more time to consider this. Please tread carefully dude given recent events. - Paul -- To unsubscribe, e-mail: For additional commands, e-mail: