Thanks Ludovic for making this precise, I was under the exact same impression but feared I failed to know a newer technique. Composite objects (I think that's the practice here) is how sub-classing has been done in Curriki where, for example, attachments-assets are a special type of assets, with even more special types being zip archives, and SCORM packages. All these are just "added details" Curriki has also leveraged the custom-class feature, when an asset extends Document, and has implemented commodity methods based on that (e.g. "get the start resource of the zip"). Paul Le 26 août 2012 à 10:32, Ludovic Dubost a écrit :
You can use a contact object inside a page with a customer object. This not exactly inheritance but it looks like it
Envoyé de mon iPhone
Le 25 août 2012 à 19:39, Boudjelda Mohamed Said <[email protected]> a écrit :
Hi Every body I have to create an application upon XWiki, I have a this model , Person -> Contact (Person is a Contact ) and Also Customer - > Contact , How can I make such implementation using XWiki Classes