Wicket2

Hi,

there a significant amount of wicket things at this point. Next step is to complete forms. Right now all the logic works for editing/adding/deleting/validation, but the forms have only a description field and validation "validate" and return errors, but there are no specific validation types in place.
Also, the system is correct in accepting or not some operations, but it doesn't cope with generic state transitions yet (e.g.: it offers add/obsolete/edit/supersed, but not validate, pre-validate etc.).
While the system should already cope with labels and the like (also with some sort of "semantic" ordering for properties), this is not really visible/testable with the current dataset.
So...
next step is actually to re-wire the command line and change large part of configuration as to have properties, states, transitions, labels etc. all configurable. So next iteration (wicket3) despite the name, will not be really about wicket.