Skip to main content

Accessing the BindingContext through Servlet in ADF Application

By
Follow the following steps to access the BindingContext in your Servlet

1. Create one seprate pageDef file without any fragement or page.We don't have any option to create  pagedef directly without any page.
So go to the folder(on the drive C/D) where you want to add pagedef inside the application and copy one existig pagedef and paste.Rename this copied file with new name ex. MyPageServletPageDef.
After that in jDev you can see this file in the same folder where you created through backend.

2. Add the method binding or iterator binding which you want to access in the servlet on the created pageDef file that is MyPageServletPageDef.

3.Next step is to register this pagedef in DataBindings.cpx file.
  Open your DataBindings.cpx  file code through source and add follwoing code

ex. MyPageServlet is the servlet and  MyPageServletPageDef is the page definition file which we created.
First create the id for your pageDef file inside the tag <pageDefinitionUsages>
<pageDefinitionUsages>
<page id="og_dr_sm_mgt_ui_page_MyPageServletPageDef"
            path="og.dr.sm.mgt.ui.page.MyPageServletPageDef"/>
|
|
</pageDefinitionUsages>
or.dr.......page is path of the file.
Inside the  <pageMap> tag add following code
<pageMap>
<page path="og.dr.sm.mgt.ui.bean.MyPageServlet"
            usageId="og_dr_sm_mgt_ui_page_MyPageServletPageDef"/>
|
|
</pageMap>



4.Register your servlet in web.xml of your portal(your main applications web.xml file)
   You need to add inside the Filters->adfBindings->Filter Mappings
 


Inside the Filter Mappings click add button and add your servlet as shown in above screen.
  
5.Finally add the following code inside your servlet to maccess the binding
    BindingContext bindingContext=null;
    bindingContext = BindingContext.getCurrent();
    DCBindingContainer dcBindingContainer = bindingContext.findBindingContainer("og_dr_sm_mgt_ui_page_MyPageServletPageDef");
    OperationBinding operation = (OperationBinding)dcBindingContainer.getOperationBinding("MethodName");
    operation.invoke();

Comments

Post a Comment

Popular posts from this blog

The file store "WLS_DIAGNOSTICS" could not be opened

By
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
1 comment
Read more

Passivation and Activation in ADF (Application Module )

By
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 c...
1 comment
Read more

Overview Editor for bc4j.xcfg

By
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...
4 comments
Read more