From adffaces-dev-return-1397-apmail-incubator-adffaces-dev-archive=incubator.apache.org@incubator.apache.org Wed Oct 11 16:25:19 2006 Return-Path: Delivered-To: apmail-incubator-adffaces-dev-archive@locus.apache.org Received: (qmail 64179 invoked from network); 11 Oct 2006 16:25:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Oct 2006 16:25:19 -0000 Received: (qmail 21164 invoked by uid 500); 11 Oct 2006 16:25:18 -0000 Delivered-To: apmail-incubator-adffaces-dev-archive@incubator.apache.org Received: (qmail 21150 invoked by uid 500); 11 Oct 2006 16:25:18 -0000 Mailing-List: contact adffaces-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: adffaces-dev@incubator.apache.org Delivered-To: mailing list adffaces-dev@incubator.apache.org Received: (qmail 21141 invoked by uid 99); 11 Oct 2006 16:25:18 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2006 09:25:18 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of awiner@gmail.com designates 66.249.92.168 as permitted sender) Received: from [66.249.92.168] (HELO ug-out-1314.google.com) (66.249.92.168) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Oct 2006 09:25:16 -0700 Received: by ug-out-1314.google.com with SMTP id y2so179277uge for ; Wed, 11 Oct 2006 09:24:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SUjZuWHPzdDwGbhXbjCAvCx3BMmpHcpB25R/i9gSVH2VcJ8u4trj30KXNfVH+ejYB9UVWVzjjQzZK2uMT1rVVmJAmlthQ5fMGZupL3xJ5lj9AKuSJHfvlmOvKfZLFI3c2pc7PFayGbs4pREisdNp+578lshdX0NHOZ7gu4i2FEw= Received: by 10.66.244.11 with SMTP id r11mr1271819ugh; Wed, 11 Oct 2006 09:24:54 -0700 (PDT) Received: by 10.67.102.2 with HTTP; Wed, 11 Oct 2006 09:24:54 -0700 (PDT) Message-ID: <6dac79b90610110924v3dd01726r49e8d50e1c2c686e@mail.gmail.com> Date: Wed, 11 Oct 2006 09:24:54 -0700 From: "Adam Winer" To: adffaces-dev@incubator.apache.org Subject: Re: Re: MyFaces 1.2 component autogeneration (was: Trinidad JSF 1.2 status update) In-Reply-To: <452CA29D.7030407@exadel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1a681ff20610080554t32b3b9a4y80b6017da5d831c4@mail.gmail.com> <6dac79b90610081033w15e2565cxceed811bba7ce5d0@mail.gmail.com> <452CA29D.7030407@exadel.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Alexandr, What's wrong with faces-config.xml metadata? From our perspective, this has been a very successful source of the information needed to derive things as diverse as Javadoc, code, and TLDs (and, faces-config.xml itself). The "XML is bad, annotations are great" line you here a lot these days is waaaay overblown. XML has its strengths, annotations has its strengths. -- Adam On 10/11/06, Alexandr Smirnov wrote: > Component code generation can greatly improve components creation, since > in Ajax4jsf project I also have own generator with same ideas. In > addition to same files as in ADF/Trinidad , we have generator for > renderer's from jsp-like template ( even with same tags as Jsp/jstl, > which allow to use JSP visual editor for renderer's ). For complex > components , it allow avoid most of html errors and can divide work > between html designer and java coders. > As a next stage, I want to reduce files need for component creation to > two - base abstract component class, and renderer template. For > component meta information, I have plan to use Java annotations ( in > current implementation, I use Java reflection to analise component and > implemented interfaces methods, bean properties etc. ). As I thing, such > annotations must be standardize, not proprietary API. Is > Myfaces/Trinidad team will interested to use annotations for component > generator meta information ? I need help to create public api for such > feature. > Also, we can contribute parts of existing generator to MyFaces project, > at least renderer generator part - I don't see such feature in other tools. > > Adam Winer : > > Yes, they definitely could be used in that way. > > > > The basic picture is that you write up a bunch of little mini > > faces-config.xml files, one for each component (don't have to, > > actually, you could generate straight from one big faces-config), > > and from that we autogenerate: > > - Java component classes > > - JSP tag classes > > - TLD file > > - Tag documentation > > - Facelets definition file > > - Overall merged faces-config.xml > > > > -- Adam > > > > > > On 10/8/06, Bruno Aranda wrote: > >> That sounds really interesting. As you may know, we are working quite > >> actively in the implementation of MyFaces 1.2. Now I am migrating the > >> JSF core tags, but we will reach soon the point to migrate the HTML > >> Basic components. I don't know the exact details of how this > >> autogeneration works for Trinidad, but couldn't we have the same or > >> similar method to generate the JSF basic html components for MyFaces? > >> > >> Sorry for cross-posting but I think this can be interesting, > >> > >> Cheers, > >> > >> Bruno > >> > >