Half user config and half client prog implemented

I have a Leave type that represents a kind of employee leave (eg holiday,
sick etc)
The app I'm writing may end up at any company, so I need to have the leave
types configurable throught the app. I'll do this for simple types that
just require a unique labeling. But other types maybe more complex and
require some bespoke algorithm on a per company basis. So I'll implement an
interface for each of these special types.
I'm using Hibernate for the ORM.
I'm thinking at the moment to have a persisted PLeaveType with a ClassName
attribute so that this base persisted type may be wrapped by the Class
denoted. Usually in the case of the user configured simple leave this will
be just some generic implementation. But with the special types there will
be a specific class to instantiate.
Does this sound like a decent plan?

--
Mike W


.