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]
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...)



Hi there,

In the DDS Add-In Beta 1, defining an application which uses more than one domain participant results in a warning during model validation.
Code can be generated, but the resulting application has only one domain participant, whose publisher and/or subscriber has readers/writers for all the topics specified in the participants the application uses in the model. This is not an equivalent solution, since the topics (in the model) belong to different domains and a domain participant participates in one domain only.
Also, in the generated (C++) applications the domain identity is passed as a single command-line argument, meaning the application can participate in only one domain.

The RTIDDS User's Manual 4.1 explicitly lists multiple participants in a single application as a possibility (section 2.4, page 2-10).
Is this Add-In limitation just an artifact in the Beta (and as such one that will be removed in the production release), and if not, what is the reason for it?



Automation Interface, Add-Ins and Tools / DDS Add-In Java generation
« on: February 04, 2007, 04:53:00 pm »
Hi all,

I've been trying out the DDS Add-In over a few weeks and have not once managed to get it to generate Java code.
I've specified Java and the j2sdk platform in the applications' tagged values, and Java as the language in everything else - but still it generates C++ code.
Does anyone know what I'm doing wrong?



Automation Interface, Add-Ins and Tools / DDS Add-In release?
« on: February 04, 2007, 04:47:16 pm »

I've been evaluating the DDS Add-In, Beta 1. I like it a lot, but of course it is not yet at production grade.
Could anyone enlighten me as to the release schedule and pricing?



Pages: 1 ... 19 20 [21]