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

Leonardo Uribe commented on MYFACES-1832:
-----------------------------------------

The response of the ri dev mail list what the following:

.........After talking with the spec leads, the current thinking is that the 
render kit docs/tld docs are incorrect.
I've logged:  
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=436 to 
have the documentation
addressed for 2.0.........

So I'll close this issue as fixed (the encoding of writer.writeAttribute is 
enough).

> bad charset encoding on <f:param> tag
> -------------------------------------
>
>                 Key: MYFACES-1832
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1832
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 1.1.5,  1.2.0, 1.2.2
>         Environment: myfaces 1.1.5 
>            Reporter: Luca Stancapiano
>             Fix For:  1.1.6-SNAPSHOT, 1.2.4-SNAPSHOT
>
>
> there is a bug into myfaces 1.1.5 and up..... 
> on a page as it:
> <h:form>                                                                      
>       
>                  <h:commandLink action="#{Action.execute}">
>                     <h:outputText value="some"/>
>                     <f:param name="id" value="#{instance.id}"/>
>                  </h:commandLink>
> </h:form> 
> using <f:param name="id" value="#{instance.id}"> tag inside <h:commandLink> , 
> I see that instance.id value has a bad encoding... if I use a word with 
> special characters as à, è, ù, ì as instance.id for example 'modalità' , it 
> is encoded into 'modalit&amp;#224' instead of 'modalit&agrave' . When I click 
> on link through command link, that id cannot to be decoded and so cannot to 
> work with the real value ofinstance.id

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

Reply via email to