Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Junilu Lacar
  • Martin Vashko
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Scott Selikoff
  • salvin francis
  • Piet Souris

Wicket in Action: Question

 
Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Martijn & Eelco!
Welcome to Java Ranch. Its nice to see a book written on Wicket framework.
I'm new to Wicket, so got a few questions.

1. How different is Wicket from Struts?
2. Is it useful for enterprise applications or only web applications?
3. How much time will it be necessary to master Wicket?

Thanks and Regds,

Sridhar Palla
 
Ranch Hand
Posts: 471
Mac OS X Hibernate Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Palla,

Let me answer the first two questions. As for the first one, wicket is a component-based framework (more like JSF and tapestry) while struts is request based. To make this more clear, traditional request-based MVC frameworks (like struts), the controller works in the terms of whole requests and whole pages. It is also responsible for pulling the data out of the model to populate the view. In the case of wicket, the wicket components more resemble the stateful self contained widgets (like the ones in swing GUI). The components use listener delegates to listen to GET and POST requests the same way swing components listen to events (clicks and key strokes)

As for your second question, IMHO, web frameworks are best for the web, and that's it. Most enterprise applications nowadays have a web presentation layer, but a good design mandates that your enterprise business logic should be separated in POJOs so that if you need to change wor presentation layer, database layer or integration layer (the one that integrates your application with other backend systems), you will not be in a large mess.
 
Alaa Nassef
Ranch Hand
Posts: 471
Mac OS X Hibernate Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
OK, as for your 3rd question, Martijn answered a similar one here
 
We can walk to school together. And we can both read this tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!