ac:updateModelAfterAJAXRequest (server-side widget)

Since AngularFaces 2.1, this tag shouldn't be needed at all. First of all, I recommend not to use traditional JSF AJAX in
an AngularFaces application. You don't need it. Just move everything you've previously done with AJAX to Javascript.

Second, Marco Rinck has contributed his JUA library to AngularFaces. JUA transparently frees memory allocated by AngularJS and re-initializes
the AngularJS model after an JSF AJAX request. Unfortunately, there are limits to what this library can do.

Re-initializing AngularJS after an AJAX request

In rare cases, AngularJS doesn't recover from an AJAX request. In this case you can re-initialize the AngularJS engine by adding
<ac:updateModelAfterAJAXRequest />. There's a caveat: most likely this causes client-side memory leaks.

ac:updateModelAfterAJAXRequest (server-side widget)

Since AngularFaces 2.1, this tag shouldn't be needed at all. First of all, I recommend not to use traditional JSF AJAX in
an AngularFaces application. You don't need it. Just move everything you've previously done with AJAX to Javascript.

Second, Marco Rinck has contributed his JUA library to AngularFaces. JUA transparently frees memory allocated by AngularJS and re-initializes
the AngularJS model after an JSF AJAX request. Unfortunately, there are limits to what this library can do.

Re-initializing AngularJS after an AJAX request

In rare cases, AngularJS doesn't recover from an AJAX request. In this case you can re-initialize the AngularJS engine by adding
<ac:updateModelAfterAJAXRequest />. There's a caveat: most likely this causes client-side memory leaks.

ac:updateModelAfterAJAXRequest (server-side widget)

Since AngularFaces 2.1, this tag shouldn't be needed at all. First of all, I recommend not to use traditional JSF AJAX in
an AngularFaces application. You don't need it. Just move everything you've previously done with AJAX to Javascript.

Second, Marco Rinck has contributed his JUA library to AngularFaces. JUA transparently frees memory allocated by AngularJS and re-initializes
the AngularJS model after an JSF AJAX request. Unfortunately, there are limits to what this library can do.

Re-initializing AngularJS after an AJAX request

In rare cases, AngularJS doesn't recover from an AJAX request. In this case you can re-initialize the AngularJS engine by adding
<ac:updateModelAfterAJAXRequest />. There's a caveat: most likely this causes client-side memory leaks.

ac:updateModelAfterAJAXRequest (server-side widget)

Since AngularFaces 2.1, this tag shouldn't be needed at all. First of all, I recommend not to use traditional JSF AJAX in
an AngularFaces application. You don't need it. Just move everything you've previously done with AJAX to Javascript.

Second, Marco Rinck has contributed his JUA library to AngularFaces. JUA transparently frees memory allocated by AngularJS and re-initializes
the AngularJS model after an JSF AJAX request. Unfortunately, there are limits to what this library can do.

Re-initializing AngularJS after an AJAX request

In rare cases, AngularJS doesn't recover from an AJAX request. In this case you can re-initialize the AngularJS engine by adding
<ac:updateModelAfterAJAXRequest />. There's a caveat: most likely this causes client-side memory leaks.