Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 41275 invoked from network); 28 Jul 2005 16:36:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 28 Jul 2005 16:36:28 -0000 Received: (qmail 64320 invoked by uid 500); 28 Jul 2005 16:36:14 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 64262 invoked by uid 500); 28 Jul 2005 16:36:14 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 64221 invoked by uid 99); 28 Jul 2005 16:36:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2005 09:36:14 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [217.199.181.91] (HELO ns3.wkwyw.net) (217.199.181.91) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 28 Jul 2005 09:36:05 -0700 Received: (qmail 14198 invoked from network); 28 Jul 2005 16:36:14 -0000 Received: from 82-69-78-226.dsl.in-addr.zen.co.uk (HELO ?192.168.0.2?) (82.69.78.226) by ns3.wkwyw.net with SMTP; 28 Jul 2005 16:36:14 -0000 Message-ID: <42E9096F.5040905@apache.org> Date: Thu, 28 Jul 2005 17:35:59 +0100 From: Ross Gardler User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Forrest Developers List Subject: Where to put forrest:contracts Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N One thing we discussed a little on the list before ApacheCon and we touched on at ApacheCon, but never came up with a proposal was the issue of where to put forrest:contracts. Currently all XHTML contracts are stored in the viewHelper.xhtml plugin. As was mentioned on this list before this limits reuse of the contracts across different forrest:views implementations. In addition this creates a dependency between the XHTML view and other plugins, fo example, if we use the PDF contract we create a dependancy on the PDF plugin. We are seeing this agian with the view plugin. Is it possible, and does it make sense to, have plugins provide contracts for use in forrest:views? Ross