29 Nov
2005
29 Nov
'05
6:03 p.m.
Yep, that's true. MAClassDescription expects a
class. I have
never put a single description into a
MASingleOptionDescription yet, so I didn't encouter this problem yet.
I don't know, but I would try
descriptionProject
^(MASingleOptionDescription selector: #project label: 'Project'
priority: 10)
reference: TMProject description;
options: (MADynamicObject on: [ TMProject repository
asArray]);
beRequired; beSorted ;
yourself
Else a possibility might be to create a new description, say
a null- object pattern MAUnknownDescription that wouldn't
validate the referenced object.
That solution works well, thanks much. Though, I do want to mention,
it's always bothered me that you chose description as an accessor for
getting at the metaModel, since description is probably one of the most
used accessors to put onto a domain object, along with name. I think
description is too generic and useful a term to use it as an extension
to the instance side of Object, what do you think?