Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Uffe

Pages: 1 ... 19 20 [21] 22

I have created my first MDG Technology. It contains a set of Profiles, a couple of Transformation Templates and a single Tagged Value Type (a RefGUID type named "InstanceType").

I have deployed the MDG Technology and am using it in a different project to the one where it is defined.

The problem is that in the project where I'm using it, the "InstanceType" seems to be absent.

The type is not visible in the "Settings-UML" window, and neither are the stereotypes I've defined in my profile. But the Transformation Templates are visible under "Settings-Transformation Templates."

My MDG Technology contains only profiles, transforms and tag types. I've checked the file, and the type is definitely in there along with the rest of the stuff.

I am using the automation interface to reverse-engineer a lot of classes, and this process fails because the "InstanceType" is not available in the target project. If I add it manually, it all works.

I'm thinking I've missed a step in the deployment, but I can't think what.
Anyone else?



Hej allihopa!

When I use the Automation Interface (Java) to create classes, the attributes end up ordered by name, not the order specified. I'm just calling elements.AddNew() a number of times.

The thing is, while the order is not important in UML I am in fact creating classes which, in the next transformation step, will get turned into Enumeration types. In other words, I do want the order preserved.

Is there a way of doing this in the Automation Interface?



Hello everyone,

I'm trying to create a Profile containing a Stereotype extending Enumeration.

It's not working.

First off, the icon in the resulting toolbox is the Package icon, which indicates something is amiss.

Secondly, I can't use my shiny new stereotype at all. If I select the icon in the toolbox and create an element in a diagram that way, the element type becomes Class, not Enumeration.

If I select an Enumeration in the standard Class toolbox, I can select the stereotype in the drop-down list in the creation dialog, but once I click OK the element type becomes Class.

And as we all know, you can't change the element type from Class to Enumeration.

So what gives?




In a Profile diagram, I can draw a <<taggedValue>> Connector from a Stereotype to another Stereotype. But I can't draw it from the Stereotype to a <<metaclass>>.

Why is this?

And how do I create a Profile where a Class has a tagged value that's selectable from a bunch of (non-stereotyped) Requirements?



Automation Interface, Add-Ins and Tools / Profiles: Stereotype inheritance
« on: February 17, 2009, 07:41:57 pm »
Hey beveryody,

I'm working on a Profile and I'm wondering if what I'm experiencing is as it should be.

First off, I create two abstract Stereotypes MyStereo and MyTag which <<extend>> Class, then add four concrete Stereotypes MyStereoA and MyStereoB which Generalize MyStereo, and MyTagA and MyTagB which Generalize MyTag.
I then want MyStereoA to have a tag of type MyTagA, and MyStereoB to have a tag of type MyTagB. I can do this - but the tags cannot have the same name (MyTag). I must name them differently, eg aMyTag and bMyTag.

Secondly, I can specify that a Stereotype should be composite (_makeComposite, _defaultDiagramType) - but if I do that on the abstract MyStereo, the concrete MyStereoA and MyStereoB are not made composite when dragged in from the Resources tab.

Are these bugs or am I UMLing wrong?



Automation Interface, Add-Ins and Tools / Eclipse Integration on Linux?
« on: February 05, 2009, 06:32:18 pm »
Hi all,

Quick question: is the Eclipse Integration module available on Linux? Not according to the system requirements page, but I'm that may be a mistake. Anyone know f'sure?


Automation Interface, Add-Ins and Tools / Ada support in DDS Add-In
« on: April 23, 2008, 05:48:58 pm »

This is really more of a support question, but since there may be one or two other interested parties I'm posting it here.

Sparx' EA Add-In for DDS is the tool RTI recommends for its DDS implementation. RTIDDS has traditionally come with C, C++ and Java APIs.

Over the past year, RTI has been adding Ada bindings as well. So the question is, are there any plans to add Ada support to the Add-In? If so, roughly what timeframe would we be looking at?

Since the RTI Ada bindings were actually developed in co-operation with my company (Saab Systems) we're obviously very interested in having the support in the design tool as well. We might even be interested in working with Sparx to achieve this, although I stress that that is not a decision I am authorised to make (I'm just the dude who'd most likely end up doing it).

Would anyone else out there be interested in Ada support in EA, either specifically for the RTIDDS Add-In or in general?



Hi everybody,

I'm running the brand spanking new EA 7.1.827 (evaluation) on XP SP2.
I haven't tested this on other versions of EA.

I'm doing some profile modelling and I've bumped into something a bit odd.

Here's what I've got:

Code: [Select]
<<stereotype>> MyStereo <<extends>> <<metaclass>> Class
<<stereotype>> AbsTagType (abstract) <<extends>> <<metaclass>> Class
<<stereotype>> ConcrTagType_1 generalizes AbsTagType
<<stereotype>> ConcrTagType_2 generalizes AbsTagType

I want MyStereo to have a tagged value of type AbsTagType, so I use the <<taggedValue>> connector.

Now here's the thing.

In the <<taggedValue>> Association Properties dialog, I can set a name for the tag either as the Link Name (General tab), or as the Target Role.
Which method I choose affects the resulting Profile.

In both cases, the tag in MyStereo receives the intended name. No worries there.

If I use the Link Name, the typing fails: I cannot use <<ConcrTagType_1>> or <<ConcrTagType_2>> classes as tag values, only <<AbsTagType>>, which is intented to be abstract.
Since <<AbsTagType>> is abstract I cannot drag it from the Resources tree, but I can write it into a Class' Properties manually, and I can then use it for the tag in a <<MyStereo>> class.
If I make AbsTagType concrete in the profile, the inheritance still doesn't work and I can only use <<AbsTagType>> values in the tag.

If I instead use the Target Role, the typing works: I can use both the concrete stereotypes as values for the tag.
But in the Tagged Values window, the value for the tag is presented as <<ConcrTagType_1>> ActualTagClass. That is to say the stereotype name is displayed, which takes up a lot of space.
The stereotype name is displayed not only for those tags that are defined with an abstract type in the profile, but for all tags whose names are specified using the Target Role.

If I use the Link Name for the tag name, the stereotype name is not displayed in the Tagged Values window, which is tidier.

So the question is: is this a UML quirk (ie specified behaviour)?
Or is it a feature (intended behaviour), and if so what's the reasoning behind it?
Ot is it......... a bug?



Hi everyone,

I'm trying to create a model transform which, for each package, creates a new class which all transformed classes in that package have an association to.

I can create a class in the Namespace transform, and the respective classes in the Class transform. In the Class transform, I can create the association... almost. What's missing is the reference to the class created in the Namespace transform.

I can't seem to get my head around how to get hold of that reference.
Basically, the structure looks like this:

Code: [Select]
%list "Class"%

Code: [Select]
  -- Here's where I need the GUID for "NewClass" created in Namespace.

Any good ideas?



Automation Interface, Add-Ins and Tools / DDS Add-In: QoS tags go missing
« on: September 18, 2007, 08:21:47 pm »
Hey everybody,

I've bumped into a pretty serious issue with the DDS Add-In and I'm wondering if anyone's got a workaround.

Topics and other DDS entities have QoS parameters assigned to them using tagged values. These vanish, making it impossible to change the QoS settings.

I have not been able to ascertain under which exact circumstances the tags go AWOL, but once it happens it's universal through the project. The only QoS tags that remain are those whose value you have already changed at least once.

I've exported identical data structures from a corrupt and a good project. In the corrupt XMI file the QosProperty for a topic had lost its own "classifier" and "classname" tags.

Does anyone know why this is, and what steps can be taken to remedy the situation? At present, all I can do is create a new project and start from scratch. Not really acceptable.



Automation Interface, Add-Ins and Tools / DDS Add-In modifications
« on: August 05, 2007, 04:51:10 pm »

I've made some modifications to the DDS Add-In code generation template I'd like to submit for possible inclusion into the next version.
Should I post them here or send them by e-mail and if so, who to?



Automation Interface, Add-Ins and Tools / Stereotype inheritance
« on: July 30, 2007, 08:36:19 pm »
Hello gurus,

If I in a UML profile define a prototype for a class, say, can I generalize it and have that work in f'rinstance code generation?
In other words, is prototype inheritance possible?
I've done some tests and they seem to indicate the answer is no, but then again I simply might not be getting it. It's happened before once.




In a Code Generation Template, is there any way to grab hold of a package stereotype?
There's no %packageStereotype% macro, and a Namespace stereotyped override seems to have no effect.
I'm on 6.5.806 in production, but my 7.0.813 evaluation installation appears to behave identically.



Hey people!

I'm creating UML profiles and code generation templates for various nefarious purposes. There's a couple of things I don't get, or just can't do properly:

1) Packages. It seems the %packagePath% always comes out the same as the %packageName%, even if the class being generated is three levels into a hierarchy. It seems that only the View level package is actually translated into a %packageName%. What am I missing?

2) Multi-class files. I'd like to generate all classes in a package into one and the same file, but when I specify the same file name for the classes they end up overwriting each other. Ideally, I'd like to be able to generate a whole hierarchy of packages into one file. Considering that there's no %package% template hook, is this possible? Are there any plans to incorporate a %package% hook in a future version?

All help appreciated.



Hey everyone,

I'm setting up code generation templates for some proprietary config / scripting languages we use.

In one of these, I need to be able to
a) Output the number of elements in a class, and
b) Output the (zero-based) element numbers.

According to the help files there are no numeric variables in the code generation language; all variables are strings.

Variables are local to a template and do not retain their values between successive calls. So I can't, say, initialise a (string) variable in the Class Body template, then in Attribute output LENGTH($var) and set $var = $var + "x" to increase the length by one. Which would have been neat.

If you fiddle around with the attribute list in the Attributes dialog for a class you'll find an ID column to the right of the Initial Value column. These IDs are one-based, but if I could subtract 1 from each of them (or write a monster %if statement to output one less than the ID), I'd get what I need. However, the field is not mentioned in the help file's list of Field Substitution Macros, and %attID% is not recognised by the framework (produces no output).


1) Does anyone know of a simple way to access the number of elements in a class, rather than counting them?

2) Does anyone know of a way to do simple arithmetic in the code generation language?

3) Does anyone know of a way to access the Attribute ID field? No, it's not the GUID. Thanks.

4) Does anyone know of a way to create a global variable?

5) Does anyone have any other bright ideas?

I know that with a full-fledged Add-In you've got all the freedom you need, it's just it seems a bit excessive to me to go through that whole process just for x = x + 1.

I'm using EA 6.5.806 on my production machine, 7.0.813 is still in evaluation (by me), but seems to be no different in this regard.

(Adding %attID% and %classNrAttributes% would of course solve my problems too...)



Pages: 1 ... 19 20 [21] 22