Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <42EE9CAF.1030904@cyberspaceroad.com>
Date: Mon, 01 Aug 2005 23:05:35 +0100
From: Adam Hardy <ahardy.struts@cyberspaceroad.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB;
 rv:1.7.8) Gecko/20050513 Debian/1.7.8-1
MIME-Version: 1.0
To: Struts Users Mailing List <user@struts.apache.org>
CC: fzlists@omnytex.com
Subject: Re: [STRUTS 2X]: Ideas
References: <20050801115444.21826.qmail@web32612.mail.mud.yahoo.com>
In-Reply-To: <20050801115444.21826.qmail@web32612.mail.mud.yahoo.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Paul Benedict on 01/08/05 12:54, wrote:
> Peter writes:
> 
>>>(2) Stubbing of abstract attributes for framework
>>>implementation like Tapestry.
>>>Are you talking abouting the ``jwcid'' attribute?
> 
> No. 
> 
> When you create a Tapestry page, you don't have to
> implement the getters - or even write the setter
> methods for attributes (unless you want to use them). 
> 
> See the class example I wrote; the three properties
> are stubbed out for implementation and then the
> framework automatically subclasses the class, and
> provides an implementation for them.

So Tapestry auto-generates the subclasses like xdoclet or middlegen? It 
makes me wonder what its deployment lifecycle is like.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org