| Re: [mdt-papyrus.dev] emf validation in Papyrus |
Dear Nicholas, I'm not very happy using the internal function, I principally wanted to avoid to duplicate code that is already present. For additional constraints, we use the standard EMF extension point, i.e. in the moment I do not see a need to customize the EValidatorAdapter. => could it be made a non-internal function? The alternative is to create a minimal EValidatorAdapter in Papyrus. Btw. I also use the internal Modisco class LinkItem in function tryChildIfEmpty() of class ValidationTool: in order to know, if it should be decorated with a marker, I need to know the EObject of the childs. => is there a cleaner way to get the information about the childs? => if not, could LinkItem be made non-internal? Have a Merry Christmas and a Happy New Year! Ansgar -----Original Message----- From: mdt-papyrus.dev-bounces@xxxxxxxxxxx on behalf of Nicholas Pacini Sent: Wed 12/22/2010 4:18 PM To: mdt-papyrus.dev@xxxxxxxxxxx Subject: [mdt-papyrus.dev] emf validation in Papyrus dear all, In the current version of Papyrus i noticed that you are using an internal class of MoDisco in order to check user-defined rules based on the emf.validation.constraintProviders extension point. I was wondering, if possible, if you intend to keep this implementation or if you are going to develop a custom EValidatorAdapter within Papyrus in order to add other constraints without touching a MoDisco plugin. thanks in advance, best regards, Nicholas _______________________________________________ mdt-papyrus.dev mailing list mdt-papyrus.dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
<<winmail.dat>>