Posts Tagged Tutorial

Wicket Tutorial, part 9 – storing and loading user preferences from cookies

Tags: ,

In the previous post we learnt a few tricks regarding internationalization features in Wicket. Today we will go further and will let application to remember some user preferences using HTTP Cookies. Storing some basic data in cookies is an easy and popular way of letting user customize look and feel of web application he uses very often. Some portals use cookies to render modules in order chosen by user so that most interesting information are in the top.

In our ItemDirectory web application we don’t have (yet!) any sophisticated mechanism which could rely on cookies so we will show how it can be used to store and load language selected by the user.

Continue reading this post …


Be Sociable, Share!

Wicket Tutorial, part 8 – adding internationalization support

Tags: , , , ,

Today we will continue Wicket tutorial series with adding support to multiple languages in web application. Ok, let’s do it step by step.

Create form to change language

To make our changes visible and testable at the beginning we add form to change application language. To make it more reusable we will implement it as a Wicket panel.
So first, let’s create html and Java files:

Continue reading this post …


Be Sociable, Share!

Wicket Tutorial, part 7 – editing and removing item locations

Tags: , ,

Welcome back to our practical Wicket tutorial series. I apologize for long break after last post (shame on me as it was published more than 1,5 month ago) but I had many unplanned things with higher priority: Wicket demo appplication  on 33rdDegree conference to prepare, a conference itself and most time-consuming one, I damaged knee ligament during football match and after that everyday for three weeks I was driving to the hospital for rehabilitation so day became too short to write something here. But now everything seems to be ok and I have some spare time to continue Wicket tutorial subject.

Today we will add two new features: editing and removing locations from our application. Currently we don’t have any items connected with locations so deleting shouldn’t be too complicated. Later on, when we add some items, we will have to rework this functionality but now it shouldn’t bother us too much.

Continue reading this post …


Be Sociable, Share!

Wicket tutorial series – building web application from scratch

Tags: , ,

This post aggregates the  series of Wicket tutorial articles from this blog. But as this tutorial is still not finished and new posts will be published in the near future, please return here again to find new parts or (simpler) just add my RSS to your reader.

Wicket tutorial series

    1. Wicket Tutorial, part 1 – setting up project with Spring 3, JPA 2 and MySQL

    2. Wicket Tutorial, part 2 – adding common layout to the project

    3. Wicket Tutorial, part 3 – first form in our application

    4. Wicket Tutorial, part 4 – custom validator for unique entity name

    5. Wicket tutorial, part 5 – generic unique entity validator

    6. Wicket Tutorial, part 6 – listing locations in a simple manner

    7. Wicket Tutorial, part 7 – editing and removing item locations

 

 

You might also be interested in post Wicket – useful links with other good tutorials, presentations and tools I found useful while learning and using Wicket.


Be Sociable, Share!

Wicket Tutorial, part 6 – listing locations in a simple manner

Tags: , , ,

Today we will add simple listing view for locations added to the database in previous posts.  I said ‘simple’ as there are some more sophisticated ways to show many items using Wicket but probably we will not have many locations to show in our application so simple view without pagination should be ok. More complicated way (DataTable component) will be covered in the future when we will add ‘listing items’ feature’.

Continue reading this post …


Be Sociable, Share!

Wicket tutorial, part 5 – generic unique entity validator

Tags: , , ,

As I promised in the previous post, today we will focus on transforming our unique name validator in Wicket to generic one. So now, let’s simply list what we are going to achieve;

  • validator should validate any entity object in our project
  • validator should check unique value of any property from validated object
  • error message should be generic too but customization should be easy

Continue reading this post …


Be Sociable, Share!