From jira-events at lists.jboss.org Fri Jan 22 07:04:19 2010
Content-Type: multipart/mixed; boundary="===============7019575655183011485=="
MIME-Version: 1.0
From: Michael Heinen (JIRA) <jira-events at lists.jboss.org>
To: richfaces-issues at lists.jboss.org
Subject: [richfaces-issues] [JBoss JIRA] Commented: (RF-8036) RichFaces
 doesn't work with latest Neko release
Date: Fri, 22 Jan 2010 07:04:19 -0500
Message-ID: <1394166213.1264161859696.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com>
In-Reply-To: 626410629.1256145461425.JavaMail.jboss@jira01.app.mwc.hst.phx2.redhat.com

--===============7019575655183011485==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


    [ https://jira.jboss.org/jira/browse/RF-8036?page=3Dcom.atlassian.jira.=
plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12507706#a=
ction_12507706 ] =


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

I am not sure whether this is a bug in latest neko parser or a config optio=
n 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=3D"areg" renderRegionOnly=3D"false">
    <t:selectOneRadio id=3D"head"  value=3D"#{CyberController.sortByNumber}=
" =

   layout=3D"lineDirection">
      <f:selectItem id=3D"id" itemValue=3D"#{false}" itemLabel=3D"ID"/>
      <f:selectItem id=3D"nr" itemValue=3D"#{true}" itemLabel=3D"Nr"/>
      <a4j:support id=3D"aChange" =

                   event=3D"onclick"
                   actionListener=3D"#{CyberController.dummyListener}"
                   reRender=3D"myform"/>
    </t:selectOneRadio>
</a4j:region>
</h:form> =


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

The <td> tags in the first row are not rendered and therefore IE doesn't di=
splay 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 o=
ff.
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,. whic=
h is 1.9.13.  I believe that this is because Neko has deprecated/removed so=
me 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 Ne=
ko.
> I talked to Alex about this and here is his response:
> That is mix of problems. RichFaces has pluggable set of filters that conv=
erts JSF Html response to well-formed XML that could be parsed by JavaScrip=
t 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 di=
d not pay attention to that because we had had no problems with Neko librar=
ies before. It would take a while to figure out Neko API changes and fix th=
at 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: htt=
ps://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       =20

--===============7019575655183011485==--