Attached test case that shows issue.

So I ran the test and can see the reported issue. Rather than remove the entire datapaginator component, I removed some of it's attributes. So given this to start:

            <ice:dataPaginator for="testTable" 
                               id="myPaginator"
                               fastStep="2"
                               paginator="true"
                               paginatorMaxPages="3">

If I then remove the last 3 attributes:

            <ice:dataPaginator for="testTable" 
                               id="myPaginator">

However removing one attribute at a time doesn't help. If any of those 3 attributes are provided, the same problem occurs. So it looks like the component is having a decoding problem of some kind. Since the 3 that I removed are actually Strings (but ints and boolean), it may be related to an issue with the type it's expecting. I'll have to try one of our own compat portlet examples to see if the same issue exists there.

So this appears to be a problem with the LiferayFaces Bridge. I've discussed this with the developer and he is going to take a look at it. I'll link to the issue in the Liferay system when it's available.

It turns out that the bridge has some fixes for ICE-6398 that directly impact the ice:dataPaginator component. During our discussion, we tried running one of Liferay's working sample portlets that uses the ice:dataPaginator ( http://www.liferay.com/community/liferay-projects/liferay-faces/demos#icefaces3-directory-portlet). In addition to code changes that impact the component, Liferay also provides a composite component tag for using the paginator. You can see how this is done by downloading and looking at the code in the linked example. The heart of the matter can be found in the directory.xhtml file:

<liferay-ui:ice-page-iterator for="users"/>

Using the composite component, you can also add the desired attributes without causing the problem:

<liferay-ui:ice-page-iterator for="users" paginator="true" fastStep="2" paginatorMaxPages="3"/>

If you switch the example to use an ice:dataPaginator directly, the problem manifests:

<ice:dataPaginator for="users" paginator="true" fastStep="2" paginatorMaxPages="3"/>

So while Liferay looks to fix the problem in the bridge, a valid workaround would be to use the composite component provided by Liferay. This basically means adding the LiferayFaces Portal library (https://www.liferay.com/community/liferay-projects/liferay-faces/portal) to the project and changing the paginator markup to what I've noted above.

Corresponding issue in Liferay's tracking system:

http://issues.liferay.com/browse/FACES-1482

Since the issue is likely to be correct in the next LiferayFaces Bridge release and the current workaround provided is reasonable, I'm resolving this as Won't Fix.

Mistake. This shouldn't be resolved until we can verify the fix in the LiferayFaces Bridge. Re-opening and lowering priority for now.

Resolving as Won't Fix. The documented workarounds are considered to be sufficient for dealing with the problem.