Entity packages and customer extensions from Java in version 8.0

Accessing entity and typelist data from Java changed significantly in this release. For complete documentation on entity and typecode data from Java, see Accessing entity data from Java.

In Gosu, you can refer to an entity type using the syntax simply entity.ENTITYNAME or simply the entity name because the package entity is always in scope. In the PolicyCenter Java API, you can reference a type directly by its fully-qualified name. However, for PolicyCenter entity types, from Java the fully-qualified name of an entity is not simply entity.ENTITYNAME or simply the entity name. The syntax entity.ENTITYNAME or using the entity name with no package is a shortcut within the Gosu language’s type system.

Unlike in previous releases, PolicyCenter exposes each entity type as up to three different interfaces. Which interface name to use depends on whether the property is defined in the base configuration, application-specific extensions, customer extensions, or entirely new entities that you define.

If you only want the base configuration properties, the type name is the same in Java as in Gosu, but the package varies by entity type. Some aspects of the fully-qualified names of some interfaces are configurable.

For typecodes, there are differences for how to access a typecode based on where the typecode was defined or extended. This is similar to the differences mentioned earlier for multiple entity interfaces in the 8.0 Java API.

For more information, refer to the following sections:

• Accessing entity data from Java
• Accessing entity instances from Java
• Accessing typecodes from Java