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.


Messages - dr_shorthair

Pages: 1 [2] 3
16
Bugs and Issues / Re: isNavigable & Navigable tagged value inconsist
« on: November 26, 2008, 10:43:05 pm »
OK - I've made this an official bug report.

17
Bugs and Issues / isNavigable & Navigable tagged value inconsistent
« on: November 26, 2008, 05:46:54 pm »
In the Association dialogue in EA it is possible to set the navigability of an association in more than one way:
1. using the "Direction" value on the General tab
2. using the "Navigability" property on the Source Role and Target Role tab.

For most combos set the latter way, this causes the value of the "isNavigable" property of the association-end to be set correctly in the exported XMI document (i.e. in the UML:AssociationEnd/@isNavigable attribute).
 
However, for certain combinations, the value of UML:AssociationEnd/@isNavigable is clearly wrong.

Here's a test model:  
https://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/FullMoonTestModels#Test_25 and the XMI
https://www.seegrid.csiro.au/subversion/FullMoon/trunk/resources/xmi-samples/TestAS25.xml

The association between Sample and FT5 is unspecified/non-navigable, but in the XMI both ends are isNavigable="true". Similar problem with FT7.

Worse still with FT8 where the ends are explicitly non-navigable, but both are labelled isNavigable="true"!

(Note that the correct value can be detected by parsing the sourcestyle or deststyle tag, but this is an EA extension, not standard XMI.)

Looks like a pretty serious bug?

18
Bugs and Issues / Re: Not receiving any notifications
« on: November 26, 2008, 03:46:10 pm »
I got notified of this response, which suggests that my profile is OK.
But none for the questions I posted to the general board in the last week.

19
Bugs and Issues / Not receiving any notifications
« on: November 25, 2008, 11:27:19 am »
I've selected  "Notify of replies" on a few postings in the last week, but am not receiving any. I've checked my spam cache and its not there either ...

20
Bugs and Issues / Re: "Synch Tagged Values" creates duplicates
« on: September 16, 2008, 05:30:05 pm »
I'm getting this bug again.

Seems to happen if the element stereotype is changed manually.
Then if some of the tagged values had been loaded through the original stereotype, they get added again if they are also associated with the new stereotype.

21
Bugs and Issues / Re: "Synch Tagged Values" creates duplicates
« on: August 29, 2008, 10:18:44 am »
Thanks - seems to be OK in 832.

22
Bugs and Issues / "Synch Tagged Values" creates duplicates
« on: August 28, 2008, 05:43:29 pm »
I've updated a UML profile in an MDG, adding two new tagged values to a stereotype. When I run "Synch Tagged Values and Constraints" from the resources window, it creates duplicate tagged values on all elements with this stereotype - the ones that already existed, some of which contained values, plus a new complete set of empty tagged values.

This is highly undersirable - I only wanted to synch the model with the profile to get the new tags, not empty duplicates ...

23
Bugs and Issues / Re: MDG based profile not in resources window
« on: April 03, 2008, 06:33:01 pm »
I've also just discovered this bug.
Import an MDG technology, but UML profiles do _not_ appear in the resources window.
In my case it is an MDG that I created myself (I can supply for testing).
Worked fine in 7.0, but appears to have been broken in 7.1.

I might have to revert - I need to be able to add stereotypes to an existing model, and then sync to get a host of tagged values.
But I don't want to revert since I need the XMI/Rose improvements.
Have Sparx commented on this?

24
Bugs and Issues / Re: Difficulties creating a UML profile
« on: February 14, 2008, 06:05:47 pm »
Can you believe that the problem went away! I banged my head against it for 3 hours on Wednesday. I tested today and the AppliesTo elements are now all present.

However, the Stereotypes are still not ordered as requested. I'll send you the XMI anyway so you can look at the latter issue (though obviously much less important).

25
Bugs and Issues / Re: Difficulties creating a UML profile
« on: February 13, 2008, 10:06:13 pm »
The ones I have most problems with extend <<metaclass>> Class.

I also found that one that extends both <<metaclass>>Attribute and AssociationRole sometimes misses one of them in the list of <AppliesTo> classes.

26
Bugs and Issues / Re: Difficulties creating a UML profile
« on: February 12, 2008, 08:29:54 pm »
Thanks David -

Yes - that is a big help.
It allows me to package several UML profiles as well as tagged values, so that another user can load this environment.

Some more investigation of the profile save/load issue:

1. After running "Save Package as UML Profile" from the project browser, several of the Stereotype/AppliesTo elements are missing. This is why they do not show up when loaded as a Resource. Why are they not saved?
2. The "Order Stereotypes" function does not appear to have any effect.

27
Bugs and Issues / Difficulties creating a UML profile
« on: February 12, 2008, 01:30:30 am »
I've followed the instructions in the Help pages starting at "Create a Profile Package".
Two problems:

1. the procedure to add a predefined tag type does not appear to work at all
2. inconsistent/broken behaviour when saving and loading
(i) I saved the profile out as a "UML profile" using right-click/Save Package as UML Profile in the Project Browser; when I loaded this profile in the Resources panel, only a subset of the stereotypes were loaded. I checked the XML file, and they all appear to be there
(ii) I saved using right-click/Save as Profile on the diagram; when I loaded in the resources panel the stereotype ordering was jumbled

I can provide the XMI and both XML Profiles for debugging.



28
Bugs and Issues / Re: Length of tagged values
« on: February 11, 2008, 10:30:03 pm »
Doesn't appear to allow custom tagged-value types to be exported (as entered using the Settings/UML dialogue).

I also have an issue concerning how to harmonize the various ways to add custom tagged-value types, but probably better to start a fresh thread for that.

29
Bugs and Issues / Re: Length of tagged values
« on: February 11, 2008, 09:44:51 pm »
Great - thats a good start. I can use this.

Is there a way to export all my UML Settings so that someone else can load them?

Simon


30
Bugs and Issues / Length of tagged values
« on: February 11, 2008, 09:04:29 pm »
 ???
We want to include some (XML) implementation-specific information in a UML model (Schematron fragments) that is used by an external encoder.
The usual place to add implementation platform specific detail is in Tagged Values.
However, the length of the tagged value field appears to be limited to ~256 chars.

Is this a UML limitation, or just the EA implementation?
Can it be increased?

If not, then we will have to reconsider where to store potentially long Schematron elements.
Any suggestions? - N.B. must be consistent with UML spec, and not EA specific or a kludge.

Simon

Pages: 1 [2] 3