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 Reporter: Stan Silvert 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.

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 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.

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.