Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Message-ID: <27294128.223011294442028144.JavaMail.jira@thor>
Date: Fri, 7 Jan 2011 18:13:48 -0500 (EST)
From: "Jakob Korherr (JIRA)" <dev@myfaces.apache.org>
To: dev@myfaces.apache.org
Subject: [jira] Commented: (MYFACES-3012) Allow f:param for <h:inputText>
 <f:ajax>
In-Reply-To: <155717.212781294412626510.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/MYFACES-3012?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12=
979018#action_12979018 ]=20

Jakob Korherr commented on MYFACES-3012:
----------------------------------------

I am not sure if this really =C2=BBshould=C2=AB work. At least I could not =
find any documentation about it in the spec.

IMO it is clear that this should work for UICommand components, because f:p=
aram is associated with the command that this component triggers. But I don=
't know if this should be true for input components also, because on a non-=
ajax JSF request this is also not supported by input components.

However, looking at the javascript spec of jsf.ajax.request(source, event, =
options) I found the following:

options
    The set of available options that can be sent as request parameters to =
control client and/or server side request processing. Acceptable name/value=
 pair options are:
    name =09value
    execute =09space seperated list of client identifiers
    render =09space seperated list of client identifiers
    onevent =09function to callback for event
    onerror =09function to callback for error
    params =09object containing parameters to include in the request
    The options argument is optional.

--> you are able to specify custom params here, so why shouldn't it work vi=
a the JSF tags f:param + f:ajax?

Thus IMO we should ask the expert group about the expected behavior before =
committing the patch. However, I think the behavior you're describing is NO=
T expected in JSF 2.0 and 2.1, but it might be a cool feature for JSF 2.2.

Furthermore it could support something like this:

<f:ajax>
    <f:param name=3D"param1" value=3D"value1" />
</f:ajax>

I'll write a mail to jsr-314-open about this!

> Allow f:param for <h:inputText> <f:ajax>
> ----------------------------------------
>
>                 Key: MYFACES-3012
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3012
>             Project: MyFaces Core
>          Issue Type: Improvement
>          Components: JSR-314
>    Affects Versions: 2.0.4-SNAPSHOT
>         Environment: myfaces trunk, shared svn. rev 1051469
>            Reporter: Martin Ko=C4=8D=C3=AD
>            Priority: Minor
>         Attachments: MYFACES-3012.patch
>
>
> I don't know what  spec says but following should work:
> <h:inputText>
>   <f:param name=3D"paramName" value=3D"paramValue" />  =20
>   <f:ajax />
> </h:inputText>
> expected result is paramName =3D paramValue pair in request.
> For h:command it works already.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.