Refactor the test harness to remove the duplications and make it more readable.

There is the bug with the term update mechanism.
The update method was wrongly implemented needs to be fixed.

Got the walking skeleton and at least 2 use cases.
Should start thinking about moving to a cleaner architecture.

Try to first decouple the persistence layer.
Do latter the UI.

Review the code and see if you can replace some of the code specially loops with the functional library totally lazzy.

The terms are not displayed correctly in the UI, the width of the panel srinks.
This is probably because the word break mechanism is not working fine.

For some reason the input text area does permit the user to continue typing after 400 characters. This should be fixed

Decided to do programmatic registration rather than configuring a security realm in the application server. The registration mechanism is not yet fully implemented and it is prone to bugs very easily. Add more testing around it and also investigate how it affects to the session management mechanism once is implemented(not yet implemented).

I started to decouple but the modules remain tight coupled.
Starting from the domain, try to isolate the services and push out the dependencies.

Currently the project is not functional.
I shoulda made a branch before attempting such a big refactor(Am stupid!)

In the UI there is a problem. All the definitions(max 400 chars) are displayed in one line. This shouldn't be like this. Add some system line breaks and do a bit of css to make that text look petter.

Add a bit of css to make the UI look a bit decent(It looks horrible now).