| Re: [mdt-papyrus.dev] Parameterized class as an operation parameter |
|
Please, let’s use the forum. Thanks. Ps: Arnaud, in cc will answer directly on the forum as soon as the topic is there open. If already open, please send a link the topic. ------------------------------------------------------------------------------------------------------------------------------------------------ Sébastien Gérard +33 (0)1 69 08 58 24 / +33(0)6 88 20 00 47 CEA Saclay Nano-INNOV Institut CARNOT CEA LIST DILS/Laboratoire
d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE), Point Courrier n°174 91 191 Gif sur Yvette CEDEX De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Martin Puffe Hi, I'm new to this mailing list and am currently working on a UML class diagram to model a typical business application (sort of a customer relationship management system). Thus I need to define a template's operation with a parameter, whose type is a parameterized interface (List<E>, where E is the templates parameter). To clarify my class structure: class List<class T> interface JpaRepository<class E> List<E> findAll() void delete(E element) etc... I know how to define the delete function in this case, I can apply E as a parameter. But I don't know how to define the findAll() operation, as I have not yet found a way to use parameterized classes as operation
parameter types in Papyrus. I have heard, that UML provides parameterized classes, but is it possible to use them with Papyrus? I do not want to create a new template bound class for each usage of List<T>! Greetings, Martin Puffe |
