use GWT because thats the key difference between wicket and gwt
I only see some things like validators that could be precompiled not th
complete webapp and all your current page/panel/component/html code
On Wed, Oct 22, 2008 at 3:44 PM, cowwoc [EMAIL PROTECTED] wrote:
Hi,
I'd like to
because on the server the business logic runs
Its a complete different paradigm
if thinks that are now done in onclick() or onsubmit() would run on the
client
what would be possible then? Currently many people just call DAO's there
(spring stuff and so on)
johan
On Thu, Oct 23, 2008 at 11:40
so write a prototype and present it to the community. we are all eyes.
-igor
On Thu, Oct 23, 2008 at 2:40 PM, cowwoc [EMAIL PROTECTED] wrote:
GWT generates business logic, HTML and CSS from Java code; as opposed to
letting you bind business logic written in Java against normal HTML files.
It
Johan,
I'm not saying you should move *everything* over to the client. I'm saying
that most form manipulation can take place without querying the database,
especially on a per-request basis. Adding rows and cell validation tend to
rely on at most one database lookup (during the initial request).
I just to clarify one point. You would still have three types of components:
HTML
CSS
Java
You would still be binding the Java code against HTML IDs (clean separation
of concerns). The only thing that would change is where the Java code
executes.
--
View this message in context:
