DZone
Java Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Java Zone > Not A Java Web Frameworks Survey: Just use Wicket!

Not A Java Web Frameworks Survey: Just use Wicket!

Peter Karussell user avatar by
Peter Karussell
·
Jul. 14, 10 · Java Zone · Interview
Like (0)
Save
Tweet
10.69K Views

Join the DZone community and get the full member experience.

Join For Free

‘Java Web Frameworks Survey’ was my first blog posted which was reposted at dzone. Sadly there never was a follow up of it. Although I planned followups with jZeno, SpringMVC, Seam, Vaadin (at that time: IT-Mill Toolkit), MyFaces, Stripes, Struts, ItsNat, IWebMvc

Now, today I have just a short, subjective mini-follow-up, for anyone who is interested after all those months. Over the months I have additionally investigated JSF, Rails, Vaadin and one more:

  • No comments to JSF :-/
  • Rails is great! Especially the db migrations and other goodies. Partials are a crap: I prefer component based UI frameworks. If you don’t like ruby take a look at grails with autobase.
  • Additionally I highly recommend everyone to take a look at vaadin (‘server-side GWT’) if you need a stateful webapplication. Loading time was a problem for me. Other client-side performance problems can be solved if you use CssLayout, I think.

But for jetwick I chose wicket! There were/are 10 reasons:

  • great performance,
  • ease of use (highly subjective, of course),
  • component based + no routing,
  • good documentation and active community,
  • ajax fallback and simplicity,
  • quick get-started,
  • out-of-the-box back-button support,
  • integrated testing support,
  • unbeaten separation of html and Java code
  • and a simple guice integration

The most important thing is: if you use ‘mvn jetty:run’ and NetBeans in combination then the development cycle feels like Rails: modify html, css or even Java code. Save and hit F5 in the browser. Nothing more.

The only problem is the database migration (wicket solves only the UI problems). For that I would use liquibase. Or simply run db4o, a nosql solution ‘or’ solr.

From http://karussell.wordpress.com/2010/07/13/not-a-java-web-frameworks-survey-just-use-wicket/

Framework Java (programming language)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Implementing One and Two Way SSL (Mutual Authentication) for MuleSoft Application
  • Conducting Sprint Retrospective Meetings
  • Augmented Analytics: The Future of Business Intelligence
  • CSS Position: Relative vs Position Absolute

Comments

Java Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo