skip to main content
Corticon Server: Integration & Deployment Guide : Preparing Studio files for deployment : Entity mapping

Try Corticon Now

Entity mapping

Let's take a look at a sample class that we might have wanted to map to the Aircraft entity.
Figure 290. First Portion of MyAircraft Class
We can see in line 6 of this figure that this class is not actually named Aircraft – it is named MyAircraft. The automatic mapper attempts to locate a class by the same name as each entity. In the case of Aircraft, it looks for a class named Aircraft. Not finding one, it leaves the field empty, as shown in the following figure.
When Java Object mapping has been added to the Vocabulary, its Entity properties are displayed.
Table 21. Java Object Mapping Entity Properties
Java Package
Specifies the package to be used for Java class metadata mapping.
Java Class Name
Maps the entity to the specified class when no class exists with the entity name.
Figure 291. Default Map of Class to Entity
Because no Aircraft class exists in the package, we need to manually map this entity, using the Java Package and Java Class Name drop-downs, as shown in the following figure. The metadata import process populates the drop-downs for us. Be sure to select the package name from the Java Package drop-down so the mapper knows where to look.
Figure 292. Manually Mapping MyAircraft Class to Aircraft Entity