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 - VK

Pages: 1 2 [3] 4
General Board / Re: [BUG] xmi export has a bug
« on: April 25, 2005, 07:23:16 pm »
Hi HarryMuc,

I could not reproduce your problem.

When I exported the package to Unisys/Rose Format XMI 1.0, and imported them in Poseidon and MagicDraw UML (I am not sure what tool you are using), I could get the tagged value of the package correctly. Also, when I checked the XMI file, the tagged values for the package are being referenced as 'EAPK_' and not 'EAID_'.

So, if you could send in a sample model which reproduces your issue, it would help me in correcting the bug.

You can send the model to :


General Board / Re: Import EA generated XMI (1.0/1.2) files
« on: April 17, 2005, 05:48:01 pm »
Hi nicholas_yue,

EA doesn't have the option to write out the diagrams in SVG format.

As a workaround for generating SVG diagrams, export to Unisys/Rose Format XMI1.0 in EA by :

* CTRL + ALT + E
* Check both Unisys/Rose Format and XMI 1.0 options

Import the file in 'MagicDraw UML' and then save the graphics as SVG file  :)


Bugs and Issues / Re: use case structured scenarios in v8.0
« on: February 16, 2010, 03:19:31 pm »
One other method for copying Scenarios between UseCases is by reverse engineering the generated Activity Diagram ( as explained in the following topic in the EA Help file : Modeling With UML -> Work With Elements -> Properties -> Scenarios -> Generate Scenario From Activity Diagram )

Bugs and Issues / Re: BPEL in version 7.5
« on: February 24, 2009, 04:21:51 pm »
The Enterprise Architect Example file (EAExample.EAP) has a sample BPMN 1.1 model from which BPEL can be generated. If you have installed Enterprise Architect 7.5 at the default location, open this file:

    C:\Program Files\Sparx Systems\EA\EAExample.EAP

The BPMN model package, within EAExample.EAP, is in: System Model -> Implementation Model (PSM) -> BPEL Example.

Bugs and Issues / Re: BUG: XSD Model Group is exlcusive
« on: November 05, 2007, 05:49:13 pm »
Hi Paolo,

This is a bug and we will have it fixed for the next Build of EA.


Automation Interface, Add-Ins and Tools / Re: XSD generation
« on: February 04, 2010, 09:15:09 am »
Goto the Tagged Values window for the attribute and change the value the tag use to required

To generate a 'ref' attribute, open the tagged-values window for the connector and set the following tagged-values in the 'Connector Source' section :

1. Tag    = anonymousType
    Value = false

2. Tag    = anonymousRole
    Value = true

Hello Bernd,

The following link will help you perform this transformation :


Automation Interface, Add-Ins and Tools / Re: Import WSDL
« on: October 26, 2006, 03:23:14 pm »
We will have this issue fixed in the next Build of EA  :)

Automation Interface, Add-Ins and Tools / Re: Import WSDL
« on: October 05, 2006, 07:35:32 pm »
The WSDL Importer does not currently handle multiple namespace-prefixes for the same namespace. Hence it throws the header incorrect error.

Of these 2 declarations :


I believe that the WSDL file is using the namespace-prefix "wsdl" to refer to the WSDL namespace. Hence, delete the other namespace-prefix declaration ( xmlns="" ) and EA will import the WSDL without throwing any errors.

Hi kline,

Set the value for the tag anonymousRole as "false" and anonymousType as "true" at the "Connector Source" and generate the schema.

You should get an output like :

<xs:complexType name="Case">
          <xs:element name="applicant" type="Party"/>
          <xs:element name="company" type="Party"/>


Hello pmahoney,

The XML Profile is being modified and it will incorporate  many new features, including a new stereotype called <XSDattributeGroup>  :)

These changes will be available during the next major release of EA.


Hello Paul,

As of now, there is no option to specify the dataType of a <XSDsimpleType> stereotyped class. It always takes the default value of "xs:string".

But, we will change this default behaviour in the future release of EA.


Hello pmahoney,

Elements in a Class can have stereotype <XSDattribute>. An element with this stereotype will be generated as an attribute group.

Lets say that you create a Class, say 'Class1', with stereotype <XSDcomplexType>. Add an element to it, say 'elem1', and set its stereotype to <XSDattribute>. Generate the XSD. The schema will be like :

<xs:element name="Class1" type="Class1"/>
<xs:complexType name="Class1">
           <xs:attributeGroup ref="Class1.att"/>

<xs:attributeGroup name="Class1.att">
           <xs:attribute name="elem1" use="optional" type="xs:integer"/>

The advantage of using the stereotype <XSDattribute> on elements is that you can have any desired data-type for the element - not just "xs:string".


Hi Tomas,

This bug has definately been fixed. Would it be possible for you to send in a model reproducing your problem to Sparx Support ?

Pages: 1 2 [3] 4