--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Another person and I are starting to add support for requires and
policySets attributes to the various elements in the model. One possible
direction we are considering is to have those model objects that
support requires and policySets attributes extend the
PolicyAttachableModel object. To this object a method would be added to
handle extracting the requires and policySets attributes and would save
them. Another option would be to have an instance of a
PolicyAttachableModel object in each of the model objects that support
the requires and policySets attributes. Does the community have a
preference for either of these options or have a suggestion for another
option? During the build phase the attributes would be processed from
the model. This is where the reduction and checking for conflicts would
take place. Methods would be added to AbstractSCAObject to add/get
intents and policsySets.This would make it so that the various
implementations of the model would inherit them.
- requires and policySets attribute support Mark I. Dinges
- Re: requires and policySets attribute support Jeremy Boynes
- Re: requires and policySets attribute supp... Jim Marino
- Re: requires and policySets attribute ... haleh mahbod
- Re: requires and policySets attrib... Jeremy Boynes
- Re: requires and policySets attrib... Jim Marino
- Re: requires and policySets a... haleh mahbod
- Re: requires and policySets attribute support Mark I. Dinges
- Re: requires and policySets attribute supp... Jean-Sebastien Delfino
- [Spec related] @Requires on interfaces... Jean-Sebastien Delfino
