Frank Maritato wrote:
So, displaytag is a pretty interesting taglib.
It is very nice, I use it a lot!
Does it need to have the
entire dataset, or can it use an action/controller to lazy load the information from a datasource (or ejb, or web service, etc.) ?
View layer does not deal with data of course, that is for the model.
Of course to implement a good model, one should know some SQL. (Doing a good view, one should know CSS, or JavaScript, etc. )
Some DAO's, such iBaits, have pagination. (and caching; also iBatis can return a List, and .... displaytag needs a List. How nice.)
Lazyloading might help in some cases in Java, but it would not help you in SQL/Data side.
SQL works on sets (set theory, right; intersections, unions, etc. Read up on Celko) and server side and client side cursors are slow and non scaleable. A given DB engine compiles the querry, selects a path, executes the path with joins, sorts the result and then send it out(this last part you want to be faster?).
Some DB engines, such as pgSQL offers support for SELECT . . . LIMIT/OFFSET, so you can get to the 3rd set of 1000 records from your result set.
Depending of the DB engine you use, I would ask in the DB forum, since "row by row loading" (what I think you wanted) is same in C lang as it would be in Java. (CLI, OCI, etc.)
I do have a google like example of doing this in a "good practice" example open source app. bP,
If data access is slow for you, I would stress test that layer/module.
View should present the collection in a paginated way, but after you have some data.
hth, .V
Vic Cekvenich wrote:
Here is an example of something I do a lot of w/Struts: http://displaytag.sf.net
(that Matt contributed to)
You can click on examples link (uper right) to see nested, pagination, etc.
Using your skill and experience you listed, can you show something similar?
.V
Kito D. Mann wrote:
At 11:20 AM 10/9/2003 -0500, you wrote:
I watched a presentation on JSF last night. Here's my high-level impressions:
1. It's a replacement for Struts (no matter what folks say).
It may be in the long-term, but it won't be in version 1.0. I think the combination of the two is pretty powerful.
2. It's basically Swing for the Web.
True.
3. It's more difficult than Struts.
I think it might be more difficult for people who haven't worked with desktop-oriented GUI frameworks like Swing, Delphi's VCL, or Visual Basic OCXs (and likewise .NET). Once you get used to a more component-oriented approach, it's a lot more efficient. Most of the people I know who develop complex desktop GUIs with tools like Delphi feel that the servlet development is a step backwards, even with great frameworks like Struts. I also think that JSF will be easier to swallow than Swing, but that's based on my limited Swing experience (I've done a lot more Delphi desktop development than Swing).
Anyway, that's my two cents, as someone who's familiar with JSF and has also worked with Struts, ASP.NET WebForms, and tools like Delphi.
This topic has been beat to death all over the place; you can find out more on my site, JSFCentral.com. There's a FAQ there that addresses some Struts/Faces questions.
Kito D. Mann Author, JSF in Action
Basically, I'm not impressed. I think they're going to have do a lot to
make it easier to learn and easier to develop with. It seems that a lot of
"Experts" are touting that it'll be easy to develop because it's a
*standard* and IDEs will support it. I'll believe it when I see it
considering I still use HTML editors to edit JSPs and JSTL (because Homesite
is still the best JSP editor IMO).
Read more at http://tinyurl.com/qbyk.
These are just my opinions - so take them with a grain of salt.
Matt
-- Victor Cekvenich, Struts Instructor (215) 312-9146
Advanced Struts Training <http://basebeans.com/do/cmsPg?content=TRAINING> Server Side Java training with Rich UI, mentoring, designs, samples and project recovery in North East. Simple best practice basic Portal, a Struts CMS, Membership, Forums, Shopping and Credit processing, <http://basicportal.com> software, ready to develop/customize; requires a db to run.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
