Weblog

Today I continue with a pattern where business objects can be logically deleted and restored by using the 'restorable' pattern. Different from the 'trash bin' pattern in part 1 this pattern is based on booleans expressing the state of an object, either logically deleted or not. Both patterns are non-historical. In addition Restorable covers also a mechanism to process business class specific logic before an object is logically deleted (trashed).

Recycling objects... trashing them and then restoring them... as often as your users want. Here comes 'trash bin', a pattern for non-historical, logical deletion based on associations. Probably this is the first UML pattern ever protecting our environment. ;-)