Memory leak - Managed beans kept in memory in ADF

Hi,
Our application occasionally runs out of memory, and what we are finding is that the managed beans beneath components on the page are not being cleaned up, even after the user's session has expired.
What I am finding, by using the JDeveloper debugger and Heap window, is that there are instances of com.evermind.server.http.EvermindHttpServletRequest left in memory, which hangs on to the entire page, and therefore all of the instances of the ADF Component classes and managaged beans.
Has anyone else come across this and found a way to clean up all of the page information left on the EvermindHttpServletRequest after the page is no longer in scope, and the session has expired?
Any assistance which anyone can provide on this issue would be greatly appreciated.

Hi,
I'm quite sure I'm hitting the same problem here. This is really serious!

Similar Messages

Managed bean/Data exchange between two ADF Rich Faces based applications

Hi,
I have been trying to research what seems to be a small issue. My requirements are as follows.
1. I need to be able to pass managed bean information from one ADF Rich Faces based application to another (in two separate ears) at runtime (e.g. from Ear1: SenderApp/Sender.jspx -> Ear2: ReceiverApp/Receiver.jspx).
2. I do not want to use the database as my applications need to be performant.
3. Serialization/de-serialization would fall pretty much under the database category. In other words, I like to avoid Serialization/de-serialization of the managed bean.
4. I cannot use query string due to security issues.
My question is as follows:
1. Is there any standard/architecture/best practices for data exchange of backing beans or other forms between two ADF Rich Faces based apps (in two separate ears)?
2. Has someone found anything similar to an applicationScope that works across applications?
I would appreciate any ideas.
Thanks very much,
Edited by: user11219846 on Jul 23, 2009 2:38 PM
Edited by: user11219846 on Jul 23, 2009 2:42 PM

Hi,
its not an ADF Faces problem, but not possible in Java EE. You can however fallback to vendor specific implementations like in WLS. From the WebLogic documentation : http://e-docs.bea.com/wls/docs103/webapp/sessions.html
Enabling Web applications to share the same session*
By default, Web applications do not share the same session. If you would like Web applications to share the same session, you can configure the session descriptor at the application level in the weblogic-application.xml deployment descriptor. To enable Web applications to share the same session, set the sharing-enabled attribute in the session descriptor to true in the weblogic-application.xml deployment descriptor. See “sharing-enabled” in session-descriptor.
The session descriptor configuration that you specify at the application level overrides any session descriptor configuration that you specify at the Web application level for all of the Web applications in the application. If you set the sharing-enabled attribute to true at the Web application level, it will be ignored.
All Web applications in an application are automatically started using the same session instance if you specify the session descriptor in the weblogic-application.xml deployment descriptor and set the sharing-enabled attribute to true as in the following example:
+<?xml version="1.0" encoding="ISO-8859-1"?>+
+<weblogic-application xmlns="http://www.bea.com/ns/weblogic/90";;>+
+...+
<session-descriptor>
+<persistent-store-type>memory</persistent-store-type>+
+<sharing-enabled>true</sharing-enabled>+
+...+
+</session-descriptor>+
+...+
+</weblogic-application>+
Frank

How to query data from database and store it into Managed Bean ?

Hi all,
In our application we have requirement to store information within Managed Bean to be accessed by ADF pages.
The information is stored in database tables.
The question is :
What is the efficient / recommended way to do that ?
I do not use apps module to query the data because the information is required in View layer not the model layer
Thank you for your help,
xtanto

Xtanto,
if the information is stored in the database then the question is if there is a database connect open already. If yes, then why not using this connection to query for the data you want to access and store. Alternatively you can directly open a JDBC connection in a managed bean or access an EJB session bean. However, this comes with the price of an extra database connection.
Make sure the managed bean is in session scope if you want to share the information without re-fetching it
Frank

Managed Bean Help for Definition Help

I am working on creating Managed Bean Help for Definition Help as described in ‘19.5.3 How to Create Managed Bean Help’ section of the Web User Interface Developer's Guide fpr ADF. Using JDev Version 11.1.2.1.0.
Thought I had all the artifacts assembled but when I run the log message is: <ELHelpProvider> <_getTranslationMap> ELHelpProvider's helpSourceExpression is null.
Any suggestions would be greatly appreciated.
Here is the managed bean:
public class ELHelpProviderProjRequest extends ELHelpProvider {
    public ELHelpProviderProjRequest() {
    /* To use the HelpProvider, the EL expression in the helpTopicId attribute must point to a Map, otherwise
       * you will get a coerceToType error. */
    public Map<String, String> getHelpMap()
          Iterator iterator = _HELP_MAP.entrySet().iterator();
          while(iterator. hasNext()){
          System.out.println("hash map entry " + iterator.next());
        return _HELP_MAP;
    static private final Map<String, String> _HELP_MAP = new HashMap<String, String>();
        static {
          // each element [put] can be for a separate helpTopicId attribute
          _HELP_MAP.put("MAPHELP_CATEGORY_CAPITAL_DEFINITION", "Map value for credit card definition");
          _HELP_MAP.put("MAPHELP_CATEGORY_OTHER_DEFINITION", "Map value for credit card instructions");
} Here is the adf-setting.xml in Application sources / META-INF:
<?xml version="1.0" encoding="windows-1252" ?>
<adf-settings xmlns="http://xmlns.oracle.com/adf/settings" >
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/settings">
<help-provider prefix="MAPHELP_">
    <help-provider-class>
        com.corpnet.abc.util.ELHelpProviderProjRequest
    </help-provider-class>
    <property>
      <property-name>helpSource</property-name>
      <value>#{helpTranslationMap.helpMap}</value>
    </property>
</help-provider>
</adf-faces-config>
</adf-settings>Here is the faces-config:
<managed-bean>
    <managed-bean-name>helpTranslationMap</managed-bean-name>
    <managed-bean-class> com.corpnet.abc.util.ELHelpProviderProjRequest </managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
</managed-bean>Here is the helpTopicId in the inputText component:
<af:inputText value="Test" inlineStyle="font-weight: bold;" id="it31" simple="true" helpTopicId="MAPHELP_CATEGORY_CAPITAL" readOnly="true"/>

Register the managed-bean as a help provider in the adf-settings xml like:
Example 19-9 Registering a Managed Bean as a Help Provider
<adf-settings xmlns="http://xmlns.oracle.com/adf/settings">
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/settings">
<help-provider prefix="MAPHELP_">
<help-provider-class>
oracle.adf.view.rich.help.ELHelpProvider
</help-provider-class>
<property>
<property-name>helpSource</property-name>
<value>#{helpTranslationMap.helpMap}</value>
</property>
</help-provider>
</adf-faces-config>
</adf-settings>
As you've pointed out, Review section 19.5.3 for more details -> http://docs.oracle.com/cd/E24382_01/web.1112/e16181/af_message.htm#CHDHIGIA
You could also investigate use the OHW product available here: http://www.oracle.com/technetwork/developer-tools/help/index-083946.html

How to change MANAGED-BEAN-SCOPE??????

Hi Gurus,
How to change the managed-bean-scope? In my ADF application I have created one backing bean which has attched with the page fragment. I cant able to set the bean scope other than REQUEST....
If I set the bean scope request, then page and the inside fragment is rendering without any error. But I need to make that bean scope to pageFlow... but if I do, getting the below error. Non of the scopes are working except request... Please help me how to set the other scope which will solve my major development issue!!!!
Error:
Error trying to include:viewId:/advsearch-flow-definition/advUserSearch uri:/app/advUserSearch.jsffjavax.faces.FacesException: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'UserSearch' resolved to null
My ADFC-Config.xml:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
<managed-bean>
<managed-bean-name>backing_app_idm</managed-bean-name>
<managed-bean-class>edu.syr.oim.backing.app.Idm</managed-bean-class>
<managed-bean-scope>backingBean</managed-bean-scope>

</managed-bean>
<managed-bean>
<managed-bean-name>backing_app_userMgmt</managed-bean-name>
<managed-bean-class>edu.syr.oim.backing.app.UserMgmt</managed-bean-class>
<managed-bean-scope>backingBean</managed-bean-scope>

</managed-bean>
*<managed-bean>*
*<managed-bean-name>UserSearch</managed-bean-name>*
*<managed-bean-class>edu.syr.oim.backing.app.UserSearch</managed-bean-class>*
*<managed-bean-scope>request</managed-bean-scope>*
*</managed-bean>*
</adfc-config>
-kln
Edited by: klogube on Jan 14, 2010 7:23 AM

*public class UserSearch {*
private RichTable searchResultTable;
private Row currentRow;
private String selectedNetID;
private RichInputText inputOne;
private RichInputText inputTwo;
private RichInputText inputThree;
private RichSelectOneChoice choiceOne;
private RichSelectOneChoice choiceTwo;
private RichSelectOneChoice choiceThree;
private RichRegion region;
private String choiceOneVal;
private String choiceTwoVal;
private String choiceThreeVal;
DCBindingContainer bindings;
int choiceOneRowIndex;
int choiceTwoRowIndex;
int choiceThreeRowIndex;
Row choiceOnerw;
Row choiceTworw;
Row choiceThreerw;
String choiceOneUserSelected = null;
String choiceTwoUserSelected = null;
String choiceThreeUserSelected = null;
static String txnTypeOne = null;
static String txnTypeTwo = null;
static String txnTypeThree = null;
String netid;
RequestContext requestContext = RequestContext.getCurrentInstance();
HashMap rcBackupHM = new HashMap();
FacesContext facesContext = FacesContext.getCurrentInstance();
Application app = facesContext.getApplication();
ExpressionFactory elFactory = app.getExpressionFactory();
ELContext elContext = facesContext.getELContext();
FacesContext fc = FacesContext.getCurrentInstance();
HttpServletRequest request = (HttpServletRequest)fc.getExternalContext().getRequest();
HttpSession session = request.getSession();
*public UserSearch() {*
*public String userSelected() {*
FacesCtrlHierNodeBinding binding = (FacesCtrlHierNodeBinding) searchResultTable.getSelectedRowData();
currentRow = binding.getRow();
selectedNetID = (String) currentRow.getAttribute("netid");
requestContext.getPageFlowScope().put("netid",selectedNetID);
return "goToDetails";
** Invoke this method when user double click the row in searchResult*
*public void doDbClick(ClientEvent clientEvent) {*
FacesCtrlHierNodeBinding binding = (FacesCtrlHierNodeBinding) searchResultTable.getSelectedRowData();
currentRow = binding.getRow();
selectedNetID = (String) currentRow.getAttribute("netid");
requestContext.getPageFlowScope().put("netid",selectedNetID);
*try{*
FacesContext facesCtx = FacesContext.getCurrentInstance();
NavigationHandler nh = facesCtx.getApplication().getNavigationHandler();
nh.handleNavigation(facesCtx, "", "goDetails");
*// Refresh the current region; advse1 is the id of the region component inside jspx page*
AdfFacesContext.getCurrentInstance().addPartialTarget(region);
*catch(Exception e){ }*
*public void setSearchResultTable(RichTable searchResultTable) {*
this.searchResultTable = searchResultTable;
*public RichTable getSearchResultTable() {*
return searchResultTable;
*public void setInputOne(RichInputText inputOne) {*
this.inputOne = inputOne;
*public RichInputText getInputOne() {*
return inputOne;
*public void setInputTwo(RichInputText inputTwo) {*
this.inputTwo = inputTwo;
*public RichInputText getInputTwo() {*
return inputTwo;
*public void setInputThree(RichInputText inputThree) {*
this.inputThree = inputThree;
*public RichInputText getInputThree() {*
return inputThree;
*public void setChoiceOne(RichSelectOneChoice choiceOne) {*
this.choiceOne = choiceOne;
*public RichSelectOneChoice getChoiceOne() {*
return choiceOne;
*public void setChoiceTwo(RichSelectOneChoice choiceTwo) {*
this.choiceTwo = choiceTwo;
*public RichSelectOneChoice getChoiceTwo() {*
return choiceTwo;
*public void setChoiceThree(RichSelectOneChoice choiceThree) {*
this.choiceThree = choiceThree;
*public RichSelectOneChoice getChoiceThree() {*
return choiceThree;
*public void setChoiceOneVal(String choiceOneVal) {*
this.choiceOneVal = choiceOneVal;
*public String getChoiceOneVal() {*
return choiceOneVal;
*public void setChoiceTwoVal(String choiceTwoVal) {*
this.choiceTwoVal = choiceTwoVal;
*public String getChoiceTwoVal() {*
return choiceTwoVal;
*public void setChoiceThreeVal(String choiceThreeVal) {*
this.choiceThreeVal = choiceThreeVal;
*public String getChoiceThreeVal() {*
return choiceThreeVal;
*public void setRegion(RichRegion region) {*
this.region = region;
*public RichRegion getRegion() {*
return region;
Can you please explain how to define the 2nd bean in the pageFlowScope and injnect?...bacially my problem is I am loosing the pageFlowScope value when I navigate from first page to next page which I am setting by this above class....I need to carry forward the netid which I am losing ...any idea plz

Urgent - can't set managed bean value using a form, getting null

I have a form with a bean -- unbelievably, I can't get the values entered into the form by the user to get stored into the bean. Everything is null... I've looked at a zillion examples, posts and compared etc...yet still can't see what is missing.
Here's part of a trace :
[cc]Dec-31 01:25:02 ApplicationImpl - Created bean resourceBean successfully
[cc]Dec-31 01:25:02 ApplicationImpl - Storing resourceBean in scope request
[cc]Dec-31 01:25:02 VariableResolverImpl - resolveVariable: Resolved variable:id=null name=null
[cc]Dec-31 01:25:02 ValueBindingImpl - getValue Result:id=null name=null
[cc]Dec-31 01:25:02 ValueBindingImpl - -->Returning id=null name=null
If you have any ideas, please let me know--it seems just as I solve one JSF issue, I run into another on unexpectedly simple things.
Here's the ResourceBean.java, the bean-config.xml and my jsp.
package com.intalio.qa.tcm.view.beans;
import java.util.Map;
import javax.faces.context.FacesContext;
import javax.faces.model.SelectItem;
import org.apache.log4j.Logger;
import com.intalio.qa.exceptions.DuplicateIdException;
import com.intalio.qa.tcm.model.Resource;
import com.intalio.qa.tcm.view.builders.ResourceBuilder;
import com.intalio.qa.tcm.view.util.FacesUtils;
* Resource backing bean.
public class ResourceBean extends RootBean {
     * Class logger
     public static final Logger LOG =
          Logger.getLogger(ResourceBean.class);
* The Resource id
     private String id = null;
     * The Resource name
     private String name = null;
* Description
private String description= null;
     * the resource type id associated with the Resource
     private String resourceTypeId= null;
     private static SelectItem[] resourceTypeIds = new SelectItem[] {
          new SelectItem("External Software"),
          new SelectItem("Hardware"),
          new SelectItem("Intalio Product Software"),
          new SelectItem("Machine - Dual CPU"),
          new SelectItem("Machine - CPU Single"),
          new SelectItem("Memory - UNIX"),
          new SelectItem("Memory - Windows") };
* @return Returns the resourceTypeIds.
public SelectItem[] getResourceTypeIds() {
return resourceTypeIds;
* @param resourceTypeIds The resourceTypeIds to set.
public void setResourceTypeIds(SelectItem[] typeIds) {
resourceTypeIds = typeIds;
     * Default constructor.
     public ResourceBean() {
super();
init();
     * Initializes ResourceBean.
     * @see RootBean#init()
     protected void init() {
     /*True, but I'd strongly recommend instead using:
FacesContext fContext = FacesContext.getCurrentInstance();
Map requestParams = fContext.getExternalContext().getRequestParameterMap();
String companyId = (String) requestParams.get("companyID");
The getRequest(), getSession(), and getContext() methods of ExternalContext should only be used as a last resort.*/
     * Backing bean action to update Resource.
     * @return the navigation result
     public String updateAction() {
          LOG.info("updateAction is invoked");
          try {
               Resource Resource = ResourceBuilder.createResource(this);
               LOG.info("ResourceId = " + Resource.getId());
          //     viewServicesManager.getResourceService().updateResource(Resource);
          } catch (Exception e) {
               String msg = "Could not update Resource";
               LOG.error(msg, e);
               FacesUtils.addErrorMessage(msg + ": Internal Error.");
               return ActionResult.FAILURE;
          LOG.info("Resource with id of " + id + " was updated successfully.");
          return ActionResult.SUCCESS;
     * Backing bean action to create a new Resource.
     * @return the navigation result
     public String addAction() {
          try {
               Resource resource = ResourceBuilder.createResource(this);
LOG.info("resource created: " + resource.getName() + " with typeId = " + resource.getResourceTypeId());
               viewServicesManager.getResourceService().saveResource(resource);
          } catch (DuplicateIdException de) {
               String msg = "This id already exists";
               LOG.info(msg);
               FacesUtils.addErrorMessage(msg);
               return ActionResult.RETRY;
          } catch (Exception e) {
               String msg = "Could not save Resource";
               LOG.error(msg, e);
               FacesUtils.addErrorMessage(msg + ": Internal Error");
               return ActionResult.FAILURE;
          String msg = "Resource with id of " + id + " was created successfully.";
          LOG.info(msg);
          return ActionResult.SUCCESS;
     * Backing bean action to delete Resource.
     * @return the navigation result
     public String deleteAction() {
          LOG.info("deleteAction is invoked");
          try {
     //          Resource Resource = ResourceBuilder.createResource(this);
     //          viewServicesManager.getResourceService().deleteResource(Resource);
               //remove the ResourceList inside the cache
//               FacesUtils.resetManagedBean(BeanNames.RESOURCE_LIST_BEAN);
          } catch (Exception e) {
               String msg = "Could not delete Resource. ";
               LOG.error(msg, e);
               FacesUtils.addErrorMessage(null, msg + "Internal Error.");
               return ActionResult.FAILURE;
          String msg = "Resource with id of " + id + " was deleted successfully.";
          LOG.info(msg);
          FacesUtils.addInfoMessage(msg);
          return ActionResult.SUCCESS;
     public String getId() {
          return id;
     * Invoked by the JSF managed bean facility.
     * <p>
     * The id is from the request parameter.
     * If the id is not null, by using the id as the key,
     * the Resource bean is initialized.
     * @param newQueryId the query id from request parameter
     public void setId(String newId) {
          LOG.info("setId " + newId);
          id = newId;
     public String getName() {
          return name;
     public void setName(String newName) {
          name = newName;
     public String getDescription() {
          return description;
     public void setDescription(String newDescription) {
          description = newDescription;
     public String getResourceTypeId() {
          return resourceTypeId;
     public void setResourceTypeId(String newResourceTypeId) {
          resourceTypeId = newResourceTypeId;
     public String toString() {
          return "id=" + id + " name=" + name;
     
     <managed-bean>
          <description>
               Managed bean
          </description>
          <managed-bean-name>applicationBean</managed-bean-name>
          <managed-bean-class>
               com.intalio.qa.tcm.view.beans.ApplicationBean
          </managed-bean-class>
          <managed-bean-scope>application</managed-bean-scope>
          <managed-property>
               <property-name>viewServicesManager</property-name>
               <value>#{viewServicesManagerBean}</value>
          </managed-property>
          </managed-bean>
     <managed-bean>
          <description>
               View service manager impl for business services
          </description>
          <managed-bean-name>viewServicesManagerBean</managed-bean-name>
          <managed-bean-class>
               com.intalio.qa.tcm.view.beans.ViewServicesManagerBean</managed-bean-class>
          <managed-bean-scope>application</managed-bean-scope>
     </managed-bean>
     <managed-bean>
          <description>
               Backing bean that contains product information.
          </description>
          <managed-bean-name>resourceBean</managed-bean-name>
          <managed-bean-class>
               com.intalio.qa.tcm.view.beans.ResourceBean
          </managed-bean-class>
          <managed-bean-scope>request</managed-bean-scope>
          <managed-property>
               <property-name>viewServicesManager</property-name>
               <value>#{viewServicesManagerBean}</value>
          </managed-property>
     </managed-bean>
</faces-config>
<f:view>
     <h:form id="createResourceForm" target="dataFrame">
          <h:outputText value="#{applicationBean.dummyVariable}" rendered="true" />
          <div align="center">
          <head>
          <link href="../../css/stylesheet.css" rel="stylesheet" type="text/css">
          <FONT color="#191970" size="4" face="Arial">Resources View</FONT>
          </head>
          <table style="margin-top: 2%" width="35%" cellpadding="10">
               <div align="left">
               <FONT color="#191970" size="3" face="Arial">Update Resources </FONT>
               </div>
               <tr>
                    <td align="center" valign="top" align="center" style="" bgcolor="white" />
                    <table>
                         <tbody>
                              <tr>
                                   <td align="left" styleClass="header" width="100" />
                                   <td align="left" width="450" />
                              </tr>
                              <tr>
                                   <td align="right" width="100"><h:outputText value="Id" /></td>
                                   <td align="left" width="450"><h:inputText value="#{resourceBean.id}" id="id"/> <h:message for="id" styleClass="errorMessage" /></td>
                              </tr>
                              <tr>
                                   <td align="right" width="100"><h:outputText value="Name" /></td>
                                   <td align="left" width="450"><h:inputText value="#{resourceBean.name}" id="name" /> <h:message for="name" styleClass="errorMessage" /></td>
                              </tr>
                              <tr>
                                   
     
     <td width="30%" align="left" valign="top"><h:form id="buttonCommandsForm">
          <h:panelGroup id="buttons">
               <h:panelGrid columns="1" cellspacing="1" cellpadding="2" border="0" bgcolor="white">
                    <h:commandButton value="Add" style="height:21px; width:51px;font-size:8pt; font-color: black;" action="#{resourceBean.addAction}">
                    </h:commandButton>
                    <h:commandButton id="deleteCB" value="Delete" style="height:21px; width:51px;font-size:8pt" action="#{resourceBean.deleteAction}">
                    </h:commandButton>
                    <h:commandButton id="spaceFillerButton" style="height:21px; width:51px;font-size:8pt;background-color: #ffffff;color: #ffffff;border: 0px;">
                    </h:commandButton>
                    <h:commandButton id="saveCB" value="Save" style="height:21px; width:51px;font-size:8pt" action="#{resourceBean.saveAction}">
                    </h:commandButton>
                    <h:commandButton id="updateCB" value="Update" style="height:21px; width:51px;font-size:8pt" action="#{resourceBean.updateAction}">
                    </h:commandButton>
               </h:panelGrid>
          </h:panelGroup>
     </h:form> </td>
     </tr>
     </table>
     <HR align="center" size="2" width="60%" />
     
     </div>
</f:view>
THANKS.
-L

I solved this.
Since I was testing the action code only, I didn't define a navigation entry corresponding to the action string returned for this button:
<h:commandButton value="Add" style="height:21px; width:51px;font-size:8pt; font-color: black;" action="#{resourceBean.addAction}">
</h:commandButton>After I added a nav definition, it worked. I don't know why at this point. I suspect a key step in the lifecycle was pre-empted...someone else can probably explain why. If I get a chance to research it after I'm done with my project, I'll update this post.
Thanks.
-L

JSF - Best Practice For Using Managed Bean

I want to discuss what is the best practice for managed bean usage, especially using session scope or request scope to build database driven pages
---- Session Bean ----
- In the book Core Java Server Faces, the author mentioned that most of the cases session bean should be used, unless the processing is passed on to other handler. Since JSF can store the state on client side, i think storing everything in session is not a big memory concern. (can some expert confirm this is true?) Session objects are easy to manage and states can be shared across the pages. It can make programming easy.
In the case of a page binded to a resultset, the bean usually helds a java.util.List object for the result, which is intialized in the constructor by query the database first. However, this approach has a problem: when user navigates to other page and comes back, the data is not refreshed. You can of course solve the problem by issuing query everytime in your getXXX method. But you need to be very careful that you don't bind this XXX property too many times. In the case of querying in getXXX, setXXX is also tricky as you don't have a member to set. You usually don't want to persist the resultset changes in the setXXX as the changes may not be final, in stead, you want to handle in the actionlistener (like a save(actionevent)).
I would glad to see your thought on this.
--- Request Bean ---
request bean is initialized everytime a reuqest is made. It sometimes drove me nuts because JSF seems not to be every consistent in updating model values. Suppose you have a page showing parent-children a list of records from database, and you also allow user to change directly on the children. if I hbind the parent to a bean called #{Parent} and you bind the children to ADF table (value="#{Parent.children}" var="rowValue". If I set Parent as a request scope, the setChildren method is never called when I submit the form. Not sure if this is just for ADF or it is JSF problem. But if you change the bean to session scope, everything works fine.
I believe JSF doesn't update the bindings for all component attributes. It only update the input component value binding. Some one please verify this is true.
In many cases, i found request bean is very hard to work with if there are lots of updates. (I have lots of trouble with update the binding value for rendered attributes).
However, request bean is working fine for read only pages and simple binded forms. It definitely frees up memory quicker than session bean.
----- any comments or opinions are welcome!!! ------

I think it should be either Option 2 or Option 3.
Option 2 would be necessary if the bean data depends on some request parameters.
(Example: Getting customer bean for a particular customer id)
Otherwise Option 3 seems the reasonable approach.
But, I am also pondering on this issue. The above are just my initial thoughts.

Bind a UiComponent to manage bean

Hi
jdeveloper 11.1.1.7
i need to refresh a inputText programatically .so
How can i assign a inputText to UiComponent in the managed bean ?
thanks

The parameter you pass to the addPartialTarget method is indeed the java representation of a ui component. In your code I miss the component you want to refresh.
The normal way to get the component reference is to look it up in the page structure by its id. For this you can use e.g.
Edwin Biemond's blog http://biemond.blogspot.com/2009/11/find-uicomponent-in-adf-task-flow.html
Binding the component directly to the bean is only a possibility if the beans memory scope is request.
Timo

Managed beans scalability

Hi guys,
It seems to be a standard practice for each JSP to have a corresponding backing bean. This seems to work fairly well for a relatively small Web applications.
Web applications that we deploy sometimes consist of thousands JSPs (as high as 10 thousand and even more). Even though managed beans are created lazily, just loading them into a JVM takes up a fair amount of memory. We've discovered in the past that web containers do not have the tendency of unloading classes once all class instances are destroyed. Therefore, a large number of backing bean classes in itself may present a problem.
We delt with this issue in the pre-JSF implementaiton of our Web application quite effectively. However, our model beans needed an ID of the HTML component when they were retrieving its value.
I wonder if any thought has been given to such scalability issues?
I do not believe that using single backing bean for multiple JSPs really solves the problem either. It will make development of the application quite messy...
Any help, thoughts, ideas would be greatly appreciated.
Vadim.

I am wondering whether my question below is simply silly, or nobody really had to deal with these kinds of issues?
Thanks in advance,
Vadim.

MANAGED BEAN BOOK

Hi ,
I am using jdeveloper 11 g release 2 .
Can anyone assist with books to implement the managed bean in adf?
Regards
steve kalenga

I'm not aware of a book on this. However, creating a manged bean is pretty simple as you only have to create a java class and then configure this class in the adfc-config.xml if you use ADF.
You should lookup memory scopes in the docs as managed beans should always be in the smalest scope possible for the use case.
And very impoertant: don't use automatic binding of components!
Timo

Managed Beans and Data Access Object

I have a question / need help understanding how to configure backing bean and model objects so that memory and object creation/deletion is done as efficiently as possible.
1. I have a .jsf page with a form and a commandbutton that submits the form inputs to a backing bean (enrollispbean is backing bean)
<h:commandButton value="Enter" action="#{enrollispbean.insert}"/>
2. The backing bean is used for form handling - the insert() method is used to read the data fields from the form and create a SQL string that will be submitted to a model object, DbInsert, that is used as a generic data access object that connects to the database and insert the SQL string:
public class EnrollIspBean {
private String beanvar1="";
private String beanvar2= "";
// DbInsert is data access object
private DbInsert dbinsert = new DbInsert();
public String insert (){
String sqlstmt;
sqlstmt = "INSERT INTO ispmain VALUES(beanvar1, beanvar2,..)"
dbinsert.insert(sqlstmt);
return "success"; }
3. DbInsert is the data access object that contains a method, insert(), that accepts a sql string to insert into the database. This method contains the code to obtain a connection from the database connection pool and then execute the sql statement (note: error checking code not shown):
public class DbInsert {
public void insert(String sqlstmt) throws SQLException {
Connection conn = null;
GetDBConnection getdbconnection = new GetDBConnection();
PreparedStatement stmt = null;
conn = getdbconnection.getdbconn();
stmt = conn.prepareStatement(sqlstmt);
stmt.executeUpdate();
stmt.close();
conn.close();
return;
Where I need help understanding is how to set up the scope for the managed beans and data access object. Currently, I have the backing bean within the session scope (using the facesconfig.xml file). My main question is how to set up the scope for the Data Access Object - currently I do not have it as a managed bean within facesconfig.xml. Instead I am creating a new instance within the backing bean:
private DbInsert dbinsert = new DbInsert();
Is this the best way to do this? Will the DBInsert object now be tied to the session scope of the backing bean (i.e., when backing bean is deleted, the DbInsert object will be deleted from session scope as well.)
Ideally I would like the data access object to be available as a shared object throughout the life of the application. When I was programming using a servlet approach, I would have created a servlet to load on startup. Now that I'm using java server faces, I'm confused about the scope / how to efficiently set up a data access object that I want to be available to all backing beans in the application.
tnanks for any help understanding this.
Tom

I was thinking about setting the data access object as application scope so that it can be used by an backing bean to execute sql statements.
If I do set it as application scope, however, if I do this, do I still need to declare a new instance of the object from within each bean that uses the object?
For example do I need to declare a new instance of the data access object from within the bean? or, should I assume that there is always an instance of the bean available in the application scope, and if so, how do I reference it from within the bean?
Bean Code:
public class EnrollIspBean {
// DbInsert is data access object
private DbInsert dbinsert = new DbInsert();
Finally, I understand performance may be an issue if I have one instance of the data access object available in the application scope - is there a way to make multiple instances available in the application scope?
thanks

Hot-(re)deploy of managed beans

Using JDeveloper 11 (I know, preview, but my question targets lots of versions..)
When I change a .jsp the file is automatically redeployed.
When I change a .java file (for example a managed Bean) and compile it into a .class, the old version is used.
To see the result of my change I restart the OC4J (takes lot of time).
--> Is there an easy way to hot-(re)deploy classes on OC4J / JDeveloper? (for example: something in my memory tells me Tomcat can run in a special mode, in which classes are also checked for updated versions and loaded when needed)
Thanks,
regards
Stephan
Message was edited by:
Stephan van Hoof

Hi,
this question is better asked on the OC4J forum because JDeveloper consumes what is provided from them. I know there were plans for hot deployment, but I am not sure this is in 11 yet. So you better ask on this forum. In preview JDeveloper 11 doesn't have hot deployment for managed beans.
Please send questions regarding JDeveloper 11 to JDeveloper and OC4J 11g Technology Preview
thanks
Frank

Disabling a checkbox which is in a table, from managed bean

disabling a checkbox which is in a table, from managed bean -
i am able to iterate table and get/set value of checkbox but i want to disable it, how can i do that?
FacesContext facesContext = FacesContext.getCurrentInstance();
Application app = facesContext.getApplication();
ExpressionFactory elFactory = app.getExpressionFactory();
ELContext elContext = facesContext.getELContext();
ValueExpression valueExp = elFactory.createValueExpression(elContext, "#{bindings}", Object.class);
DCBindingContainer bindings = (DCBindingContainer) valueExp.getValue(elContext);
DCIteratorBinding iter = bindings.findIteratorBinding("dogsIterator");
RowSetIterator rit = iter.getRowSetIterator();
rit.reset();
while(rit.hasNext()) {
Row currentRow = rit.next();
Attribute attr = (Attribute)row.getAttribute("checked");
what code should come here to disable checkbox?
rit.closeRowSetIterator();
thanks.

Wes Fang wrote:
You might find it easier to simply use EL and evaluate that value on the disable property:
<af:column ...>
<af:selectBooleanCheckbox ... disabled="#{row.bindings.checked.inputValue==YOUR_DISABLE_VALUE?true:false}"/>
</af:column>
i used this approach.
kept a bean in session and used it's property in disabled attribute - now setting this property in my bean...

Sharing managed beans

Ok �. This is driving me nuts. I�m relatively new to JSF (2 week profession  ), and I may not have grasped the concept of Managed Beans. The problem is detailed below:
Development Environment:
WebSphere Studio 1.5.2 � This creates a backing bean for each respective JSP page that is created, including setters and getters for each managed bean. The two backing beans I�ll talk about whilst specifying the problem are stored in session scope.
The Problem:
I can�t share data between two pages. On the first page I create managed bean in session scope and make this reusable (let�s say person). On the second page I add the reusable Person bean. The resulting entry in the faces.config file is:
<managed-bean>
<managed-bean-name>person</managed-bean-name>
<managed-bean-class>ibm.wlrs.model.PersonVO</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
Both pages however maintain an independent copy of the managed bean instead of JSF maintaining a shared one. I�ve looked at several documents, and too me it seems as though this bean should be shared between the two pages�� HELP!
On the first page I create a new Person object with the relevant details. This person is created upon a button click added to the backing beans managed bean.
//Page 1 add person from button click
public String doLnkInsertEntryAction() {
System.out.println("Insert");
     Person p1 = new Person();
     p1.setName("Duncan");
     setPerson(p1);
System.out.println(getPerson().getName());
//This prints the person�s name
     return "insert";
I have also setup a page load event to test that the person object stays in the session
//Page 1 page load
public void onPageLoadBegin(FacesContext facescontext) {
     System.out.println(getPerson().getName());
//Prints the person name that was added during the button click event� on Postback or even after going from page1 � page2 and back again.
On Page two if I try and access the managedBean contained within the session, the �name� will always print out as null.
//Page 2 page load
public void onPageLoadBegin(FacesContext facescontext) {
     System.out.println(getPerson().getName());
If I add an any information to the managed bean on page two i.e. person.setName(�Another�), this data stays in the session, only for page two though.
Is this how JSF is supposed to work? I though if a managed bean was stored in the session, the object (and it�s data) should be reusable between pages.
Sorry for the long post�. I though it would be worth while to try and be as specific as possible.
Thanks
Duncan

And� I still don�t understand why two independent
copies are kept by the pages�Because YOU create the copy.
JSF (exactly speaking the default VariableResolver) at first searches for an attribute in
request scope, then session scope, then application scope with the matching name.
Only when no attribute is found, it examines faces-config.xml, creates an instance of
the specified class, and stores the instance in the specified scope.
It never creates two instances with a same name.
I.E� On Page 1�. Several Person objects are stored in
a DataTable. The Vector containing the Person objects
is a managed bean bound to this data table. Upon a
button click I require to extract a person from the
data table and place it into the managed bean session
scope for person. Humm, I guess you misunderstand what the managed bean is.
h:dataTable has the "var" attribute which is used to refer each Person object.
JSF implements the "var" variable as a request scope attribute and re-binds it
to each Person object in the iteration. So, it is not a managed bean but is simply an attribute.
The entry of faces-config.xml is not required.
To know how to pass the selected row data to the next page, please see some
example using h:dataTable and javax.faces.model.DataModel.

Error while opening a popup from managed bean

Hi,
I am trying to open a popup from bean, after another popup is closed. When I open the second popup either through ActionListener(on first popup button) or DialogListener(on first popup), I am getting the below error on browser status bar(!); and the second popup doesn't open. There is no error in the log.
*'AdfPage.PAGE.findComponent(...)' is null or not an object.*
Although the popup id is there on the jspx page.
<af:popup id="confirmationStatus" binding="#{MyBean1.confirmationStatus}">
<af:dialog cancelVisible="false"
closeIconVisible="false" binding="#{MyBean1.d2}"
title="Appointment Confirmation Status">
<af:outputText value="Appointment is successfully confirmed"/>
</af:dialog>
</af:popup>
public void confirmAppointment_dialogListener(DialogEvent dialogEvent) {
FacesContext context = FacesContext.getCurrentInstance();
ExtendedRenderKitService service = Service.getRenderKitService(context, ExtendedRenderKitService.class);
String popupId = "confirmationStatus";
service.addScript(context,"AdfPage.PAGE.findComponent('" + popupId + "').show();");
Please tell me why my popup is not getting open from the managed bean and I am getting an error in below line.
service.addScript(context,"AdfPage.PAGE.findComponent('" + popupId + "').show();");

To find out the right address of a component related to an other component, open your page select the component you want to add a partial trigger, go to the partial trigger property, select the down arrow at the right end and select 'Edit'. Now look for the popup in the component tree shown on the left side. When you have found the popup shuffle it the the selected side and click OK. The string you see in the field is the full address of the popup related to he component you've selected. Try the string you see there in your bean code. Remove the string from the partial trigger property, it's just to get the correct path.
One other thing to check is that your popup has the ClientComponent property set to true.
Next thing to try, is to use AdfPage.PAGE.findComponentByAbsoluteId(...)
Timo

Memory leak - Managed beans kept in memory in ADF

Similar Messages

Maybe you are looking for