Pure Blood Nigerian: Sometimes Technological. Other times I plead the ignorance amendment

Bean Validation Made Simple With JSR 303

2011-12-02T13:22:00.000+01:00

JSR 303 (Bean Validation) is the specification of the Java API for JavaBean validation in Java EE and Java SE. Simply put it provides an easy way of ensuring that the properties of your JavaBean(s) have the right values in them. This post aims to show you how to use the Bean Validation API in your project.

To begin, imagine that you were building the next Facebook and you would need member(s) to register to use your application. In order to successfully register, prospective member(s) have to provide the following: a last name, a first name, a gender, an email address and a date of birth. In addition, the individual who is registering must be between 18 and 150 years inclusive.

Prior to JSR 303, you probably would have needed a bunch of if-else statements to achieve the above requirements. Thankfully, not any more.

We will begin by creating a JavaBean named 'Member' that would hold all the properties we are interested in.

01 package validationapiblog.model;
02 
03 import java.util.Date;
04 import validationapiblog.enums.Gender;
05 
06 /**
07  *
08  * @author Adedayo Ominiyi
09  */
10 public class Member {
11 
12     private String lastName = null;
13     private String firstName = null;
14     private Gender gender = null;
15     private String emailAddress = null;
16     private Date dateOfBirth = null;
17 
18     public Member() {
19     }
20 
21     public String getFirstName() {
22         return firstName;
23     }
24 
25     public void setFirstName(String firstName) {
26         this.firstName = firstName;
27     }
28 
29     public Gender getGender() {
30         return gender;
31     }
32 
33     public void setGender(Gender gender) {
34         this.gender = gender;
35     }
36 
37     public String getLastName() {
38         return lastName;
39     }
40 
41     public void setLastName(String lastName) {
42         this.lastName = lastName;
43     }
44 
45     public Date getDateOfBirth() {
46         return dateOfBirth;
47     }
48 
49     public void setDateOfBirth(Date dateOfBirth) {
50         this.dateOfBirth = dateOfBirth;
51     }
52 
53     public Integer getAge() {
54         if (this.dateOfBirth != null) {
55             // calculate age of member here
56         }
57         return null;
58     }
59 
60     public String getEmailAddress() {
61         return emailAddress;
62     }
63 
64     public void setEmailAddress(String emailAddress) {
65         this.emailAddress = emailAddress;
66     }
67 }

Java2html

The gender property is a simple enum and is shown below

1 package validationapiblog.enums;
2 
3 /**
4  *
5  * @author Adedayo Ominiyi
6  */
7 public enum Gender {
8     MALE, FEMALE;
9 }

Java2html

Now that we have the pieces to the puzzle. The next step is to download an implementation of JSR 303. For this post we would be using the reference implementation namely Hibernate Validator. The version as at the time this post was written is 4.2.0 Final. After downloading it you should add the following 4 jars to the classpath of your project:

hibernate-validator-4.2.0.Final.jar
hibernate-validator-annotation-processor-4.2.0.Final.jar
slf4j-api-1.6.1.jar
validation-api-1.0.0.GA.jar

Once this is done, you simply annotate the 'Member' JavaBean we created earlier to indicate which properties need be validated. You can annotate either the fields or the accessor (or getter) methods of the JavaBean. In this post I will be annotating the accessor methods.

01 package validationapiblog.model;
02 
03 import java.util.Date;
04 import javax.validation.constraints.Max;
05 import javax.validation.constraints.Min;
06 import javax.validation.constraints.NotNull;
07 import javax.validation.constraints.Past;
08 import javax.validation.constraints.Pattern;
09 import org.hibernate.validator.constraints.Email;
10 import org.hibernate.validator.constraints.NotBlank;
11 import validationapiblog.enums.Gender;
12 
13 /**
14  *
15  * @author Adedayo Ominiyi
16  */
17 public class Member {
18 
19     private String lastName = null;
20     private String firstName = null;
21     private Gender gender = null;
22     private String emailAddress = null;
23     private Date dateOfBirth = null;
24 
25     public Member() {
26     }
27 
28     @NotNull(message = "First name is compulsory")
29     @NotBlank(message = "First name is compulsory")
30     @Pattern(regexp = "[a-z-A-Z]*", message = "First name has invalid characters")
31     public String getFirstName() {
32         return firstName;
33     }
34 
35     public void setFirstName(String firstName) {
36         this.firstName = firstName;
37     }
38 
39     @NotNull(message = "Gender is compulsory")
40     public Gender getGender() {
41         return gender;
42     }
43 
44     public void setGender(Gender gender) {
45         this.gender = gender;
46     }
47 
48     @NotNull(message = "Last name is compulsory")
49     @NotBlank(message = "Last name is compulsory")
50     @Pattern(regexp = "[a-z-A-Z]*", message = "Last name has invalid characters")
51     public String getLastName() {
52         return lastName;
53     }
54 
55     public void setLastName(String lastName) {
56         this.lastName = lastName;
57     }
58 
59     @Past(message = "Date of Birth must be the past")
60     @NotNull
61     public Date getDateOfBirth() {
62         return dateOfBirth;
63     }
64 
65     public void setDateOfBirth(Date dateOfBirth) {
66         this.dateOfBirth = dateOfBirth;
67     }
68 
69     @Min(value = 18, message = "Age must be greater than or equal to 18")
70     @Max(value = 150, message = "Age must be less than or equal to 150")
71     public Integer getAge() {
72         if (this.dateOfBirth != null) {
73             // calculate age of member here
74         }
75         return null;
76     }
77 
78     @NotNull(message="Email Address is compulsory")
79     @NotBlank(message="Email Address is compulsory")
80     @Email(message = "Email Address is not a valid format")
81     public String getEmailAddress() {
82         return emailAddress;
83     }
84 
85     public void setEmailAddress(String emailAddress) {
86         this.emailAddress = emailAddress;
87     }
88 }

Java2html

Please note that these are just some of the annotations available in JSR 303. In addition Hibernate Validator introduces a few of its own that are not in the specification. Feel free to study the annotations not in this post in your free time you might find something interesting. There is also the ability to create your own custom validator if the need arises. Now lets review the annotations used:

@NotNull - Checks that the annotated value is not null. Unfortunately it doesn't check for empty string values
@Pattern - Checks if the annotated string matches the regular expression given. We used it to ensure that the last name and first name properties have valid string values
@Past - The annotated element must be a date in the past.
@Min - The annotated element must be a number whose value must be greater or equal to the specified minimum
@Max - The annotated element must be a number whose value must be lower or equal to the specified maximum
@NotBlank - Checks that the annotated string is not null and the trimmed length is greater than 0. This annotation is not in JSR 303
@Email - Checks whether the specified string is a valid email address. This annotation is also not in JSR 303

To test the validation we could use a unit test as shown below.

package validationapiblog.test;

import java.util.Set;
import javax.validation.ConstraintViolation;
import javax.validation.Validation;
import javax.validation.Validator;
import javax.validation.ValidatorFactory;
import validationapiblog.model.Member;
import org.junit.Test;
import static org.junit.Assert.*;

/**
 *
 * @author Adedayo Ominiyi
 */
public class ValidationAPIUnitTest {

    public ValidationAPIUnitTest() {
    }

    @Test
    public void testMemberWithNoValues() {
        Member member = new Member();

        // validate the input
        ValidatorFactory factory = Validation.buildDefaultValidatorFactory();
        Validator validator = factory.getValidator();
        Set<ConstraintViolation<Member>> violations = validator.validate(member);
        assertEquals(violations.size(), 5);
    }
}

Java2html

In conclusion, you should experiment with JSR 303 and see for yourself which annotations you like. Thank you and have fun.

Gender Equality: A Noble but Flawed Cause

2011-09-21T10:23:00.002+01:00

Disclaimer: This post is strictly about gender equality and not about women rights. I am in no way an advocate of beating women, mutilating their genitals or any other inhumane acts against them. I love women (in a can’t live with them, can’t live without them way). In addition if the following does not apply to you or you don’t agree. Instead of bashing me with words you can kindly tell us how you or your life is different and create a learning experience for the rest of us.

The ideology behind gender equality advocacy is “It doesn’t’ matter what your gender is, we are equal in everything”. That is, no gender stereotyping. That is the ideal; now let us discuss the reality.

To start with I will make the bold claim that “In today’s world, most women are guilty of gender stereotyping”. You will see what I mean shortly.

I always thought that the goal of any anti- (such as anti-racism, anti-tribalism, anti-genderalism (if that is even a word) and so on) was to walk (or work) under the guise that the factor that gave rise to the “-ism” in the first place did not exist (such as a black man being black or a white man being white). Wouldn’t it be a cool sight when a white man can say to a black man in a truly race-equal environment “Hey black man do you want to go get a drink” and the black man replies without taking offence “Sure white boy I would love to”. Of course this kind of dialogue should have taken place before they exchange names if not it would be stupid. But I digress. Today’s write-up asks the question, why is it that when most women want to get you to do something you don’t want to do or can’t do they always use 1 of the following 2 statements (They are particularly used when money is involved):

You don’t love me (if you are in a relationship or trying to get into one with her)
Are you not a man?

The former I will skip for today. The latter is the one of interest. WTF (kids please close your ears), I thought the whole gender equality thing was so that we stop such gender stereotyping.

It is amazing how the same gender of human beings can go from saying “What a man can do a woman can do better” to saying something as contradicting as “Are you not a man?” all in the same 24 hour clock. Interesting isn’t it? In the first statement, she is strong and superhuman and in the second statement she suddenly became the weak and helpless victim. I don’t know if I should call this hypocrisy, vacuousness or mental manipulation. Wouldn’t it be a truly gender equal world when a man can say to a woman “You sleep on the couch while I sleep in the bed”. Without the man hearing a cliché “You are not even a gentleman”. More gender stereotyping in action if you ask me. Seriously what happened to my fundamental human right and free will to choose to say no or yes when I want to. I am not sure if you see where I am going with this.

My response is simple. Real men can see through this act. The only men who fall for it are babies, wankers or have less testosterone than the rest of us. Nobody is trying to disrespect you or not help out when we can. But when a man says he can’t do something, he can’t. Let it go. Well I pity the fool who falls victim of this lame act and ends up dead in a bid to please a selfish woman. I rest my case.

Playing with a DBMonster

2010-09-25T10:40:00.025+01:00

I recently had the privilege of using DBMonster when I needed to generate some random test data for a MySQL database. What I am about to demonstrate is a simple use of the DBMonster tool.

The SQL statement for the simple table used in this writeup is as follows (of course you will have to create a database first):

CREATE TABLE person (
id int not null auto_increment,
last_name varchar(45) not null,
first_name varchar(45) not null,
gender varchar(6) not null,
date_of_birth date not null,
PRIMARY KEY (id)
);

Note that, the SQL statement is for MySQL only although if you remove the auto_increment statement it should work for your database.

Now that we are all set we can start to use DBMonster. The simplest way to start is by using DBMonster to reverse engineer the database table and generate a schema for itself. Then you can tweak the schema to your satisfaction.

To start (you will need access to the JDBC Driver for your database):
a) Download DBMonster and unzip. I will call this directory "<DBMonster_Home>".
b) In the <DBMonster_Home> directory, create a file call "dbmonster.properties". In this file insert the following (each on a separate line):
dbmonster.jdbc.driver=com.mysql.jdbc.Driver
dbmonster.jdbc.url=jdbc:mysql://localhost:3306/<database_name>
dbmonster.jdbc.username=<username>
dbmonster.jdbc.password=<password>
c) When this is done, launch the command prompt and navigate to the <DBMonster_Home> directory, at the command prompt type the following (without the inverted commas):
"java -classpath ../mysql-connector-java-5.1.6-bin.jar;dbmonster-core-1.0.3.jar pl.kernelpanic.dbmonster.Launcher -c dbmonster.properties --grab -o dbmonster-schema.xml"
d) A Schema file called "dbmonster-schema.xml" should have been generated for you. We will be making some changes to this file.

Note: Do not close the command prompt we will be reusing it later

The changes we will be making in the dbmonster-schema.xml file are:
a) We will reduce the number of rows to 50 unless you have the time to wait for 1000 entries
b) For the last_name and first_name fields, spaces should not be allowed. We will change that.
c) It makes no sense for gender to be anything other than Male or Female. Fortunately, DBMonster has a DictionaryGenerator we can use for this.

To proceed,
a) Open the dbmonster-schema.xml file in your favorite XML editor.
b) Look for <table name="person" rows="1000"> and change to <table name="person" rows="50">
c) Also look for <column name="last_name" databaseDefault="false">. Within this tag, there should be a <property name="allowSpaces" value="true"/> change that to <property name="allowSpaces" value="false"/>. Repeat this for the <column name="first_name" databaseDefault="false"> tag.
d) Create a file called "gender_dictionary.txt" in the <DBMonster_Home> directory and put the following in it (each on a separate line)
Male
Female
e) In the dbmonster-schema.xml file, replace the entire <column name="gender" databaseDefault="false"> tag withe the following:
<column name="gender" databaseDefault="false">
<generator type="pl.kernelpanic.dbmonster.generator.DictionaryGenerator">
<property name="unique" value="false"/>
<property name="dictFile" value="gender_dictionary.txt"/>
</generator>
</column>

We have finished with the dbmonster-schema.xml file. To generate the test data run the following at the command prompt (without the inverted commas):
"java -classpath ../mysql-connector-java-5.1.6-bin.jar;dbmonster-core-1.0.3.jar pl.kernelpanic.dbmonster.Launcher -s dbmonster-schema.xml -c dbmonster.properties"

Do not hesitate to visit the DBMonster Homepage to learn more.

Enjoy.

All Religion is Flawed

2010-09-18T15:17:00.005+01:00

Yes, you read that right "All Religion is Flawed". The goal of any religion is to portray the "Worshipped" of the chosen religion in a perspective that is far superior to the "worshipped" of alternative religions. And yet no one asks where all these chaos originated from. I was speaking to a guy the other day whose religion borders on the principle that the individual in his religion is God. That you made (or make) the decision of where you are now (or need to be) from where you have been (in terms of being born). So I asked him "Are you saying I have been here (the world) before?". He said "Yes". Then I said "Are you saying I chose to come back here (the world)?". He said "Yes". So I said to him "Wake up. It doesn't make any sense why would I choose to come back to this sh*t hole if I have already been here before. And on top of that to be my own God I will have to be all-knowing, all-powerful and all-seeing". He said "You are". Then I replied "That means that all of us in this world are our own Gods". He said "We are". Damn, talk about a classic case of "too many cooks spoil the broth". Imagine one billion plus (1, 000, 000, 000+) all-knowing, all-powerful and all-seeing Gods working around on this earth for their individual, selfish reasons. Talk about Chaos.

This isn't written in order to take a swipe at anyone's religion. I just got tired of listening to all the "Come and worship my God" or "My God is the shiznit" nonsense.

I don't know a lot of what I expect from a religion but here are a few things that I know and believe:

a) I am not God. Simply because I don't know it all, I don't see it all and I can't do it all
b) It is not possible for any human being (flesh and blood) to be God (same reason as (a))
c) There is a God. Simply because it takes creativity to create something as interesting as this world. The air I breathe, the water I drink, the food I eat, the women I see and so on. Its all perfect except for one (1) thing "chaos"
d) It is clear that there is good and there is evil. And both definitely do not like one another.
e) Human beings love to receive good things or things that make us feel good all the time (a promotion, lovely gifts, a check in the mail, a beautiful wife, a pretty girlfriend, a loving husband, a caring boyfriend, a cool car, a nice house, a tasty meal, a good hair do and so on. The list is endless). Which means we clearly lean towards good in our receiving but in our giving that's another story (the classic shades of gray symptom).

To summarize, a good-loving intelligent God created this world and created human beings to live in it. Note that I have reserved the use of the words: all-knowing, all-seeing and all-powerful to describe this God. Why did I say "good-loving"? Simply because I do not think that an "evil-loving" God will create beings who constantly love to receive good things. Evil likes evil, Good likes good. So it seems only natural that their offsprings would like what their parents like (at least on the receiving side of things).

Now the question arises "How did a good-loving God create something (or someone) that loves to receives good things all the time but on the giving side of things, it (he/she) can give either good or evil?". Good question. Unfortunately, I don't know the answer to that. If I did I would be all-knowing (you see my point).

However a few possibilities come to mind:
a) A fundamental flaw in the design (or in computer speak, a bug in the programming). If this is true it would definitely undermine the perception of an all-knowing God that many religions proclaim. I hope you now see why I reserved the word "all-knowing" to describe the God that created this world.
b) The design was done intentionally (or on purpose). Now this one is interesting. Why? Simply because it would mean good created something that could please evil. Maybe good has a crush on evil (pun intended). Reminds me of high school. This would definitely grant credibility to the "free-will" concept of some religions.

In summary, if it was a flaw in the design then why hasn't it been fixed all these thousands of years later. Does it mean that the Creator doesn't care or simply doesn't mind that evil festers. Or does it simply mean the Creator cannot fix it. That would mean the Creator is not "all-powerful" as some would have us believe. On the other side of things, if it was a purposeful design why is it a criminal gets punished for using his/her design feature. That is, if the feature is there and it is used is it valid to consider it a crime. "I wonder, I really wonder". The same applies to religions with an "after-life" concept. Either way you will get punished for evil whether it was the Creator's design fault that the ability to do evil was there in the first place or whether you exercised your "free-will" in doing the evil. Both ways you are screwed.

In conclusion, I am hoping you see why I began by saying "All Religion is Flawed". They all say the same thing "Follow me if you want to see the light". Unfortunately, there is no light at the end of all their tunnels. My advice, if you like receiving good so much, others like it as well so you should try as much as possible to give out as much good as you can on a daily basis (or their might be a shortage of good in the world).

Thank you, have a nice day and may the Creator (whoever that may be) be with you all. (Pun intended).

EJB Unit testing with OpenEJB 3.1.2 and Netbeans 6.8 (again without Maven)

2010-04-27T19:29:00.005+01:00

I recently became interested in researching the possibility of unit-testing my Enterprise JavaBeans (EJBs) 3.0. This led me to look at OpenEJB. Upon my journey through the OpenEJB documentation, I found that there were many examples at the OpenEJB Download page. However these examples are based on the Maven way of doing things and although it was possible to run them in Eclipse it wasn't so easy to do the same in Netbeans as I was offline when I was trying the examples (quite frankly my Maven skills is down there with my graphics skills (that is, almost non-existent)).
After reading through the simple-stateless unit test example I decided to try and run it in my Netbeans 6.8, it went well so I decided to document it for others who might be interested. Btw, my operating system (OS) is Windows Vista but I believe this should work on any OS that supports Java.

The first steps are (duh):
a) Download and Install Netbeans 6.8
b) Download the OpenEJB Standalone Server (openejb-3.1.2.zip) and the OpenEJB Examples (openejb-examples-3.1.2.zip) from the OpenEJB website.

If you have done that launch Netbean 6.8 and
a) Choose New Project... from the menu.
b) Choose Java from the Categories list and select Java Application from the Projects list. Click on the Next button
c) Enter simple-stateless as the Project Name and click the Finish button
d) In the Projects explorer to your left, right-click on the Source Packages and choose New->Java Package... (if you don't see the Java Package... option choose Other... and look under the Java Categories list)
e) Enter org.superbiz.calculator as the Package Name and click Finish
f) Again, right-click on the Test Packages and choose New->Java Package...
g) Enter org.superbiz.calculator as the Package Name and click Finish
h) Again, right-click on the Source Packages and choose New->Folder (if you don't see the Folder option choose Other... and look under the Other Categories list)
i) Enter META-INF as the Folder Name and click Finish.
j) Unzip the OpenEJB Examples zip file that you downloaded and look inside the directory. You will see a directory called simple-stateless. Enter that directory and navigate to src->main->java->org->superbiz->calculator. Select all the Java files (namely: CalculatorImpl.java, CalculatorLocal.java and CalculatorRemote.java), copy (Ctrl+C) and paste it into Netbeans by first selecting the org.superbiz.calculator package of the Source Packages that you created, right-click and choose Paste (Ctrl+V)
k) Return to the simple-stateless directory and navigate to src->main->resources->META-INF. Copy the ejb-jar.xml file and paste it into Netbeans in the META-INF folder you created earlier.
l) Return again to the simple-stateless directory and navigate to src->test->java->org->superbiz->calculator. Copy the CalculatorTest.java file and paste it into Netbeans by first selecting the org.superbiz.calculator package of the Test Packages that you created, right-click and choose Paste.
m) Unzip the OpenEJB Statndalone Server that you downloaded. Go back to Netbeans and select Libraries from the Projects explorer. Right-click and choose Add Library...
n) Select Create... from the Add Library dialog box that appears. Enter OpenEJB as the Library Name in the Create New Library dialog box and click Ok.
o) Ensure that the Classpath tab is selected from the Customize Library dialog and click Add JAR/Folder. Navigate to the unzip OpenEJB Standalone Server and open the lib directory. Choose all the JAR files in the lib directory and click the Add JAR/Folder button of the Browse JAR/Folder file chooser.
p) Click Ok to close the Customize Library dialog box.
q) Make sure the OpenEJB library is selected from the Available Libraries of the Add Library dialog and click the Add Library button

That is all that is required. Now all you have to do is choose the CalculatorTest.java from the Test Packages, right-click and choose Run File (Shift+F6) and watch your test fail spectaculously. Cool isn't it.
Now right-click on the simple-stateless project and choose Clean and Build. When this is done, choose the CalculatorTest.java file and Run File again.
Now the unit test should pass.

Hope this wasn't too long. As I learn more I will definitely post it. Thanks

Hello World Wicket Development without the Maven burden

2009-08-13T17:15:00.034+01:00

For most of us in Nigeria (this does not apply to the privileged few) learning a new technology nowadays is usually a challenge. Imagine a situation where I am trying to learn how to use a technology like Tapestry 5 or Wicket for the first time and having to pick up another technology like Maven. Don't get me wrong Maven is cool (hope the Ant people are not annoyed. Ant is cool too).

Okay I was in my little room feeling happy that I had just downloaded the Wicket 1.4 stable release using a free connection (I don't have one at home don't ask why) and I would like to try it out with its support for generics among others. I open up my Eclipse 3.4.0 and then I remember what happened when I first used Wicket 1.3 (refer to the Wicket Quickstart if you don't know what I am blabbing about). No Maven on this computer and no Internet. Damn. Hence this post was written to teach you how to use Wicket without relying on Maven. Read on if you are interested.

This post assumes that you are familiar with Java, Eclipse (with the Java EE perspective) and that you have downloaded Wicket 1.4. Your Eclipse environment should also have been setup to run on a server like Apache Tomcat 6.

These are the basic steps:
a) In your Eclipse IDE start a new Dynamic Web Project (name the project HelloWorldWicket)

b) Unzip your Wicket download to anywhere you like (for example, C:\apache-wicket-1.4.0)

c) Navigate to the lib folder under the the folder where you unzipped Wicket and copy the file named wicket-1.4.0.jar to the WEB-INF/lib of your Eclipse project.

d) Create 2 Java class files HelloWorldApplication.java and HelloWorld.java under the package helloworld (copy and paste the code for these files from this post)

e) Create an html file called HelloWorld.html and place it in the sample package folder as the HelloWorld.java (copy and paste the code for this file from this post)

f) Copy and paste the code for the web.xml file from this post and replace the WEB-INF/web.xml file in your eclipse project.

g) If you try to run the project now your will get an error java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory. The tricky part starts now

h) Navigate to the lib folder under the the folder where you unzipped Wicket. You will see a file called wicket-examples-1.4.0.war. Use the jar command to unzip the WEB/lib folder (for those that do not know the command is "<path_to_java_jdk_installation>/bin/jar -xvf <path_to_unzipped_wicket>/wicket-examples-1.4.0.war WEB-INF/lib" without the curly braces). The files we are interested in are called log4j-1.2.13.jar, slf4j-api-1.4.2.jar and slf4j-log4j12-1.4.2.jar. Copy these files to the WEB/lib of your Eclipse project and run the application. You should now see a nice Hello World by navigating your browser to http://localhost:8080/HelloWorldWicket/

Hope this post is useful. As I promised the code for this post is found below.

HelloWorldApplication.java




package helloworld;

  

import org.apache.wicket.Page;    

import org.apache.wicket.protocol.http.WebApplication;



public class HelloWorldApplication extends WebApplication {

    

    @Override     

    public Class getHomePage() {       

        return HelloWorld.class;     

    }   

}        
      Java2html

HelloWorld.java




 package helloworld;     



import org.apache.wicket.markup.html.WebPage; 

 import org.apache.wicket.markup.html.basic.Label;     



public class HelloWorld extends WebPage {  

     

    public HelloWorld() {       

        add(new Label("message", "HelloWorld"));     

    } 

}        
      Java2html

HelloWorld.html

<html>
<body>
<span wicket:id="message" id="message" />
</body>
</html>

web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="HelloWorldWicket" version="2.5">
<display-name>HelloWorldWicket</display-name>
<filter>
<filter-name>HelloWorldApplication</filter-name>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class>
<init-param>
<param-name>applicationClassName</param-name>
<param-value>helloworld.HelloWorldApplication</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>HelloWorldApplication</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
</web-app>

My First Post - Fun and Supposedly Meaningless

2009-07-27T17:57:00.007+01:00

Thank God it seems I am finally able to post something. Awesome... I wasn't sure what it should be so I decided to practice with this somewhat meaningless writeup. Not much for my first post right.
Some of my posts may be tutorial-style while others may be just random babbling. When they do seem like random babbling take note that I have probably been overworked and I am probable just letting off some steam.
I am hoping that some of my posts will be useful to some people just as the posts of others have been useful to me (the 80-20 rule).
Have fun.....