Eclipse Community Forums: Papyrus » Property edition not supported in Profiles ?

Help

Home

Home » Modeling » Papyrus » Property edition not supported in Profiles ?(Property Class Profile Stereotype)

Show: Today's Messages :: Show Polls :: Message Navigator

Property edition not supported in Profiles ? [message #814678]

Tue, 06 March 2012 19:07

Stéphane Le Minoux

Messages: 2
Registered: March 2012

Junior Member

Dear All,
I've been defining in another tool a Profile with a Stereotype S containing a Property of Class C which has two properties that are simple types (String and int).

When I apply the profile to a model, everything seems OK, however, whenever I want to apply the stereotype and define my Property of Class C, it fails editing the subproperties. As a result I cannot use Papyrus to edit such model.

Is it planned to support such constructions ?
How could I handle this kind of Profile Application with Papyrus ?

Regards,
--
Stéphane

Report message to a moderator

Re: Property edition not supported in Profiles ? [message #815108 is a reply to message #814678]

Wed, 07 March 2012 08:34

Camille Letavernier

Messages: 943
Registered: February 2011

Senior Member

Hello,

It is not possible to create Classes in a UML Profile with Papyrus. However, for a simple case such as yours, you could use a Datatype instead. You could also use another Stereotype, although the behavior would not be exactly the same.

If you don't want to modify your profile, it might be possible to implement your own property view to handle this case (Which cannot be handled by the generic one).

There's currently no plan for supporting this kind of Profile in Papyrus (Neither for defining it nor editing a model on which it is applied).

Camille

Camille Letavernier

Report message to a moderator

Re: Property edition not supported in Profiles ? [message #816378 is a reply to message #815108]

Thu, 08 March 2012 19:38

Stéphane Le Minoux

Messages: 2
Registered: March 2012

Junior Member

Thanks for this quick answer.
I'll try using a DataType instead, and indeed another stereotype would'nt be applicable to the context.

I think it's a shame not to have a reflective editor for such cases in order to enable profiled uml2 direct edition for a tree structure of stereotyped information.

Where could I find some pointers on implementing my own property view to handle this case ?

Regards,
--
Stéphane

Report message to a moderator

Previous Topic:	MARTE Elements in editor
Next Topic:	How can i link between 2 class diagrams?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Apr 19 10:02:50 GMT 2021

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter