All,
I have woodstock tables rendering ok in a seam ajax4jsf environment but action not working. Any quick pointers ?
I have the javascript / dojo includes ..
From firebug look like evens are being triggered ok but table not updating, even basic sort functionality.
Note I am backing by Objectdataprovider per Dans blog /example
Apologies if wrong forum , but figured you guys are the experts.
Rgds,
Padraig.
----- Original Message ----
From: Winston Prakash <Winston.Prakash@Sun.COM>
To: dev@woodstock.dev.java.net
Sent: Thursday, August 16, 2007 3:52:50 PM
Subject: Re: DataProviders, JPA and Tables
Hi Lilianne,
If you are interested in using JPA with woodstock component, these two
articles may be useful
http://www.netbeans.org/kb/60/web/web-jpa.html
http://www.netbeans.org/kb/60/web/web-jpa-part2.html
- Winston
http://blogs.sun.com
> Lilianne E. Blaze wrote:
>> Hello,
>> Either they're designed for something else entirely, or I'm missing
>> something :/
>> Consider the following scenario: a table with a list of users. Suppose
>> it's up to 10.000 users, and it's page size is 25. Each row contains
>> some basic data, plus some data which is calculated as needed and has to
>> be done on object-by-object basis.
>> Now, if I got it right, a "normal" DataProvider would require to get
>> everything from a db, then sort it, then provide only the current 25. Is
>> that correct?
>>
>
> If you're working with CachedRowSetDataProvider, that should cache
> data for rows currently in view. However, there are other types of
> providers that do not require a database. For example, you could use
> an ObjectArrayDataProvider or ObjectListDataProvider. (There are
> several examples in the TLD docs for TableRowGroup, which are hosted
> live.) You can even bind a List or Object array directly to the table;
> although, these "normal" providers require all data to be present.
>
>> After reading the source I believe I can write, relatively easy, a
>> DataProvider which, for example, when asked for 26th object lazily loads
>> objects 25-50, doing sorting and limiting to page size on JPA's
>> entityManager, while never actually containing more than visible at the
>> moment. But I'm feeling I'm reinventing the wheel here, there should be
>> support for such scenario, and I just can't see it. What am I missing
>> here?
>>
> John Baker responded to a 8/13 thread, labeled "Woodstock table with
> Seam", which has links to Dataprovider information. Did you check that
> out?
>
> Dan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@woodstock.dev.java.net
> For additional commands, e-mail: dev-help@woodstock.dev.java.net
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@woodstock.dev.java.net
For additional commands, e-mail: dev-help@woodstock.dev.java.net