a4j:support doesn't work inside tomahawk dataTable
--------------------------------------------------
Key: RF-4020
URL: https://jira.jboss.org/jira/browse/RF-4020
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.6
Environment: tomahawk, myfaces 1.1.5
Reporter: tbech
The a4j:support for the component (selectOneMenu or inputText, etc) in
tomahawk dataTable doesn't work. The request to the server is done, but:
- component has binding, however the 'binding' doesn't have submitted value set
(so no way to get the value);
- the component in 'rerender' attribute is not rerendered.
Log:
debug[13:33:03,009]: Full response content: <?xml version="1.0"?>
...
<body><select id="content:searchForm:data:myField"
name="content:searchForm:data:myField" size="1" class=""
onchange="A4J.AJAX.Submit('_viewRoot','content:searchForm',event,{
...
debug[13:33:03,056]: Attempt to update part of page for Id:
content:searchForm:data:myField
debug[13:33:03,056]: call getElementById for id= content:searchForm:data:myField
warn[13:33:03,056]: Node for replace by response with id
content:searchForm:data:myField not found in document
The problem is, that the name of the component is not well resolved - the
missing part is the index. It should be
<body><select id="content:searchForm:data:0:myField"
name="content:searchForm:data:0:myField" size="1" class=""
onchange="A4J.AJAX.Submit('_viewRoot','content:searchForm',event,{
We have plenty of pages with tomahawk:dataTable, and migration to any other
component (for example rich:dataTable) is not possible, however the a4j:support
is needed now. I suspect that the same problem is with standard
myfaces:dataTable.
--
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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues