Home » Modeling » UML2 » Unable to add required property 'event' in ExecutionOccurrenceSpecification
Unable to add required property 'event' in ExecutionOccurrenceSpecification [message #478324] |
Thu, 23 April 2009 19:47 |
Eclipse User |
|
|
|
Originally posted by: florianwendland.freenet.de
Hey all,
i've found a bug, when i played a bit with interactions. The Validator
(and even the spec) recommend, that an ExecutionOccurrenceSpecification
had to declare a required property 'Event', which is possibly an
Receive/SendOperationEvent. So i've set it, and this causes an
IllegalArgumentException. Here is the relevant trace:
java.lang.IllegalArgumentException:
org.eclipse.uml2.uml.internal.impl.ReceiveOperationEventImpl @6a9b28
(name: RecvEvt9, visibility: <unset>)
at
org.eclipse.uml2.uml.internal.impl.ExecutionOccurrenceSpecif icationImpl.setEvent(ExecutionOccurrenceSpecificationImpl.ja va:177)
at
org.eclipse.uml2.uml.internal.impl.ExecutionOccurrenceSpecif icationImpl.eSet(ExecutionOccurrenceSpecificationImpl.java:3 08)
at
org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjec tImpl.java:1071)
at org.eclipse.emf.edit.command.SetCommand.doExecute(SetCommand .java:721)
at
org.eclipse.emf.edit.command.AbstractOverrideableCommand.exe cute(AbstractOverrideableCommand.java:131)
at
org.eclipse.emf.common.command.BasicCommandStack.execute(Bas icCommandStack.java:84)
at
org.eclipse.emf.edit.provider.ItemPropertyDescriptor.setProp ertyValue(ItemPropertyDescriptor.java:1427)
at
org.eclipse.uml2.uml.editor.presentation.UMLEditor$UMLProper tySource.setPropertyValue(UMLEditor.java:1917)
at
org.eclipse.ui.views.properties.PropertySheetEntry.valueChan ged(PropertySheetEntry.java:782)
at
org.eclipse.ui.views.properties.PropertySheetEntry.setValue( PropertySheetEntry.java:723)
at
org.eclipse.ui.views.properties.PropertySheetEntry.applyEdit orValue(PropertySheetEntry.java:146)
at
org.eclipse.ui.views.properties.PropertySheetEntry$1.applyEd itorValue(PropertySheetEntry.java:103)
at org.eclipse.jface.viewers.CellEditor$1.run(CellEditor.java:3 33
HTH
Marc-Florian
|
|
| |
Re: Unable to add required property 'event' in ExecutionOccurrenceSpecification [message #478327 is a reply to message #478325] |
Thu, 23 April 2009 21:53 |
Eclipse User |
|
|
|
Originally posted by: florianwendland.freenet.de
Well, that's true. I thought, that the event, to which an
ExecutionOccurrenceSpecification (EOS) points to, is the Event
(CallEvent, SendEvent, MessageEvent etc.) that starts the execution or
stops it....
So, what is an ExecutionEvent (EE)? It starts and stops an
ExecutionSpecification (ES), but this is exact the same meaning of EOS.
So, when i want to express, that an ES starts by retrieving a message
via MessageOccurrenceSpecification (MOS), i have no chance to combine
the MOS with an EOS. But this should be possible, because an EOS points
out, that an ES starts. Therefore, it should be possible to reference
not only EE but any kind of Event like MessageEvents.
By creating a structure like this:
MOS_1 {event:SendOperationEvent, m1:Message}
Message{name:m1}
MOS_2 {eventA:ReceiveOperationEvent, m1:Message}
EOS_1 {event->MOS_2, execution:ExectionSpecification}
ES {name:execution, start->EOS_1, finis->EOS_2}
EOS_2 {event->MOS4, execution:ExectionSpecification}
MOS_4 {eventA:SendOperationEvent, m2:Message}
Message{name:m2}
MOS_1 {event:ReceiveOperationEvent, m2:Message}
one could get any corelated information of the trace. But may be, i
missinterpret the meaning of ExecutionEven.
Marc-Florian
James Bruck schrieb:
> The spec mentions .. "... to be restricted to an execution event". I'm
> guessing that the event you are trying to set on the
> ExecutionOccurrenceSpecification is not an ExecutionEvent.
>
> - James.
>
>
> "Marc-Florian Wendland" <florianwendland@freenet.de> wrote in message
> news:gsqgdk$9u5$1@build.eclipse.org...
>> Hey all,
>>
>> i've found a bug, when i played a bit with interactions. The Validator
>> (and even the spec) recommend, that an ExecutionOccurrenceSpecification
>> had to declare a required property 'Event', which is possibly an
>> Receive/SendOperationEvent. So i've set it, and this causes an
>> IllegalArgumentException. Here is the relevant trace:
>>
>> java.lang.IllegalArgumentException:
>> org.eclipse.uml2.uml.internal.impl.ReceiveOperationEventImpl @6a9b28 (name:
>> RecvEvt9, visibility: <unset>)
>> at
>> org.eclipse.uml2.uml.internal.impl.ExecutionOccurrenceSpecif icationImpl.setEvent(ExecutionOccurrenceSpecificationImpl.ja va:177)
>> at
>> org.eclipse.uml2.uml.internal.impl.ExecutionOccurrenceSpecif icationImpl.eSet(ExecutionOccurrenceSpecificationImpl.java:3 08)
>> at
>> org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjec tImpl.java:1071)
>> at org.eclipse.emf.edit.command.SetCommand.doExecute(SetCommand .java:721)
>> at
>> org.eclipse.emf.edit.command.AbstractOverrideableCommand.exe cute(AbstractOverrideableCommand.java:131)
>> at
>> org.eclipse.emf.common.command.BasicCommandStack.execute(Bas icCommandStack.java:84)
>> at
>> org.eclipse.emf.edit.provider.ItemPropertyDescriptor.setProp ertyValue(ItemPropertyDescriptor.java:1427)
>> at
>> org.eclipse.uml2.uml.editor.presentation.UMLEditor$UMLProper tySource.setPropertyValue(UMLEditor.java:1917)
>> at
>> org.eclipse.ui.views.properties.PropertySheetEntry.valueChan ged(PropertySheetEntry.java:782)
>> at
>> org.eclipse.ui.views.properties.PropertySheetEntry.setValue( PropertySheetEntry.java:723)
>> at
>> org.eclipse.ui.views.properties.PropertySheetEntry.applyEdit orValue(PropertySheetEntry.java:146)
>> at
>> org.eclipse.ui.views.properties.PropertySheetEntry$1.applyEd itorValue(PropertySheetEntry.java:103)
>> at org.eclipse.jface.viewers.CellEditor$1.run(CellEditor.java:3 33
>>
>> HTH
>> Marc-Florian
>
>
|
|
| |
Re: Unable to add required property 'event' in ExecutionOccurrenceSpecification [message #627516 is a reply to message #478325] |
Thu, 23 April 2009 21:53 |
Eclipse User |
|
|
|
Originally posted by: florianwendland.freenet.de
Well, that's true. I thought, that the event, to which an
ExecutionOccurrenceSpecification (EOS) points to, is the Event
(CallEvent, SendEvent, MessageEvent etc.) that starts the execution or
stops it....
So, what is an ExecutionEvent (EE)? It starts and stops an
ExecutionSpecification (ES), but this is exact the same meaning of EOS.
So, when i want to express, that an ES starts by retrieving a message
via MessageOccurrenceSpecification (MOS), i have no chance to combine
the MOS with an EOS. But this should be possible, because an EOS points
out, that an ES starts. Therefore, it should be possible to reference
not only EE but any kind of Event like MessageEvents.
By creating a structure like this:
MOS_1 {event:SendOperationEvent, m1:Message}
Message{name:m1}
MOS_2 {eventA:ReceiveOperationEvent, m1:Message}
EOS_1 {event->MOS_2, execution:ExectionSpecification}
ES {name:execution, start->EOS_1, finis->EOS_2}
EOS_2 {event->MOS4, execution:ExectionSpecification}
MOS_4 {eventA:SendOperationEvent, m2:Message}
Message{name:m2}
MOS_1 {event:ReceiveOperationEvent, m2:Message}
one could get any corelated information of the trace. But may be, i
missinterpret the meaning of ExecutionEven.
Marc-Florian
James Bruck schrieb:
> The spec mentions .. "... to be restricted to an execution event". I'm
> guessing that the event you are trying to set on the
> ExecutionOccurrenceSpecification is not an ExecutionEvent.
>
> - James.
>
>
> "Marc-Florian Wendland" <florianwendland@freenet.de> wrote in message
> news:gsqgdk$9u5$1@build.eclipse.org...
>> Hey all,
>>
>> i've found a bug, when i played a bit with interactions. The Validator
>> (and even the spec) recommend, that an ExecutionOccurrenceSpecification
>> had to declare a required property 'Event', which is possibly an
>> Receive/SendOperationEvent. So i've set it, and this causes an
>> IllegalArgumentException. Here is the relevant trace:
>>
>> java.lang.IllegalArgumentException:
>> org.eclipse.uml2.uml.internal.impl.ReceiveOperationEventImpl @6a9b28 (name:
>> RecvEvt9, visibility: <unset>)
>> at
>> org.eclipse.uml2.uml.internal.impl.ExecutionOccurrenceSpecif icationImpl.setEvent(ExecutionOccurrenceSpecificationImpl.ja va:177)
>> at
>> org.eclipse.uml2.uml.internal.impl.ExecutionOccurrenceSpecif icationImpl.eSet(ExecutionOccurrenceSpecificationImpl.java:3 08)
>> at
>> org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjec tImpl.java:1071)
>> at org.eclipse.emf.edit.command.SetCommand.doExecute(SetCommand .java:721)
>> at
>> org.eclipse.emf.edit.command.AbstractOverrideableCommand.exe cute(AbstractOverrideableCommand.java:131)
>> at
>> org.eclipse.emf.common.command.BasicCommandStack.execute(Bas icCommandStack.java:84)
>> at
>> org.eclipse.emf.edit.provider.ItemPropertyDescriptor.setProp ertyValue(ItemPropertyDescriptor.java:1427)
>> at
>> org.eclipse.uml2.uml.editor.presentation.UMLEditor$UMLProper tySource.setPropertyValue(UMLEditor.java:1917)
>> at
>> org.eclipse.ui.views.properties.PropertySheetEntry.valueChan ged(PropertySheetEntry.java:782)
>> at
>> org.eclipse.ui.views.properties.PropertySheetEntry.setValue( PropertySheetEntry.java:723)
>> at
>> org.eclipse.ui.views.properties.PropertySheetEntry.applyEdit orValue(PropertySheetEntry.java:146)
>> at
>> org.eclipse.ui.views.properties.PropertySheetEntry$1.applyEd itorValue(PropertySheetEntry.java:103)
>> at org.eclipse.jface.viewers.CellEditor$1.run(CellEditor.java:3 33
>>
>> HTH
>> Marc-Florian
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 26 03:30:01 GMT 2024
Powered by FUDForum. Page generated in 0.03899 seconds
|