Configuring Objecteering Java Developer for reverse operations

Configuration of the JDK being used

In order for the reverse feature to work, the access path to the JDK must be defined in Objecteering. For this, enter the path of the JDK in the "General/JDK" field (Figure 103).

Figure 103. The "General" set of Objecteering Java Developer parameters

JavaImport notes

The list of the imports generated from the model following a reversal can be too long. To avoid generating useless imports, check the "Use JavaImport note to generate Imports" tickbox in Java Developer's code generation options (Figure 104). "JavaImport" notes are retrieved into the model during the reverse. They contain only the imports held in the original file. When this option is used, the contents of "JavaImport" notes are used to generate imports instead of the links present within the model.

Figure 104. The "Use JavaImport notes to generate imports" parameter

Reverse parameters

Figure 105. The "Reverse" set of Objecteering Java Developer parameters

Classpath for the reverse

The "Classpath for the Reverse" field is to enter the proposed default path that the compiled file reverse assistant will use when it is opened. This field is modified when the reverse is launched using a different classpath.

Application sources path

The "Application sources path" field is used to enter the proposed default path that the source file reverse assistant will use when it is opened. This field is modified when the reverse is launched.

Path for the html files

The "Path for the html files" field contains the html file paths used to visualize the documentation of the classes imported into the repository. This string is made up of a list of paths separated by ":" for UNIX, and ";" for Windows. They cannot, however, contain directories that correspond to Java packages.

Verbose mode

To have a more exhaustive trace of the reverse, the "Verbose mode" tickbox should be checked. This option allows file(s) to be displayed during the reverse.

Filter accessors on reverse

The "Filter accessors on reverse" parameter is used to filter accessors during a reverse so that the model will not be overloaded.

An operation is considered to be a read accessor if its name begins with "get" or "card" and is followed by the name of the attribute with the first letter in uppercase. The operation must have a return type.

An operation is considered to be a write accessor if its name begins with "set", "erase" or "append" and is followed by the name of the attribute with the first letter in uppercase.

Do no activate the "Filter accessors on reverse" parameter if you have put specific code in your accessors.

Example:

int myAtt;

int getMyAtt() {

return myAtt;

}

void setMyAtt(int myAtt) {

this.myAtt = myAtt;

}

int getDate() {

…

}

The "getMyAtt" and "setMyAtt" methods are considered to be accessors. If this option is activated, these methods will be filtered when a reverse is performed.

Automatically create diagrams on initial reverse

If you want to create diagrams automatically after a reverse, check the "Automatically create diagrams on initial reverse" tickbox . Diagrams can also be created after the reverse using the "Java Developer/Create diagrams" command from the context menu of a package.

Convert abstract accessors into members

Check the "Convert abstract accessors into members" tickbox to convert abstract accessors into attributes or associations of the class.

Reverse package use as references

Check the "Reverse package use as references" tickbox to reverse packages use in the form of references to the packages.