| Why are some features not changeable ? [message #475890] |
Fri, 14 September 2007 09:20  |
Eclipse User |
|
|
|
I wonder why some UML2 features are not changeable, esp.
uml::Port.provided
uml::Port.required
uml::StructuredActivityNode.input
uml::StructuredActivityNode.output
Perhaps thats the reason, why I cannot make a "provided" relationship
between a Port and an Interface in a UML2Tools Component diagram.
Any idea?
|
|
|
|
|
|
| Re: Why are some features not changeable ? [message #476008 is a reply to message #475912] |
Wed, 19 September 2007 04:58  |
| Eclipse User |
|
|
|
Originally posted by: nickkirtley.gmail.com
hi,
by the way: it is possible to add a provided interface to a port in the
component diagram. It's the required interface that doesn't work on it.
Just select provided interface, click on port and drag to somewhere, let
go and select a new interface, or drag it to an existing interface.
Or you can select the port (in the uml2 tree editor) and select it's type
- select the interface you wish to provide.
nick
|
|
|
| Re: Why are some features not changeable ? [message #624784 is a reply to message #475890] |
Fri, 14 September 2007 09:44 |
| Eclipse User |
|
|
|
Port.required and Port.provided are derived collections ( that is, the
collection is computed based on other information ) which is why you cannot
add to them directly.
To actually add a provided interface to a port you could type the port with
an interface, or type it with a classifier that has an interface realization
to some interface. If you were then to cal Port#getProvideds() you would
obtain the interface.
If you search this newsgroup you will find several other postings on this
topic.
Cheers,
- James.
"exquisitus" <supert24@gmx.net> wrote in message
news:fce1q1$7cv$1@build.eclipse.org...
> I wonder why some UML2 features are not changeable, esp.
>
> uml::Port.provided
> uml::Port.required
> uml::StructuredActivityNode.input
> uml::StructuredActivityNode.output
>
> Perhaps thats the reason, why I cannot make a "provided" relationship
> between a Port and an Interface in a UML2Tools Component diagram.
>
> Any idea?
>
>
>
|
|
|
|
| Re: Why are some features not changeable ? [message #624805 is a reply to message #475900] |
Mon, 17 September 2007 11:01 |
| Eclipse User |
|
|
|
StructuredActivityNode is a bit of a strange bird and may have issues as it
is described in the superstructure specification.
There is no subsetting property for the input/output derived unions defined
on Action.
Input and output pins would be added to the "nodes" collection but calling
getInputs() or getOutputs() would result in empty lists ( a mistake in my
humble opinion ).
Concrete subtypes of StructuredActivityNode have overriden subsetting
properties. Take ConditionalNode for example, the results list contributes
to the list of output pins.
In short, if you are not working with a subtype of StructuredActivityNode,
you won't be able to add to the collection of inputs/outputs. You will have
to add your pins to the list of nodes.
Cheers,
- James.
"exquisitus" <supert24@gmx.net> wrote in message
news:fcfrrs$7hb$1@build.eclipse.org...
> Do you also now how to set uml::StructuredActivityNode.input/output ?
|
|
|
| Re: Why are some features not changeable ? [message #624821 is a reply to message #475912] |
Wed, 19 September 2007 04:58 |
| Eclipse User |
|
|
|
Originally posted by: nickkirtley.gmail.com
hi,
by the way: it is possible to add a provided interface to a port in the
component diagram. It's the required interface that doesn't work on it.
Just select provided interface, click on port and drag to somewhere, let
go and select a new interface, or drag it to an existing interface.
Or you can select the port (in the uml2 tree editor) and select it's type
- select the interface you wish to provide.
nick
|
|
|
Powered by
FUDForum. Page generated in 0.08263 seconds
Home