myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <>
Subject [jira] [Commented] (MYFACES-3544) client side ajax error when render a primefaces datatable with f:ajax
Date Thu, 10 May 2012 08:04:55 GMT


Werner Punz commented on MYFACES-3544:

Ok this is a bug in primfaces, it basically added a script tag with an id, which then in the
browser gets lost, this triggered a sidecondition in our viewstate handling code. NeverthlessI
will add a fix on our side ,because fixing this sidecondition with an additional check makes

> client side ajax error when render a primefaces datatable with f:ajax
> ---------------------------------------------------------------------
>                 Key: MYFACES-3544
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.1.7
>         Environment: tomcat 7, primefaces 3.2
>            Reporter: Marcus B├╝ttner
>         Attachments:
> The following error occurs if a primefaces datatable is rendered by f:ajax.
> Error Message: fragment is null
> --------------------------------------------------------
> Error Name: clientError
> Server error name: TypeError
> --------------------------------------------------------
> Note, this message is only sent, because project stage is development and no other error
listeners are registered.
> If an element outside of the table (e.g. the form) is rendered by f:ajax then it works.
> I will attach a small example. 
> 1.) Start it with e.g. tomcat 7 and VM option = -Dfaces.PROJECT_STAGE=Development
> 2.) call page.xhtml
> 3.) press the "update" button

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message