Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (athena.apache.org: domain of manfred.geiler@gmail.com
 designates 209.85.146.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=nC/51jgB+McP7IFk0TPsIsDeVfEm0sDnknKMgoAl054LuAejd06CbPC+aRWw1Bz0MzPFgIJl7WSXaHiG1h15Q95drn4Y8U9uH7AHUjUCyZrBQRKx9qI05HR9PqwIFvABfLROIT9eShvLfX4Xo9HXkPycNeURBrIB7icKg6OzgDs=
Message-ID: <564d4f680711190141l3a57becdl8450fe83cdd9e3cc@mail.gmail.com>
Date: Mon, 19 Nov 2007 10:41:48 +0100
From: "Manfred Geiler" <manfred.geiler@gmail.com>
To: "MyFaces Development" <dev@myfaces.apache.org>
Subject: Re: [tobago] Problems with (jsf-)FormBasedLogin,
 stored passwords and FF
In-Reply-To: <9a64d7d10711190124y2ffb4362xadd9f0a788d8f227@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <9a64d7d10711190124y2ffb4362xadd9f0a788d8f227@mail.gmail.com>

I use straight html input tags for my form based login pages.
Why do you need <h:input* for this? Because of skinning?
Rather than adding an intrusive "name" attribute I suggest to launch
two new components <tc:inputFormBasedUsername> and
<tc:inputFormBasedPassword>. The form based login is a very special
case and under normal circumstances overriding the name attribute for
a jsf input breaks everything. So this use case actually demands new
component types rather than a hack/patch in the standard input
component.

--Manfred


On Nov 19, 2007 10:24 AM, Volker Weber <v.weber@inexso.de> wrote:
> Hi,
>
> a problem which was noticed by me (on a linux FF) a while ago seems
> now also occuring on windows FF.
>
> We have a application with form based login where the loginpage is
> created by tobago.
> The name attribute of name and password fields are changed by
> javascript from the jsf-clientIds to the required
> "j_username"/"j_password" in onload.
>
> But this seems to late for the recognition of stored passwords in new FFs.
>
> My proposal is a new attribute "name" on tc:in which value (if exists)
> could be used as name attribute for the correspondending <input> tag
> instead of the clientId.
>
> Any objections or other ideas how to solve this?
>
>
> Regards,
>     Volker
>


-- 
http://www.irian.at
Your JSF powerhouse - JSF Consulting,
Development and Courses in English and
German

Professional Support for Apache MyFaces