[jira] Commented: (MYFACES-2531) Support for name/library attributes with h:commandButton

["Martin Koci (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/MYFACES-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829278#action_12829278 ] 

Martin Koci commented on MYFACES-2531:
--------------------------------------

Patch also switch order of rendering url and name/library. According to spec:  "If the "name" attribute is present, execute algorithm Common Algorithm for Obtaining A Resource to Render to obtain a Resource instance. Call Resource.getRequestPath() and output the result as the value of the "src" attribute on the rendered markup. Otherwise, if the "url" attribute is present ...". Previously HtmlImageRendererBase rendered name/library and url vice versa.

> Support for name/library attributes with h:commandButton
> --------------------------------------------------------
>
>                 Key: MYFACES-2531
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2531
>             Project: MyFaces Core
>          Issue Type: New Feature
>          Components: JSR-314
>    Affects Versions: 2.0.0-beta-2
>         Environment: myfaces core trunk
>            Reporter: Martin Koci
>            Priority: Minor
>         Attachments: MYFACES-2531.patch
>
>
> JSF 2.0 specify new name/library attributes for h:graphicImage, h:outputStylesheet and h:outputScript. But current JSF RI implementation supports name/library even on h:commandButton (and maybe others - h:button for example ?). That is very useful feature which allows complex EL like:
>  <h:commandButton name="#{resourceBean.fileName}.#{extensions.extension}" library="#{otherBean.libraryName}/foo/bar/#{randomLibraryName}".
> Supporting this hidden feature enables easy migration from RI to myfaces too.

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