Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 87996 invoked from network); 27 Oct 2003 13:53:27 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 27 Oct 2003 13:53:27 -0000 Received: (qmail 6056 invoked by uid 500); 27 Oct 2003 13:53:20 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 6013 invoked by uid 500); 27 Oct 2003 13:53:20 -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 6000 invoked from network); 27 Oct 2003 13:53:20 -0000 Received: from unknown (HELO onramp.i95.net) (205.177.132.17) by daedalus.apache.org with SMTP; 27 Oct 2003 13:53:20 -0000 Received: from apache.org ([66.208.12.130]) by onramp.i95.net (8.12.10/8.12.9) with ESMTP id h9RDrK8M013183 for ; Mon, 27 Oct 2003 08:53:21 -0500 Message-ID: <3F9D2353.9050701@apache.org> Date: Mon, 27 Oct 2003 08:53:23 -0500 From: Berin Loritsch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Questions about Meta Info (was Re: cvs commit: cocoon-2.2/src/java/org/apache/cocoon/matching Matcher.java CookieMatcher.java) References: <20031025215950.97595.qmail@minotaur.apache.org> <3F9AF50A.90006@leverageweb.com> In-Reply-To: <3F9AF50A.90006@leverageweb.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: minotaur-2.apache.org 1.6.2 0/1000/N Geoff Howard wrote: > ghoward@apache.org wrote: > >> ghoward 2003/10/25 14:59:50 >> >> Modified: src/java/org/apache/cocoon/matching Matcher.java >> CookieMatcher.java >> Log: >> start fortressizing Matchers. lots of open questions already, >> so I'll pause here. >> >> > > I'm hoping someone with more confidence in the changes needed can check > out the simple changes below. Such a paradigm shift to give up the > marker interfaces (and I'm mourning the loss of content assist. Don't > suppose an eclipse plugin for meta info yet?) Content assist? Eclipse plugin: not at this time. > > Open questions: > - What do sitemap components get for @x-avalon-info? A new made up > string like cookie-matcher? The @name/type from the default sitemap in > 2.1? The @x-avalon-info name="cookie-matcher" line lets you define your components like this: configuration It takes away the need for a separate ROLES file. > - Will this mean we no longer have to declare sitemap components in > the sitemap? More it means that there is no reason to have a ROLES file, which also means taht you can incorporate any component into Cocoon using a friendly configuration name without resorting to specifying user roles files or even internal roles files. > - What about other lifecycle interfaces like: Contextualizable, > Parameterizable, Disposable? They haven't changed. They actually have a reason to exist. They provide information or invoke an event on the component--unlike the marker interfaces that did nothing but mess with the class hierarchy. -- "They that give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin