ILOG JRules User Guide > Creating Rule Projects > Concepts > BOM and XOM > Business Elements Originating from a Java XOM

When you create a BOM entry from a Java execution object model, the Java compiled classes are processed into business elements. The following table describes what execution elements become in the BOM by default, when you keep the option Load getters and setters as attributes selected in the New BOM Entry wizard.

Table 1 Business Elements Originating from a Java XOM
Java element... 
Becomes element in the BOM... 
Nongeneric public class. 
Class with the same name. 
Class that implements the java.util.Collection interface. 
Example: 
MyCollection implements java.util.Collection 
Class with a collection domain to be recognized as a collection when verbalized. 
Example: 
public class MyCollection implements java.util.Collection { 
domain 0, * ; 
} 
Public constructor. 
Constructor with the same parameters. 
Public attribute. 
Attribute with the same name and return type. 
Final attribute. 
Read-only attribute with the same name and return type. 
Public static final attributes whose types are the current class. 
Example: 
public class Color { 
private Color(String name) {...} 
public static final Color red = new Color("red"); 
public static final Color blue = new Color("blue"); 
public static final Color green = new Color("green"); 
} 
Enumerated domain of static references of the class. 
Example: 
public class Color {  
domain { static red, static blue, static green } 
public static final readonly Color red; 
public static final readonly Color blue; 
public static final readonly Color green; 
} 
Public method that does not follow the JavaBeans convention for property accessors (void setFoo(PropertyType value) and PropertyType getFoo()).  
Example: 
public interface Customer 
{ 
public boolean register(java.sql.Connection db); 
Method with equivalent parameters. 
Example: 
public interface Customer 
{ 
public abstract boolean register(java.sql.Connection arg); 
Public method that follows the JavaBeans convention, with a get method and no set method. 
Example: 
public interface Customer 
{ 
public int getAge(); 
} 
Read-only attribute. 
Example: 
public interface Customer 
{ 
public readonly int age; 
Public method that follows the JavaBeans convention, with only a set method. 
Example: 
public interface Customer { 
public void setBirthDate(Date date); 
Write-only attribute. 
Example: 
public interface Customer 
{ 
public writeonly java.util.Date birthDate; 
Public method that follows the JavaBeans convention, with both a get method and a set method. 
Example: 
public interface Customer { 
public String getName(); 
public void setName(String name); 
Attribute. 
Example: 
public interface Customer 
{ 
public java.lang.String name; 

If your business elements originate from a dynamic XOM, they are processed differently. See Integrating Application Data for details.

Related Concepts

BOM and XOM
Business Object Model (BOM)
Execution Object Model (XOM)

Related Tasks

Creating a BOM Entry from a XOM
Managing XOM Changes in the BOM

Related Reference

New BOM Entry Wizard

Related Samples and Tutorials

Tutorial: Defining a Vocabulary