But instead of changing existing class, i think, it will be better if we create a custom auxiliary class.
On Wed, Jan 29, 2014 at 2:44 PM, Michael Ströder <firstname.lastname@example.org> wrote:
Vikas Parashar wrote:Using 'extensibleObject' is really bad practice.
> Yes, that should be. Because, you are using two structural class from
> different chain.
> Instead of account class, please use extensibleObject.
Hint: One can easily define custom structural object classes adding the
Also object classes can be derived from two other object classes.
SUP ( inetOrgPerson $ account )