Return Enumerated Type Pattern

-
Similarly to the Return Wrapped Object Pattern, this one involves reading the EA value for an enumerated attribute value and returning a corresponding object.

get objectType() {
    return ObjectType.fromCode(
        this.wrappedObject.ObjectType
    );
}

The code stored by the native attribute ObjectType is decoded by the ObjectType enumerated type, and the enumerated value object is returned.

Comments

Post a Comment

Popular posts from this blog

Creating Items in Sparx EA via Java

-
Introduction This short post provides guidance on how to create "things" in a Sparx EA model via the Java API. Theory Creating "things" in EA via Java is driven by the Add New method and the Collection class. The first example in the code is adding a "view" to an existing root node. The code below will retrieve the root GUID if the "i" variable is set to 0; rootPackageID = rep . GetModels (). GetAt ( i ). GetPackageGUID (); After obtaining the root GUID it is possible to create a view under the root node. Note the process of retrieving the packages under the root and placing them in a collection. The Add New process is driven from the Collection. Importantly, for a view, the code needs to set a flag which indicates a particular icon. This process is only required for views. org . sparx . Package root = rep . GetPackageByGuid ( rootPackageID ); // get the root Collection < org . sparx . Package > subPackages = r...
Read more

Module Management - Part 1 - getModule() Pattern

-
As discussed in  Module Management - Analysis , EA does not provide support for the ubiquitous Module Pattern .  This becomes an issue with an increase in complexity of model addins.  In order to a) Minimise the management of dependencies, and b) Cater for the use of 3rd party modules, The  framework  provides an analogous pattern, which I'm calling the getModule() pattern, because I lack imagination. The premise is straight forward.  Rather than having an anonymous self executing function returning a module object, we instead have module class elements which have a method called "getModule()"  and this returns a module object when the method is called. The getModule() method would be declared (via the EA interface) on a class element, and then we would place all of the module's code in the body of the getModule() method/operation.  The method would return a module object to the caller. The sample contents of a typical getModule() operation ...
Read more

Java and Enterprise Architect from Sparx Systems – Getting Started

-
Image
This is the first in a series of blogs relating to the use of Java with  Enterprise Architect (EA)  from Sparx Systems. The purpose of the blogs is to provide a starting point for Java programmers in their use of the language with EA. The  official post  from Sparx Systems is to use Java as a scripting language within EA. While this is useful, I have a preference to create Java applications outside of EA. The diagram below describes how a Java application can be created which interfaces into the  Sparx Object Model . The  connection  between the Java application and EA is a COM object (SSJavaCOM.dll) provided by EA. This  page  from EA provides information on how to install the COM object within your windows environment. The Java application’s “view” of the Object Model is via a JAR file ( eaapi) which provides the  linkage  between the COM object and the Java software. I use  Netbeans  for Java Develop...
Read more