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
16
General Board / Re: Problem importing XMI from RSA 7
« on: December 21, 2006, 06:01:25 pm »
Hello Dave,

Currently, EA has the ability to import only those RSA exported files which do not have any external dependencies.

But we will be updating Build 810 with the ability to import model files where one references classes defined in another file.

Cheers.

17
General Board / Re: xml schema for exported xmi
« on: December 18, 2006, 01:49:55 pm »
Hello Kate,

EA uses the Schema published by OMG to serialize its UML models in XMI 2.1. This XSD can be found at : http://www.omg.org/cgi-bin/doc?ptc/2006-04-05

Cheers.

18
General Board / Re: BUG?: Duplicate attribute GUIDs on import
« on: December 14, 2006, 04:54:26 pm »
Hello Paolo,

The Integrity Check module will change the GUIDs of the  new attributes only. So, you can safely run the Integrity Checker.
And, I have updated Build 801 (not Build 802 as I had specified earlier) with the fix - it will be coming out in a couple of days time.

Cheers.

19
General Board / Re: BUG?: Duplicate attribute GUIDs on import
« on: December 14, 2006, 02:25:02 pm »
Hello Paolo,

EA does duplicate the GUID of attributes upon importing them from an XMI 2.1 file. We will have this issue fixed for Build 802.

Cheers.

20
General Board / Re: Want to Import Rational Software Modeler
« on: November 29, 2006, 08:48:41 pm »
Hello Ralph,

Send-in a sample *.emx file replicating the above issue to Sparx Support at : support@sparxsystems.com.au
This will help us in investigating the issue further.

Cheers.

21
General Board / Re: Package includes in XML UML Modelling ...
« on: October 05, 2006, 07:20:24 pm »
When you drag and drop an element from the Project Browser onto the current diagram using the option "as Simple Link", the element will appear in the current diagram as a simple reference back to the original source element. Changes to this element in the diagram will affect all other links to this element (refer to the EA Help file under the topic : Modeling with UML -> Common Diagram Tasks -> Pasting from the Project Browser).

For XSD Generation, just pasting an element as a Simple Link does not guarantee its inclusion in the generated schema. Consider the following diagram with a sample package structure and the package tagged-values.



Generate the Schema from the package "PA" and you will see that the generated XSD will have an "include" element.

22
General Board / Re: Import from Together (XMI)
« on: September 28, 2006, 04:01:40 pm »
Hello jstammen,

Send-in a sample XMI file replicating your issue to support@sparxsystems.com.au so that we can investigate the issue. Also, make sure that you specify the Build of EA you are importing into.

23
General Board / Re: generate xml schema
« on: September 25, 2006, 04:35:12 pm »
hello alaino,

EA should generate an Schema with all the attributes, irrespective of their scope. If possible, send-in a sample model replicating your issue to Sparx Support (support@sparxsystems.com.au ) so that we can investigate this issue further.

24
General Board / Re: XMI import problem -- Invalid unicode
« on: April 14, 2005, 06:11:05 pm »
Hi Tormentor ,

i downloaded the xml file from the link and imported it in EA.

EA does throw out an error, but when i removed the inline DTD definition from the xml file ( from lines 2 - 15 ), EA imported the file without complaining ( i am not sure why ).

if you need the definition, try adding it to 'uml.dtd' instead of extending it in the xml file.

Cheers.

25
General Board / Re: Importing a WSDL
« on: September 11, 2006, 11:58:46 pm »
The culprit seems to be the comments under the WSDL PortType - these comments are causing the WSDL Importer to fail.

In the file you had specified, under the portType "StoreSoapPort", you will find the following 2 comments :

<!-- <operation> elements define the function signatures (operation name and parameters) and associate the input and output messages  -->

<!-- parameterOrder attribute values must be separated by a single space  -->

Delete these two comments and EA will import the WSDL successfully.

We will have this bug fixed for Build 798.

26
General Board / Re: XSD Import/Export troubles.
« on: September 11, 2006, 07:53:37 pm »
For large Schemas, the advantage of importing with "UML Attributes" option is that it prevents connectors from flying all over the diagram.

Importing as attributes does not lose the relationship - the "Type" of the attribute will point to the concerned class.

Regarding EA losing a few items on round-tripping XSDs, send in a bug report with a sample file reproducing the issue so that we can investigate the issue further.

27
General Board / Re: How to make an xsd:attribute required using EA
« on: November 24, 2005, 02:07:52 pm »
The default value of 'use' for XSDattribute stereotype is 'optional'. To change this value, select the attribute, open its tagged-value window and change the value of the tag 'use' to 'required'.

Cheers.

28
General Board / Re: EA to output xs:all creating XML Schema, how?
« on: November 24, 2005, 02:02:04 pm »
The default modelGroup for an XSDcomplexType class is 'sequence'. To change this value, select the class and open its tagged-values window. You will see a tag called 'modelGroup' with value 'sequence' - change this value to 'all' .

Cheers.

29
General Board / Re: Import WSDL
« on: November 16, 2005, 04:50:07 pm »
Hello davisford,

The current build of EA allows to import WSDL by the menu option : Project -> Web Services -> Import WSDL
The option to allow importing WSDL by right-clicking on a package in the Project View will be available in our next EA update.

Cheers.

30
General Board / Re: xs:attributeGroup
« on: April 25, 2005, 07:12:08 pm »
Hi lixlix,

By default, EA groups the attributes into an attributeGroup. At present, it is not possible to change this behaviour and make the attributes inline. But we do plan to support inlining of attributes in the future.

Cheers

Pages: 1 [2] 3 4