My guess is, we could need a best practices/blueprint codebase for such
cases,
my idea is, to have various preimplemented datamodels, which utilize the
most popular frameworks by using different resource management
techniques (Page preloading by caching, Servlet interceptors, Spring,
PhaseChangeListeners ...)
This would be a perfect usage for the Wiki and Sourceforge, also maybe
for Shale (Craig are you reading) :-)
Also the Oracle guys could donate such a best practice for their ORM
mapper :-D
Werner
Jesse Alexander (KBSA 21) wrote:
-----Original Message-----
I have a system that access data by oracle stored
procedures.
My team decided that data must be paginated on
database to avoid excessive web server memory usage.
So, stored procedures receive a given page as
parameter and return records based on that page.
-----/Original Message-----
Sort of what I expected ;-)
Because something similar had occurred to me when
designing our company's power-table.
I think the best way will be to use the DataModel approach.
Basically you would override the methods
- abstract public int getRowCount()
-> if oracle can deliver this number even on a
paginable table
- abstract public Object getRowData()
-> obvious
- abstract public boolean isRowAvailable()
-> This is the most important to get the datatable to
continue to request data...
At least that was what I immagined would be a feasable way:
some sort of paginable datamodel.
-----Original Message-----
I was trying to do that writing a custom
javax.faces.model.DataModel... but it appears hard...
-----/Original Message-----
Ain't that heavy...
hope this helps
Alexander
