Hello Bogdan and Tom!
Could you make sure that this kind of information is entered in the Cookbook
in the description of the Model subsystem (or that the Cookbook is corrected
w.r.t. this kind of information)?
/Linus
2007/7/12, Bogdan Ciprian Pistol <[EMAIL PROTECTED]>:
>
> Hi
>
> I've discovered what is happening with the events and what are the
> valid values for property names.
>
> In the case of the DeleteInstanceEvent, it's simple, it just uses the
> "remove" property name.
>
> AttributeChangeEvent is instantiated like this:
> AttributeChangeEvent(source, propertyName, oldValue, newValue,
> originalEvent)
> - propertyName can have any value that represents an attribute of the
> "source" UML element.
> - newValue is the changed value of that attribute
>
> Add/RemoveAssociationEvent is instantiated like this:
> Add/RemoveAssociationEvent(source, propertyName, oldValue, newValue,
> changedValue, originalEvent)
> - propertyName is the name of the Association End owned by the "source"
> element
> - oldValue is null for a AddAssociationEvent and is the Type of the
> AssociationEnd for a RemoveAssociationEvent
> - newValue is null for a RemoveAssociationEvent and the Type of the
> AssociationEnd for a AddAssociationEvent
> - changedValue is non-null, either newValue or oldValue
>
> If I'm wrong please ping me.
>
> So, the problem now is to test if the propertyNames for Association
> Ends and attributes of elements are the same in MDR and Eclipse UML2.
>
> Bogdan,
>
> On 7/11/07, Bogdan Ciprian Pistol <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > I have some trouble understanding what are the valid property names of
> > the ModelEventPump.
> >
> > Here is what I investigated so far (please notify me if I'm wrong):
> >
> > The ModelEventPump notify it's listeners on only 4 kinds of events
> changes:
> > DeleteInstanceEvent, AttributeChangeEvent, RemoveAssociationEvent and
> > AddAssociationEvent.
> >
> > DeleteInstanceEvent uses the source UML element (the notifier) and a
> > property name (a string)
> > that in some parts of ArgoUML is expected to be "remove" and in other
> > parts it doesn't matter it's value, the only test done is if the event
> > is instance of DeleteInstanceEvent.
> >
> > AttributeChangeEvent is initialized with the source UML element, a
> > property name, old and new values. The propery name can have very
> > different values like: "name", "isAbstract", "isActive",
> > "isRoot", "isLeaf", "isSpecification", "visibility", "multiplicity",
> > "ownerScope", "changeability",
> > "targetScope" and maybe other values. (I extracted these values while
> > debugging).
> >
> > RemoveAssociation and AddAssociation events (from the MDR
> > implementation source code) doesn't give me clues how should be used
> > because the AssociationEvent (from MDR) has no source code or javadoc.
> > The events are using AssociationEvent#getNewElement(),
> > AssociationEvent#getEndName(), AssociationEvent#getFixedElement(),
> > which I do not know what are doing.
> >
> > The main problem for me are the valid values for property names.
> >
> > Bogdan,
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
