Skip to main content

How To Do Pagination Similar in Google?

Suppose you've got 1000 records in a requestScope list or map called data:
<display:table name="data" scope="request" id="record">
<display:column title="Title 1" property="property1"/>
</display:table>



and so on... There's a manual also. And you can provide the size of the page, the styles, an url to lin on each column. You can render a column by yourself or make it to autolink if the column is an url or emailaddress...



Check the examples, they tell you how to do the whole thing. Also I'll cut'n' paste here a real code of my own for you to see. It's embeded in a struts based application. See the pagesize and requestURI wich will help you do the paging. The requestURI should store the data in an attribute called "listaContactos" in scope session. I just store the data when a search is requested, the pagination is done by the displaytag so if the user don't changes the search criteria the list is the same as in the previous page but just shows up the next 10 records... hope to have explained, sorry my bad english:


<<
<display:table sort="list" name="listaContactos"
scope="session" id="contacto"
requestURI="/secret/gestion/buscarContactos/view.do" pagesize="10"
align="center" width="400px">
<display:setProperty name="basic.msg.empty_list">
<p align="center">
No hay resultados para la búsqueda.
</p>
</display:setProperty>
<display:column title="Nombre"
sortable="true"

url="/secret/gestion/editarContacto.do?accion=editar"
paramId="key"
paramProperty="contactoId">
<bean:write name="contacto"
property="apellido1"/>&nbsp;<bean:write name="contacto"
property="apellido2"/>, <bean:write name="contacto"
property="nombre"/>
</display:column>
<logic:match name="buscarContactosForm"
property="contactoEmpresa" value="true">
<display:column title="Cargo"
property="cargo"
sortable="true"

url="/secret/gestion/editarContacto.do?accion=editar"
paramId="key"
paramProperty="contactoId"
group="15"/>
<display:column title="Empresa"
property="nombreEmpresa"
sortable="true"

url="/secret/gestion/editarEmpresa.do?accion=editar"
paramId="key"
paramProperty="empresaId"
group="15"/>
</logic:match>
<display:column title="Tel&eacute;fono"
property="tlf1" width="60px"/>
</display:table>

>>

Comments

Popular posts from this blog

Asynchronous Vs. Synchronous Communications

Synchronous (One thread):   1 thread -> |<---A---->||<----B---------->||<------C----->| Synchronous (multi-threaded):   thread A -> |<---A---->| \ thread B ------------> ->|<----B---------->| \ thread C ----------------------------------> ->|<------C----->|

WebSphere MQ Interview Questions

What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. What is Message driven process? Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. What are advantages of the MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How does it support the Integration? Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform What is Asynchrony? Ans. With messag...

Advantages & Disadvantages of Synchronous / Asynchronous Communications?

  Asynchronous Communication Advantages: Requests need not be targeted to specific server. Service need not be available when request is made. No blocking, so resources could be freed.  Could use connectionless protocol Disadvantages: Response times are unpredictable. Error handling usually more complex.  Usually requires connection-oriented protocol.  Harder to design apps Synchronous Communication Advantages: Easy to program Outcome is known immediately  Error recovery easier (usually)  Better real-time response (usually) Disadvantages: Service must be up and ready. Requestor blocks, held resources are “tied up”.  Usually requires connection-oriented protocol