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

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

Overview Editor for bc4j.xcfg

This is used to customize the configuration settings for the application pool, connection pool, and transactions. Select the Application Module, then select a configuration from the Configurations list. You can specify a Default Configuration from the dropdown to use with selected application module. Edit the name of the configuration in Details. Its having 3 tabs 1.Database and Scalability 2. Properties 3. Custom Properties Database and Scalability Tab : In Database and Scalability you can mention the JDBC data source definition for each application module. You can choose to connect to a JDBC data source or to a JDBC URL.The default connection type is the default data source. A data source is a vendor-independent encapsulation of a database server connection on the application server. 1. Data sources ( JNDI name) offer advantages over a JDBC URL connection because the data source can be tuned, reconfigured, or remapped without changing the deployed application. 2. JDB...

WebCenter Deployment Architecture

The main components of the deployment architecture are: • WebLogic Server • Portlets deployed in Portlet Container • Metadata storage for customization information • Enterprise Content Management solution with Content Adapters • WebCenter Services • WebCenter Search • Identity Management         WebLogic Server, which is a Java EE–compliant application server, is at the center of WebCenter. WebCenter applications are Java EE applications that are deployed to WebLogic Server. WebCenter Spaces is a prebuilt custom application using WebCenter Framework and Services. Portlets : WebCenter applications can consume portlets. Portlets are deployed into a Portlet Container and are accessed by various HTTP-based network protocols such as WSRP and SOAP. Oracle WebCenter supports several portlet APIs such as JSR 168 and PDK Java.   Metadata Services : WebCenter applications can be customized or personalize...