Return-Path: Delivered-To: apmail-click-dev-archive@www.apache.org Received: (qmail 68656 invoked from network); 17 Apr 2010 02:04:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Apr 2010 02:04:46 -0000 Received: (qmail 1407 invoked by uid 500); 17 Apr 2010 02:04:46 -0000 Delivered-To: apmail-click-dev-archive@click.apache.org Received: (qmail 1388 invoked by uid 500); 17 Apr 2010 02:04:46 -0000 Mailing-List: contact dev-help@click.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@click.apache.org Delivered-To: mailing list dev@click.apache.org Received: (qmail 1378 invoked by uid 99); 17 Apr 2010 02:04:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 Apr 2010 02:04:46 +0000 X-ASF-Spam-Status: No, hits=-1303.4 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 Apr 2010 02:04:45 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o3H24Obx009618 for ; Fri, 16 Apr 2010 22:04:25 -0400 (EDT) Message-ID: <30163817.21741271469864852.JavaMail.jira@thor> Date: Fri, 16 Apr 2010 22:04:24 -0400 (EDT) From: "Bob Schellink (JIRA)" To: dev@click.apache.org Subject: [jira] Created: (CLK-661) Add Java based configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Add Java based configuration ---------------------------- Key: CLK-661 URL: https://issues.apache.org/jira/browse/CLK-661 Project: Click Issue Type: Improvement Reporter: Bob Schellink Fix For: 2.3.0 click.xml has grown over the years especially since we introduced the service based architecture. Some of the problems with xml based configurations is: - no compile time checking - no JavaDoc help in IDE I propose we add a new DefaultConfigService class that is Java based which XmlConfigService extends from. Its advantages is the polar opposite of xml disadvantage: - compile time checking - JavaDoc help in IDE - More powerful configuration options, e.g. its possible to configure FileUpload in ways not exposed by xml config. Also possible to create more powerful algorithms e.g. which templates to include/exclude. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira