[richfaces-issues] [JBoss JIRA] Commented: (RF-8036) RichFaces doesn't work with latest Neko release

[Michael Heinen (JIRA)]

    [ https://jira.jboss.org/jira/browse/RF-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12507706#action_12507706 ] 

Michael Heinen commented on RF-8036:
------------------------------------

I am not sure whether this is a bug in latest neko parser or a config option which should be set now explicitly from richfaces.
Many tables are not rendered correctly with neko 1.9.13 but with 1.9.12!
I use richfaces 3.3.3beta1

sample:
<a4j:region id="areg" renderRegionOnly="false">
    <t:selectOneRadio id="head"  value="#{CyberController.sortByNumber}" 
   layout="lineDirection">
      <f:selectItem id="id" itemValue="#{false}" itemLabel="ID"/>
      <f:selectItem id="nr" itemValue="#{true}" itemLabel="Nr"/>
      <a4j:support id="aChange" 
                   event="onclick"
                   actionListener="#{CyberController.dummyListener}"
                   reRender="myform"/>
    </t:selectOneRadio>
</a4j:region>
</h:form> 

If this snippet is rerendered via AJAX then the html output is following:
<table id="myform:head"><tbody>		<tr><input id="myform:head:0"

The <td> tags in the first row are not rendered and therefore IE doesn't display it correctly.
It is rendered correctly with neko 1.9.12!

Could this be caused by new options in neko parser which should be turned off.
Pls see release notes of their latest version 1.9.13

> RichFaces doesn't work with latest Neko release
> -----------------------------------------------
>
>                 Key: RF-8036
>                 URL: https://jira.jboss.org/jira/browse/RF-8036
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: core, third-party
>            Reporter: Stan Silvert
>            Assignee: Andrey Markhel
>            Priority: Minor
>             Fix For: 3.3.3.BETA1
>
>
> Right now, RichFaces will not work with the latest version of Neko,. which is 1.9.13.  I believe that this is because Neko has deprecated/removed some of its API.   
> The API's were deprecated for a long time before they were removed.  So, when this is fixed, RichFaces should work with many previous versions of Neko.
> I talked to Alex about this and here is his response:
> That is mix of problems. RichFaces has pluggable set of filters that converts JSF Html response to well-formed XML that could be parsed by JavaScript XMLHttpRequest. One of these filters is based on Neko html
> and that is default RichFaces demo configuration. These test errors seem like API change between versions that blocks AJAX response processing. I did not pay attention to that because we had had no problems with Neko libraries before. It would take a while to figure out Neko API changes and fix that issue, so I suggest two workarounds:
> 1) Switch back to earlier HtmlUnit version.
> 2) Change init parameter in application web.xml from:
>         <context-param>
>                 <param-name>org.ajax4jsf.xmlparser.ORDER</param-name>
>                 <param-value>NEKO, TIDY</param-value>
>         </context-param>
> to:
>         <context-param>
>                 <param-name>org.ajax4jsf.xmlparser.ORDER</param-name>
>                 <param-value>TIDY</param-value>
>         </context-param>
> that disables Neko parser. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira