Skip to main content

Get modified rows from Entitiy Cache

To get the modified rows from entity cache we have getEntityState() method at EntityImpl class.

Refer to my previous blog Accessing EO impl methods from VO impl where i am overriding the getEntityState() in EOimpl and calling it in VOImpl.
We can use methods written or overridden in VOImpl class to AMImpl class.

There are different states associated with an entity object.

STATUS_UNMODIFIED
STATUS_MODIFIED
STATUS_NEW
STATUS_DELETED
STATUS_DEAD

We have to check the state or row in our AmImpl class by using the VOImpl method and through this we can distinguish the rows present at vo.


Add below code in AMImpl class along with my previous post.

public void geCachedRowsCount(){
        JobsVOImpl jobsVo = (JobsVOImpl)this.getJobsVO();
        RowSetIterator iter = jobsVo.createRowSetIterator(null);
            while(iter.hasNext()){
            Row row = iter.next();
            byte state = jobsVo.getEntityState(row);
            System.out.println("Job_id -> "+row.getAttribute("JobId") +" and state ->"+state);
// use state variable to compare and write your logic
        }
     
    }


As you can see in above example, you will get the state of a row in above loop and you have to compare it with either
0 for new created row (but not committed to DB)
1 for unmodified state
2 modified state (but not committed to DB).


Comments

Post a Comment

Popular posts from this blog

Passivation and Activation in ADF (Application Module )

1. For performance reasons, ADF keeps a pool of application modules in memory. It tries to give each session the same application module as the session used during the last request; however, this might not be possible during peak load of your application. 2. In this case, ADF saves the application modules state in a database table so the application module can be used by another session. This is called passivation . 3. When the first session needs the application module again, its state is retrieved from the database process known as activation . 4. If you have made an error in your code and depend on some variable that is not persisted correctly when your application module state is stored, you will experience mysterious errors under high load.   Enable/Disable Application Module Pooling : Right-click on your application module, choose Configurations.By default, each application module has two configurations. Ensure that the one ending in …Local is selected and then click

The file store "WLS_DIAGNOSTICS" could not be opened

WLS_DIAGNOSTIC ERROR weblogic.store.PersistentStoreException: [Store:280073]The file store "WLS_DIAGNOSTICS" could not be opened because it contained a file with the invalid version 1. A file of version 2 was expected. When you get this error while running your application on internal weblogic server delete the following file WLS_DIAGNOSTICS000000.DAT search the file in following path C:\jdev_work\system11.1.1.5.37.60.13\DefaultDomain this file is in DefaultDomain folder of your jdev. and delete the WLS_DIAGNOSTICS000000.DAT file . and run your applicatuon