Return-Path: 
 <user-return-152492-apmail-struts-user-archive=struts.apache.org@struts.apache.org>
Delivered-To: apmail-struts-user-archive@www.apache.org
Received: (qmail 9779 invoked from network); 6 Mar 2006 22:26:20 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 6 Mar 2006 22:26:20 -0000
Received: (qmail 10099 invoked by uid 500); 6 Mar 2006 22:26:11 -0000
Delivered-To: apmail-struts-user-archive@struts.apache.org
Received: (qmail 10011 invoked by uid 500); 6 Mar 2006 22:26:10 -0000
Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@struts.apache.org>
List-Help: <mailto:user-help@struts.apache.org>
List-Post: <mailto:user@struts.apache.org>
List-Id: "Struts Users Mailing List" <user.struts.apache.org>
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Delivered-To: mailing list user@struts.apache.org
Received: (qmail 10000 invoked by uid 99); 6 Mar 2006 22:26:10 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 14:26:10 -0800
X-ASF-Spam-Status: No, hits=1.4 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: 67.88.140.227 is neither permitted nor
 denied by domain of rwallace@thewallacepack.net)
Received: from [67.88.140.227] (HELO beluga.contentconnections.com)
 (67.88.140.227)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2006 14:26:08 -0800
Received: from localhost (localhost [127.0.0.1])
	by beluga.contentconnections.com (Postfix) with ESMTP id 0538AC435
	for <user@struts.apache.org>; Mon,  6 Mar 2006 15:24:13 -0700 (MST)
Received: from beluga.contentconnections.com ([127.0.0.1])
 by localhost (mail.contentconnections.com [127.0.0.1]) (amavisd-new,
 port 10024)
 with ESMTP id 04147-16 for <user@struts.apache.org>;
 Mon,  6 Mar 2006 15:24:10 -0700 (MST)
Received: from [172.20.0.198] (unknown [172.20.0.198])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by beluga.contentconnections.com (Postfix) with ESMTP id BE8DD7D6D
	for <user@struts.apache.org>; Mon,  6 Mar 2006 15:24:10 -0700 (MST)
Message-ID: <440CB6EA.2060807@thewallacepack.net>
Date: Mon, 06 Mar 2006 15:25:46 -0700
From: Richard Wallace <rwallace@thewallacepack.net>
User-Agent: Thunderbird 1.5 (X11/20051201)
MIME-Version: 1.0
To: Struts Users Mailing List <user@struts.apache.org>
Subject: [shale] Extending components with new attributes
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at contentconnections.com
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hello,

I'd like to extend the inputSecret component and give the new component 
an added attribute.  Basically, what I want to do is create a component 
that has the tomahawk equal validator attached to it.  So, what I've got 
now is:

<view>
  <component jsfid="t:validateEqual" 
componentType="org.apache.myfaces.validator.Equal">
    <attributes>
      <set name="for" bindingType="Early" />
    </attributes>
  </component>
 
  <component jsfid="inputPasswordVerification" extends="inputSecret">
    <validator jsfid="t:validateEqual">
      <attributes>
          <set name="for" value="password"/>
      </attributes>
    </validator>
  </component>
</view>

What I'd like to be able to do is replace the attribute for "for" with 
something more like "@for" or something so that I can use the component 
like:

<input type="password" jsfid="inputSecret" id="password" />
<input type="password" jsfid="inputPasswordVerification" for="password" />

Can I add an attribute like that in clay?  That would be very cool.

Thanks,
Rich

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