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 - Paolo F Cantoni

Pages: 1 ... 391 392 [393] 394 395 ... 403
I thought this might go back to UML, but on checking the UML 2.1.1 standard (superstructure and infrastructure) I cannot find anything relevant.

[NOTE: That does not mean it is not there, just that I did not find it under a similar name. PUNDITS: Weigh in here as appropriate.]
Search for "Changeable" under my name and you'll find some discussion thereon.  

This property, in my experience, is normally related to data model relationships specifying whether or not the destination of the Association can be changed after creation.


Automation Interface, Add-Ins and Tools / Re: Is Property a Stereotype
« on: January 27, 2008, 04:39:14 pm »
If one creates an Attribute for a Component, one of the available Stereotypes listed in the drop down is Property, but in the list of Stereotypes, there is no entry for Property.


It seems to work to define a stereotype for an Attribute, but there are not examples and it doesn't seem to be shown anywhere.
EA works by Magic...

That's why many of the bugs can't be fixed...


<rant>I hate it when software makes arbitrary decisions about how I should do something. I believe that every developer should read "The Design of Everyday Things" (aka "The Philosophy of Everyday Things" aka "POET") as part of their training so that the "NO SURPRISES!" mantra is drummed into their heads!</rant>
Say no more!

NO SURPRISES is also known as the "Principle of least astonishment"

The intriguing thing to me is that it actually takes more work to make things inconsistent.


Hi Rick,

Your usage as shown in the examples you gave isn't quite the same as ours.

The modified example:

Code: [Select]

<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="" elementFormDefault="qualified">
<xs:complexType name="SampleAddress">
<xs:element name="AddressLine1" type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="AddressLine2" type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="AddressLine3" type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="Country" type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="Test" type="SampleAddress"/>
<xs:complexType name="GlobalEl1">
<xs:element name="element1" type="SampleAddress" minOccurs="1" maxOccurs="1"/>

Round-trips (that is export from one package and re-import into another - so it doesn't overwrite the first) OK.

And is closer to our usage.

There are issues with both import and export of stand-alone elements (ie not stereotypes as top-level elements -

Thus your:
<xs:element name="SampleAddress" type="SampleAddress"/>

Does NOT get into the browser NOR appear on the diagram  - but IS imported and re-exported!

There are bugs to report and you should do it since your usage is the one that needs to be fixed.

Does that help?

Hi Rick,

WE do that all the time...  Admittedly, we reverse engineered from an Altova created XSD.

However, the advice applies - set on up externally using your favourite XSD creator.  (If you don't have one, I recommend Liquid XML from - it's free and pretty good).

Reverse engineer that and then see what EA does with it then emulate it...  I can't provide an example since I'm not at work...

BTW: reverse using both forms of representation - I think, from memory, there are differences...


EVERY coding mechanism MUST have the ability to provide comments...



That's the Nesting connector in EA.

It's implementation may not be correct for your needs, but I think conceptually it fits...  Check out the Help.


Automation Interface, Add-Ins and Tools / Re: Requirement's StereotypeEx
« on: November 13, 2007, 01:26:34 pm »

If you look for some recent posts of mine regarding XSD handling - you'll see I showed that not only will two "identical" elements behave differently from time to time, but will also themselves behave differently depending upon the context.

It's all quicksand...


Has anyone got any ideas to help me here please?
Hi David,
I presume if you added the appropriate uniqueness constraint to the database, you'd get an exception that you'd be able to use to back out...

If you don't get the exception why don't you?

[size=10]Using EA in spite of EA, NOT because of it![/size] TM[/color]

Referential integrity!  Referential integrity! Wherefore art thou referential integrity?

(with apologies to the bard...)


Hi Michael,

Further to what David said, we also noted that EA didn't always create t_diagramlinks entries correctly and that caused problems with round-tripping and rendering of links in diagrams.

I think since at least v7 and probably a little before, EA now correctly creates those entries - that is, for each link in the diagram there will now be a t_diagramlinks entry.  However, you'll need Sparx to confirm that for sure.


Automation Interface, Add-Ins and Tools / Re: XMI export to Eclipse/EMF
« on: August 15, 2007, 08:18:38 pm »
Sergeant!  Shoot that man - he's making sense!   ;D


We'd Beta Test it...   ;D


Automation Interface, Add-Ins and Tools / Re: Find dragged diagrams
« on: August 23, 2007, 02:45:33 am »
Hi Tim,

As Thomas says, because you dragged it away, it won't appear under that function - since it ONLY returns the diagrams immediately under that element.  The link still exists as you indicate because the database still retains the link.

You need the function that returns the referenced composite diagram.  I don't know which that is (since I'm not an automation expert) a quick look at the help didn't find it - but that means nothing...


Automation Interface, Add-Ins and Tools / Re: DDS Add-In modifications
« on: August 05, 2007, 05:26:27 pm »

Best (proven) solution is to post them here (or on Wiki) and then submit a bug report referencing this Topic.  That way everyone can see and implement early while waiting for the "mills of Sparx to grind"...

Also, don't for get to post any responses from Sparx...


Pages: 1 ... 391 392 [393] 394 395 ... 403