Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 11793 invoked from network); 25 Aug 2002 12:54:05 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 Aug 2002 12:54:05 -0000 Received: (qmail 8434 invoked by uid 97); 25 Aug 2002 12:54:33 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 8416 invoked by uid 97); 25 Aug 2002 12:54:32 -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 8400 invoked by uid 98); 25 Aug 2002 12:54:32 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D68D340.7000504@apache.org> Date: Sun, 25 Aug 2002 14:53:20 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon Developers List Subject: Re: Container nesting, common attributes and startup layer: Solution? (was Re: BlockContext & Merlin.) References: <3D677832.20604@yahoo.com> <200208250354.42938.peter@apache.org> <3D67DE8C.6030901@apache.org> <3D68B067.7050102@yahoo.com> <3D68C1B4.3090807@apache.org> <3D68CE40.2020705@yahoo.com> 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: daedalus.apache.org 1.6.2 0/1000/N Paul Hammant wrote: [snipped many things that don't reall make much sense to me, but that I won't question for the respect I have of you; go along, I will follow] > Nicola, ... >> 3) define a common startup layer for the Avalon Containers, so that it >> can be used with all containers. I imagine a single set of shell >> scripts, a single servlet container, a single class container, which >> can use inside any other container. >> This would make it possible to run Phoenix or Merlin or whatever as >> standalone, or in a servlet, or in another program... and also nested. > > I don't think you can count servlet. Why? It is not an Lifecycle using > API. Concrete example: Cocoon is an Avalon Container. I want to be able to run it standalone (CLI), in a Servlet (as now) or directly as a .SAR in Phoenix. >> This would eliminate the problems we are having now, by making >> components usable in all containers by nesting containers, and making >> any container easily embedded in other apps. > > > With respect, I have written two containers that sit on top of the > default container Phoenix. They are Jesktop and EOB. Both of them > handle classloading of their separate componets well enough. It would > be nice for me to use ContainerKit or Excalibur/Container to save lines > of code, but I have not done so yet. Anyway, the point is that > container-in-container is possible already. I can easily make plain components work in Phoenix, but as you have seen with Merlin, viceversa is not painless. Can Merlin use EOB? > *Please* let me continue with my slow programme of issue-by-issue > conflict resolution. [I still don't see how your mail about the blurb is an issue-by-issue conflict resolution; please remain concrete on the proposals.] -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: