Where is pe:paginator?

[djmj]

I am using v 2.0.

Where is pe:paginator?

[sudheer]

It was removed long time back itself.

http://forum.primefaces.org/viewtopic.php?f=14&t=25394

[djmj]

Hmm bad news, I will check if i can get the source.

Defining paginator within datatable itself is not a elegant solution and creates very much boiler-plate markup. Especially if you have a generic DAO.

PF should provide <p:paginator> itself.

You know what was the latest version it was available?

[sudheer]

I think it was available in PFExt 0.6.x version.By the way why it will create boiler-plate markup for generic DAO etc.

[djmj]

Thanks will search it and build my own from it source if possible.

By the way why it will create boiler-plate markup for generic DAO etc.

Because i have like 20+ datatables with identical markup using a generic DAO class that inherits from LazyDataModel:

Code: Select all

<p:dataTable var="entity" value="#{bean.dao}" 
	rows="10" rowKey="#{entity.id}" selection="#{entity.selEntity}" selectionMode="single"
	paginator="true" paginatorPosition="bottom" pageLinks="1" paginatorAlwaysVisible="false"
	paginatorTemplate="#{msg.tablePaginatorTemplate}" emptyMessage="#{msg.noRecordsFound_u}">

    <!-- content -->
</p:dataTable>

Which could easily be reduced to:

Code: Select all

<p:dataTable var="entity" value="#{bean.dao}" 
	rows="10" rowKey="#{entity.id}" selection="#{bean.dao.selEntity}" selectionMode="single">
    <!-- content -->
    <comp:paginator dao="#{bean.dao}"/>
</p:dataTable>

[sudheer]

This is bit a rare use case.But you can confirm with Oleg/Thomas whether any chances to port it back.

[kukeltje]

This is bit a rare use case

It is not, I have an identical 'issue'. Did not try to use a custom component for the datatable yet since that would 'reduce' markup to

[tandraschko]

Exactly, it's really not that rare.
I have this problem with multiple components - like a pe:inputNumber specially configured for EURO.
I would always need to add ~5 attributes on the tag - thats annoying.

Currently i just derive the component class and overwrite the getter/statehelper#get call with my default value.

[kukeltje]

@Thomas: is there a reason you did not create a (reusable) composite component but went for overriding a java class?

[tandraschko]

IMO its easier as replicate every component attr in the cc:interface section.
But i just done it for our company internal framework and only for such a global component - otherwise i use composites too.