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

Pages: 1 2 [3] 4
31
Each smaller query was done on a specific object type (eg. class, interface, etc) and a specific stereotype.  For each element found, I streamed the results to the console, exported to Excel and sorted on Element ID as well as UUID and found no duplicates.

32
Hi Paolo,

I did not think about this.  Unfortunately, it appears the results returned by the SQL are not complete.  I created a model in an eap file and transfered it to a DBMS repository.  Running Repository.GetElementSet("select * from t_object where Object_Type <> 'Package'", 2) from the EAP file (JET type) generates 3 DAO.QueryDef[3219] errors and the collection only has 28,466 elements. Running the same operation on the DBMS repository (SQLSVR type), generates no errors but also only 28,466 elements. Breaking the query into 120 smaller queries and summing the results indicates that there were 93,736 elements (non packages) in the model. This is close to 94,002 results that I got from the SQL scratchpad.

Why only 28,466 elements were returned by the SQL and why no errors when the query was run on the DBMS repository? This is a bit concerning.

33
General Board / Re: Controlling order of classes and attributes
« on: October 20, 2016, 02:32:01 am »
Hi Guillaume,

Thanks, we went with a similar approach to resolving.

34
I have a slightly different issue but the subject seems appropriate.

For the following query in the SQL scratchpad, EA indicates "Search returned 94002 results"
select * from t_object where Object_Type <> 'Package'

Using this same query with GetElementSet returns 28466 elements.

   var sql = "select * from t_object where Object_Type <> 'Package'";
   var collection as EA.Collection;
   
   collection = Repository.GetElementSet(sql, 2);

Why the difference and which is right?

35
Bugs and Issues / Re: GetElementSet query failure
« on: October 15, 2016, 03:10:17 am »
I ran into the same issue today using GetElementSet. The query found more than 25000 elements and was generating the same error (3 times).  This error was only being generated when run on an eap file; running the query on the DBMS repository did not generate an error.

36
General Board / Re: Controlling order of classes and attributes
« on: October 13, 2016, 10:27:32 pm »
Feedback from Sparx indicates handling of nestedClassifiers in xmi file does not comply with the standard but will be corrected in a future release:

>>Is the order of these nestedClassifiers for import only controlled based on the EA extensions node?
Currently this is the case - EA relies on the information in the EA extensions node to order the elements.
But we will update the XMI 2.1 Importer in the future releases of EA to reply on the order of elements in the UML section when EA extensions node is not available.

>>Is there any option available to indicate to EA that the xmi file being imported should retain the order defined for nestedClassifiers?
No, this information is stored only in the EA extensions node.

37
Awesome.  Thanks Geert!

38
Is there a way to set the project browser context through scripting?  Using scripting, I can detect what is selected in the project browser. Given a packageID, elementID, diagramID, etc, is there a way to set the ProjectBrowser to select this?

39
General Board / Re: Controlling order of classes and attributes
« on: October 12, 2016, 12:47:55 am »
Thanks for feedback Simon.  Using nestedClassifier did not address the issue. After the import, the order of the nested classifiers does not match the order specified below.

   <packagedElement xmi:type="uml:Class" xmi:id="EAID_c297f8fb_aef3_bd88_35f3_6560afc31e42" name="AlvCalibrationDataTypeAlv1">
      <nestedClassifier xmi:type="uml:Class" xmi:id="EAID_42482dca_e1b0_8621_da41_7885cd87ffb5" name="DataDefProp"/>
      <nestedClassifier xmi:type="uml:Class" xmi:id="EAID_86a55fb0_cd88_a92a_e643_c512dd284893" name="AlvOffset"/>
      <nestedClassifier xmi:type="uml:Class" xmi:id="EAID_d6cf1044_19f7_831e_5eae_9aabaf28892f" name="Sensitivity"/>
      <nestedClassifier xmi:type="uml:Class" xmi:id="EAID_e39e552c_6c47_8ac1_b237_5fb0592fccc5" name="Checksum"/>
   </packagedElement>



40
General Board / Re: Controlling order of classes and attributes
« on: October 11, 2016, 07:19:19 am »
One additional piece of information, the xmi file being imported does not contain Enterprise Architect extension nodes; the input xmi file is created externally and is intended to be tool independent.

     <xmi:Extension extender="Enterprise Architect" extenderID="6.5">

41
General Board / Re: Controlling order of classes and attributes
« on: October 11, 2016, 07:11:39 am »
XMI 2.1 with EA 12.1

<xmi:XMI xmlns:uml="http://schema.omg.org/spec/UML/2.3" xmlns:xmi="http://schema.omg.org/spec/XMI/2.1

My xmi file has the following:
                <packagedElement xmi:type="uml:Class" xmi:id="EAID_c297f8fb_aef3_bd88_35f3_6560afc31e42" name="AlvCalibrationDataTypeAlv1">
                                <packagedElement xmi:type="uml:Class" xmi:id="EAID_42482dca_e1b0_8621_da41_7885cd87ffb5" name="DataDefProp"/>
                                <packagedElement xmi:type="uml:Class" xmi:id="EAID_86a55fb0_cd88_a92a_e643_c512dd284893" name="AlvOffset"/>
                                <packagedElement xmi:type="uml:Class" xmi:id="EAID_d6cf1044_19f7_831e_5eae_9aabaf28892f" name="Sensitivity"/>
                                <packagedElement xmi:type="uml:Class" xmi:id="EAID_e39e552c_6c47_8ac1_b237_5fb0592fccc5" name="Checksum"/>
                </packagedElement>

After import, the AlvCalibrationDataTypeAlv1 class has AlvOffset, Checksum, DataDefProp and Sensitivity sub-classes in this order.  When I export the model as xmi again, I get
      <packagedElement xmi:type="uml:Class" xmi:id="EAID_03FA9522_8E9A_4130_A3DB_7C6DB1858A62" name="AlvCalibrationDataTypeAlv1" visibility="public">
            <nestedClassifier xmi:type="uml:Class" xmi:id="EAID_49799FB4_B6C9_462b_93F6_B107BC30F897" name="AlvOffset" visibility="public"/>
            <nestedClassifier xmi:type="uml:Class" xmi:id="EAID_256557F3_2952_4344_B939_6416616D0670" name="Checksum" visibility="public"/>
            <nestedClassifier xmi:type="uml:Class" xmi:id="EAID_BEDC37A5_B584_4550_91EC_70B76D861A86" name="DataDefProp" visibility="public"/>
            <nestedClassifier xmi:type="uml:Class" xmi:id="EAID_C4693AAC_CAA7_4fab_8965_38A7BAD4FE50" name="Sensitivity" visibility="public"/>
         </packagedElement>

This matches the order displayed in the Project Browser but differs from the order that were defined in the original xmi file.

42
General Board / Controlling order of classes and attributes
« on: October 11, 2016, 06:00:43 am »
I have an xmi file that has classes with sub-classes where the order of these is important. The top level class may contain a configuration class but this must be the 1st sub-class.  The top level class may then contain 1 or more record element classes; the order of these classes should match the S/W implementation. Consider a class used to model a data record. This class could contain a sub-class that defines the attributes of the record; this sub-class is expected to be the 1st sub-class.  This data record class could also contain 1 or more data element classes; the order of these data element classes is expected to match the S/W implementation.

After importing my xmi file, the order of the sub-classes is changed.  Is there a way to force or the order of the elements to match the order they were defined in the xmi file during import?  During export, is there a way to force the elements to be populated in the xmi file according to the order they are defined in the Project Browser?

43
General Board / Re: XMI Import to DBMS Speed
« on: August 26, 2016, 02:31:40 am »
Sorry.  The xmi would be copied to the server and an instance of EA would be run on the server (remotely) to do the import.

44
General Board / Re: XMI Import to DBMS Speed
« on: August 25, 2016, 10:45:26 pm »
I am developing S/W architectures for multiple automotive products with multiple OEMs.  Multiple repositories are needed for this and our development cycle.  I will need to deliver a released S/W architecture that will be implemented and released; each S/W release must have a matching S/W architecture.  Each released S/W architecture must be reviewed (need to be able to identify changes) and will need to be placed under version management to allow visualization and restoration at a later date.

Has anyone had experience using Citrix/EA with a DBMS repository?  Would this improve the xmi import time? I am thinking the xmi files would be copied to the server and import should be much faster.

45
General Board / XMI Import to DBMS Speed
« on: August 24, 2016, 10:29:28 pm »
I want to use a DBMS repository for common models that will be used by other projects.  The choice for DBMS is driven by 1) the need for co-development of the models by a globally dispersed team and 2) robustness to corruption.

I have a repository setup with a cloud connection and am importing xmi (1.1) files that were exported from a standalone model (eap file). One of the xmi files is 28 MB.  Importing this xmi file into a standalone model takes about 2 minutes; exporting takes about 30 sec. Importing the same into the DBMS repository takes about 42 minutes; exporting takes about 55 sec.

Is this long import time due to a setup issue of the repository, network issue, or is it expected?

Pages: 1 2 [3] 4