Fusion Middleware guide chapter 4 doubt

Question

All,
In Fusion Middleware guide chapter 4 : "4.12.1 How to Find an Entity Object by Primary Key", it talks about gettnig an Entity in AM if i am not wrong gonig by the paraphrase, isnt it ?
To access an entity row, you use a related object called the entity definition. At runtime,
each entity object has a corresponding entity definition object that describes the
structure of the entity and manages the instances of the entity object it describes. After
creating an application module and enabling a custom Java class for it, imagine you
wanted to write a method to return a specific order. It might look like the
retrieveOrderById() method shown in Example 4–13.
Can some one guide me on this ?
thank you.

Answer 1

Hi,
this code is taken from the Fusion Order Demo you can download from OTN.
OrdersEOImpl.getDefinitionObject() calls
public static synchronized EntityDefImpl getDefinitionObject() {
        if (mDefinitionObject == null) {
            mDefinitionObject = EntityDefImpl.findDefObject("devguide.examples.entities.OrdersEO");
        return mDefinitionObject;
{find}
the findByPrimary key later calls
http://docs.oracle.com/cd/E15523_01/apirefs.1111/e10653/oracle/jbo/server/EntityDefImpl.html#findByPrimaryKey_oracle_jbo_server_DBTransaction__oracle_jbo_Key_
+"    Finds an Entity Object given a Primary Key.+
    +Given the name of the databse transaction and the table's primary key, this method returns the associated Entity Object. If the Entity has not already been brought into the cache by any of the View Objects, this method will cause the Entity to be fetched from the database.+
    +This method returns null if the Entity Object is not found.+
    +Parameters:+
        +txn - the transaction containing the Entity Object.+
        +key - the Primary Key.+
    +Returns:+
        +the Entity Object matching Key, or null if not found.+
+"+
Bottom line, the entity object is looked up from the entity cache for this entity and if it isn't found it is queried
So nothing wrong with the documentation.
Frank