2012 Aug. 21

Outage

There was an outage today (Aug. 21st) lasting from about 9:20 AM to 11:20 AM. Since the server wasn’t reachable during that time I’m still not sure, about the cause of this but it looks like the whole virtual server was down. I hope to resolve this later but I haven’t heared from my hoster until now. Right now, the machine is back online and running.

I apologize for any inconvenience caused by this outage.

2012 Jul. 26

It happened again - Plain-text passwords stolen

Today another case of criminal grade thoughtlessness made the (german) IT news. The on-line dating platform meetOne was found to grant access to data like “childrenNumber”, “schooling”, “yearlyIncome”, “sexuality” and “searchOneNightStand” or the plain-text password along with the matching email address of everyone to anyone who was able to change a single URL-Parameter. This change was a simple increase or decrease of a number not some fancy CrossSiteScripting-style JavaScript- or math-voodoo.

2012 Jul. 04

It's been a slow month

It’s been a slow month for CRUDr in June. With some days off, more work at my day job and other distractions, there wasn’t much in terms of accomplishment for the project. First steps were made for filtering, sorting and validating data and some tiny steps in terms of a demo application.

2012 Jun. 14

Don't you hate it when your UnitTests break?

UnitTests are great. Period. This fact has been established among developers. It helps to make sure your new code doesn’t break anything else. It gives you regression testing “for free” and it can even be used as a design method (Test Driven Development). But tests break and they don’t only break when code changes and new bugs are introduced to the system. They might break more or less on their own, when they aren’t properly written. This causes work since you’ll have to find out why this test is broken. Did you just break the feature under test or was the test just to fragile? was it you or was it the developer of the test?

2012 May. 03

A slight case of over-engineering

When I set out to create Wicket-CRUD, I envisioned a small and lightweight set of components that would deliver all the basic scaffolding options to Wicket. Right now I’m not so sure about the lightweight-part. I’s still a small set of components (a table-component, an editor, some Annotations and an Interface) with a small API. I don’t know when I started on the path of over engineering but I think right now I’m committed to it (at least for this project). Two collumn-types collectiong their various parts to provide all the functionality from several providers created by a couple of factories, kept together (and apart) by no less than 8 Interfaces… All in all the project contains some 50 code-files and it’s still growing.