Don't invoke @Initialize methods when building jobs. But introduce a @Validate annotation for "thin" initialization and validation.

[kasper]

Initialization methods are very frequently invoked in DataCleaner because of the interactive UI, which refreshes the job every time a property value changes.

To cater for such a scenario we should rather have two degrees of initialization: Validation (which is what the UI needs) and actual initialization (should be guaranteed to only be invoked once for a job! And be symmetrical to @Close methods).

So: Introduce a @Validate annotation for this and make use of it for all repeatable and lightweight initializations.

[kasper]

Releasing with AnalyzerBeans 0.10.