Whatever you want to call it, I'm advocating that something "like
DataView" be packaged officially with Wicket. If we can agree on that,
it's a start.
Going further, I do think there should be an official way to integrate
with Hibernate. The "why" is that it would save a lot of people a lot of
trouble.
Nathan
Igor Vaynberg wrote:
DataView is not really a database related project. Sure, it started out
because of a need to display database data, but it has no database-related
code in it. It is a project for generating components with repeating bodies
from datasources other then java.util.List. Look at the wicket-phonebook
example I checked in, there is absolutely no database code anywhere in the
ui-layer (wicket), so why do we need projects that integrate databases and
wicket?
-Igor
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Nathan Hamblen
Sent: Tuesday, October 11, 2005 1:56 PM
To: [email protected]
Subject: [Wicket-user] Re: Standard for database integration?
(Please!)
DataView itself is a good example of the need for database
and UI integration (even its name.). Without something
similar pulled into wicket.extensions, novice Wicket
programmers are left to solve a pretty tricky problem right
off: how do I make a ListView fill from the database without
wasting all kinds of memory?
It turns out that this problem has been solved, in various
ways, in various contributed packages, but finding those
packages and deciding between them is time consuming. Some
things you can download, others you have check out from the
paralyzingly slow anon cvs server, and then who knows which
examples are the most up-to-date or even relevant which db
interface you picked...
Learning a new framework is hard enough without all that
detective work.
Nathan
Igor Vaynberg wrote:
What does a standard db integration entail?!? What will it provide?
Why do we need to integrate the database layer with the ui layer -
arent we skipping the whole middle layer??
You don't need wicket-contrib-data* packages to write a database
driven wicket app, infact, for me those packages present nothing
useful and nothing that makes it any easier to access the database.
Here is a very simple architecture:
Use spring (or any other container) to create your middle layer and
manage all the database stuff (closing/opening session, etc). Have
wicket pull out services objects out of the spring context and use
them to manipulate data in the database. Done.
-Igor
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,
discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmp
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
