Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 59101 invoked from network); 15 Jun 2004 17:22:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 15 Jun 2004 17:22:06 -0000 Received: (qmail 9516 invoked by uid 500); 15 Jun 2004 17:22:15 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 9142 invoked by uid 500); 15 Jun 2004 17:22:12 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 8483 invoked by uid 99); 15 Jun 2004 17:22:07 -0000 Received: from [81.56.241.65] (HELO mail.anyware-tech.com) (81.56.241.65) by apache.org (qpsmtpd/0.27.1) with ESMTP; Tue, 15 Jun 2004 10:22:07 -0700 Received: from apache.org (firewall.anyware [10.1.0.254]) by mail.anyware-tech.com (Postfix) with ESMTP id C98365EBB3 for ; Tue, 15 Jun 2004 19:21:42 +0200 (CEST) Message-ID: <40CF3026.9070301@apache.org> Date: Tue, 15 Jun 2004 19:21:42 +0200 From: Sylvain Wallez User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: fr, en, en-us MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [VOTE] Unrestricting the FOM References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Carsten Ziegeler wrote: >Sylvain Wallez wrote: > > >>Makes sense. And migrating some stuff to the env-context may >>help removing some dependencies on Avalon. But whe have to be >>very careful about what attributes we want to move from >>avalon-context to env-context, and be sure they will still >>make sense in a new container and within blocks. >> >> >> >Yepp. > > >>The only point I'm not sure about is the object model: should >>it be in the env-context, since it also contains that >>env-context? Kind of circular dependency that may be confusing... >> >> >> >Yepp, that's true. I would say we leave this in the avalon >context then. > > If we do that, we can't totally cut the dependency on avalon-context... >>What we need actually is some kind of mini-environment that >>would give access only to the "safe" properties of >>o.a.c.e.Environment, i.e. mainly the object model and >>attributes, plus access to the current avalon-context >>attributes through type-safe getter methods. >> >> Actually, this mini-environment is the object model. Too bad it's currently an untyped Map. Or what about creating an ObjectModel class that would be that mini-environment ? Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }