Taskflow managed bean

Hi,
I'm using JDev11/ADF. I was wondering if I can have something like a taskflow managed bean with taskflow scope and use the same base class and the same bean name in two different taskflows, which one with it's all bean "instance".
Tks.

Hi,
I got the answer for this question. Here is the code which you need to use in your managed bean to refresh the taskflow.
BindingContext bctx = BindingContext.getCurrent();> BindingContainer bindings = bctx.getCurrentBindingsEntry();
> DCTaskFlowBinding taskflowBinding = null;
> taskflowBinding = (DCTaskFlowBinding) bindings.get("CompletedActionsTF1");
>taskflowBinding.refresh();
Thanks,
Kiran

Similar Messages

How to include Managed bean class in build sciprt for taskflow (Jdev 11.4)

Hi,
I've developed a custom taskflow to be deployed in the webcenter spaces. The taskflow that I developed contains managed beans. I am using oracle provided build script with the sample application, to deploy custom taskflow. After the build, we don't see any .class files (managed bean files) in the generated war file. Once we deploy the taskflow into the space, it is failing may be because the managed bean class files are missing in the <taskflow>.war. Am i missing something? Should we specifically include the .class files in the build script?
Below is the oracle provide build script..
<?xml version="1.0" encoding="US-ASCII" ?>


<project name="WebCenterSpacesSharedLibExtension" default="all" basedir="."
xmlns:wls="oracle.webcenter.tools.wls">
<property file="../config.properties"/>
<property file="build.properties"/>
<import file="internal-targets.xml"/>
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="${jdeveloper.install.home.directory}/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar"/>
</classpath>
</taskdef>
<target name="clean-stage"
description="Cleans the output directory and generates the war"
depends="clean, stage"/>
<target name="deploy-shared-lib"
depends="init-wls"
description="Deploy the extending WebCenter shared library">
<echo> ---------------------------- </echo>
<echo> ${wls.userconfig} ${wls.userkey} ${wls.host}:${wls.port} ${oracle.jdeveloper.deploy.dir}/exploded ${wls.webcenter.app.target} ${customer.library.name}</echo>
<exec logerror="true"
executable="${jdeveloper.install.home.directory}/oracle_common/common/bin/${wlst.executable}"
dir="${jdeveloper.install.home.directory}/oracle_common/common/bin">

<arg line="${extending.spaces.home.dir}/WebCenterSpacesSharedLibExtension/extspaces.py ${wls.userconfig} ${wls.userkey} ${wls.host}:${wls.port} ${oracle.jdeveloper.deploy.dir}/exploded/${customer.library.name}.war ${wls.webcenter.app.target} ${customer.library.name}"/>


</exec>
<echo> ---------------------------- </echo>
<echo> Restarting the app </echo>
<echo> ---------------------------- </echo>
<exec logerror="true"
executable="${jdeveloper.install.home.directory}/oracle_common/common/bin/${wlst.executable}"
dir="${jdeveloper.install.home.directory}/oracle_common/common/bin">
<arg line="${extending.spaces.home.dir}/WebCenterSpacesSharedLibExtension/redepwc.py ${wls.userconfig} ${wls.userkey} ${wls.host}:${wls.port} "/>
</exec>
</target>
</project>
Thanks in advance
Nitin

Hi,
I've developed a custom taskflow to be deployed in the webcenter spaces. The taskflow that I developed contains managed beans. I am using oracle provided build script with the sample application, to deploy custom taskflow. After the build, we don't see any .class files (managed bean files) in the generated war file. Once we deploy the taskflow into the space, it is failing may be because the managed bean class files are missing in the <taskflow>.war. Am i missing something? Should we specifically include the .class files in the build script?
Below is the oracle provide build script..
<?xml version="1.0" encoding="US-ASCII" ?>


<project name="WebCenterSpacesSharedLibExtension" default="all" basedir="."
xmlns:wls="oracle.webcenter.tools.wls">
<property file="../config.properties"/>
<property file="build.properties"/>
<import file="internal-targets.xml"/>
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="${jdeveloper.install.home.directory}/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar"/>
</classpath>
</taskdef>
<target name="clean-stage"
description="Cleans the output directory and generates the war"
depends="clean, stage"/>
<target name="deploy-shared-lib"
depends="init-wls"
description="Deploy the extending WebCenter shared library">
<echo> ---------------------------- </echo>
<echo> ${wls.userconfig} ${wls.userkey} ${wls.host}:${wls.port} ${oracle.jdeveloper.deploy.dir}/exploded ${wls.webcenter.app.target} ${customer.library.name}</echo>
<exec logerror="true"
executable="${jdeveloper.install.home.directory}/oracle_common/common/bin/${wlst.executable}"
dir="${jdeveloper.install.home.directory}/oracle_common/common/bin">

<arg line="${extending.spaces.home.dir}/WebCenterSpacesSharedLibExtension/extspaces.py ${wls.userconfig} ${wls.userkey} ${wls.host}:${wls.port} ${oracle.jdeveloper.deploy.dir}/exploded/${customer.library.name}.war ${wls.webcenter.app.target} ${customer.library.name}"/>


</exec>
<echo> ---------------------------- </echo>
<echo> Restarting the app </echo>
<echo> ---------------------------- </echo>
<exec logerror="true"
executable="${jdeveloper.install.home.directory}/oracle_common/common/bin/${wlst.executable}"
dir="${jdeveloper.install.home.directory}/oracle_common/common/bin">
<arg line="${extending.spaces.home.dir}/WebCenterSpacesSharedLibExtension/redepwc.py ${wls.userconfig} ${wls.userkey} ${wls.host}:${wls.port} "/>
</exec>
</target>
</project>
Thanks in advance
Nitin

Can you add a new managed bean when customizing taskflows?

Hi,
I see post on how to customize taskflows and most of the customization involves rendering changes such as showing/hiding parts of the page..
But I was thinking is it possible to create your own managed bean in Customization Role of JDeveloper?
I notice that when I right click some package, the New option is disabled by default? Does this mean that customization is limited to changing
only the UI/JSFF file? The documentation does not mention about this or it maybe that I could not find it.
What I would like is that, the new managed bean I define in my Customization Role will drive the UI.
Anybody has done customization at this level? Would like to know your thoughts please.
Is this possible or should I point my thinking in the other directions?
Thanks.
This is a Webcenter Portal Application by the way and I am looking into customizing an existing taskflow thru MDS means.
Webcenter 11G PS5

You cannot add a new managed bean via customization. Instead, these may be deployed as ADF Library jars within a shared library or as part of the Portal war.
Once a managed bean has been added as above, then it can be referenced within a taskflow customization. For e.g. you can add a new button with the action set to a method in the managed bean.

Session scope managed bean is not instantiating?

We have the need to use a session bean (rather than pageFlowScope) in our application. But it looks like the session beans are not being instantiated at run time like other beans are. I created a simple test case to verify. One bean, named "MySessionBean", defined in the task flow as Session scope, then referenced in a view with an input text box, value: #{sessionScope.MySessionBean.value1}. When I run the application, I just get PropertyNotFoundException, Target Unreachable, 'MySessionBean' returned null.
If I simply change the bean to use pageFlowScope, everything works fine.   I have debug code in the bean constructor, and it never gets called.   Is there some other step I am missing to have ADF instantiate the session bean?

No luck, I tried it in both adfc-config.xml, and faces-config.xml. I also tried moving the call to my view, from my bounded taskflow, into the adfc-config unbounded task flow, and then I ran that instead. Still got the same error.    Here is my code from the the last round of tests with the view called in the main adfc-config.xml unbounded taskflow:
adfc-config.xml:
<?xml version="1.0" encoding="windows-1252" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
      <view id="testView">
            <page>/testView.jspx</page>
      </view>
      <managed-bean id="__2">
      <managed-bean-name id="__5">MySessionBean</managed-bean-name>
      <managed-bean-class id="__4">test.MySessionBean</managed-bean-class>
      <managed-bean-scope id="__3">session</managed-bean-scope>
    </managed-bean>
</adfc-config>
testView.jspx:
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
          xmlns:f="http://java.sun.com/jsf/core"
          xmlns:h="http://java.sun.com/jsf/html"
          xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=UTF-8"/>
<f:view>
    <af:document id="d1">
      <af:form id="f1">
        <af:inputText label="Label 1" id="it1"
                      value="#{sessionScope.MySessionBean.value1}"/>
      </af:form>
    </af:document>
</f:view>
</jsp:root>
MySessionBean.java:
package test;
public class MySessionBean {
    private String value1="Hello World";
    public MySessionBean() {
        super();
    public void setValue1(String value1) {
        this.value1 = value1;
    public String getValue1() {
        return value1;

Error message on restart: Failed to register application management beans

We are receiving an error when deploying custom task flows to the spaces instance in our Development environment and are experiencing the following problems:
Custom taskflow instances are all being "overwritten" by a single parameter (we have a webcam 'widget' each space points do a different location, but when we deploy they all suddenly point to the same place - this is not reflected in the parameters for the instance of the task flow).
Errors we are finding when we deploy:
Message Level     1
Relationship ID     0
Component     xx_xx_Spaces
Module     oracle.webcenter.webcenterapp.internal.view.webapp
Host     xx.xx.com
Host IP Address     xx.xx.xx.xx
Thread ID     [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'
ECID     014fc7558b241cc9:-13d743d3:1367e1ed952:-8000-000000000001096f
Supplemental Detail     javax.management.InstanceAlreadyExistsException: oracle.webcenter.community:name=LoadTranslationsMXBeanImpl,type=LoadTranslationsMXBeanImpl,Application=webcenter,ApplicationName=webcenter,ApplicationVersion=11.1.1.4.0
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$27.run(WLSMBeanServerInterceptorBase.java:714)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.registerMBean(WLSMBeanServerInterceptorBase.java:709)
at weblogic.management.mbeanservers.internal.JMXContextInterceptor.registerMBean(JMXContextInterceptor.java:445)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$27.run(WLSMBeanServerInterceptorBase.java:712)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.registerMBean(WLSMBeanServerInterceptorBase.java:709)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.registerMBean(WLSMBeanServer.java:462)
at oracle.as.jmx.framework.wls.spi.security.PrivilegedMBeanServerInterceptor$1.run(PrivilegedMBeanServerInterceptor.java:55)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at oracle.as.jmx.framework.wls.spi.security.PrivilegedMBeanServerInterceptor.registerMBean(PrivilegedMBeanServerInterceptor.java:60)
at oracle.webcenter.webcenterapp.internal.view.webapp.WebCenterAppContextListener.createAndRegisterMBeans(WebCenterAppContextListener.java:389)
at oracle.webcenter.webcenterapp.internal.view.webapp.WebCenterAppContextListener.contextInitialized(WebCenterAppContextListener.java:233)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:485)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:637)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)..
Message Level     1
Relationship ID     0
Component     xx_xx_Spaces
Module     oracle.webcenter.webcenterapp.internal.view.webapp
Host     xx.xx.com
Host IP Address     xx.xx.xx.xx
Thread ID     [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'
ECID     014fc7558b241cc9:-13d743d3:1367e1ed952:-8000-000000000001096f
Message     Failed to register application management beans
I have searched please help.
Edited by: jrickoi on Apr 6, 2012 2:38 PM
Edited by: jrickoi on Apr 6, 2012 3:02 PM

I have no idea except to suggest you contact them.

How to open a jspx in a popup from managed bean.

Hello,
I'm using Studio Edition Version 11.1.1.4.0.
I have a JSPX that is to be used as an application monitor screen. So it contains 5 af:tables with plenty of columns & query search criteria. Each of the tables has context sensitive menus as well as double click functionality.
When I write everything in a single JSPX, the code functions as expected. i.e. menu items & double click actions open new popups with requisite data. However, single JSPX becomes huge in size and hence difficult to maintain.
When I transfer code to another JSPX, How do I call the new JSPX in a popup from the managed bean?
Regards,
Amar

Try this:
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/53-taskflow-in-popup-169196.pdf

How to call different managed bean methods on a page template button

Dear All,
Use Case:
I have a Page Template and inside this page template is a popup screen which is common to all my
pages. My popup has OK and Cancel button only.
My question is this, there are lots of pages that uses this template.
How is it possible to invoke a managed bean methods dialoglistener when say for example the user clicks the OK button?
One thing common among the pages is that they are included in some kind of a taskflow and I have configured
a managedbean in a pageflowscope variable in each taskflow and I just wanted to pass the
My Template
     - TaskFlow 1 (ManagedBean1.dialogListener)
     - TaskFlow 2 (ManagedBean2.dialogListener)
     - TaskFlow 3 (ManagedBean3.dialogListener)
Each dialog listener does different things.
How to do this?
JDEV 11G PS3
Thanks

Found my answer here... http://www.oracle.com/technetwork/developer-tools/adf/learnmore/79-global-template-button-strategy-360139.pdf
Thanks!

@EJB not working for managed beans in adfc-config

using adf 11.1.1.3
We have an application that uses EJB (deployed on the same WLS as our application). We notice that when we create managed beans in the adfc-config and use the @EJB annotation to get an instance of the sessionbean, it is not working.
The error we get is a simple nullPointerexception pointing to the EJB.
When we register the bean in faces-config.xml instead of adfc-config.xml, we do get an instance of the EJB.
I also get a nullpointerException when i add the managed bean to a taskflow instead of the adfc-config.
This is an example of the bean:
public class HomeTest {
    @EJB
    MyService service;
    public HomeTest() {
    public List getData(){
      return service.getSomedata();
}When i register this bean in adfc-config i get a nullpointer on service.
When i register the same bean in the faces-config, it is working.

Frank,
Thanks! I think i managed to implement the workaround:
This is my bean that has been registered in the faces-config:
public class BeanHelper {
    @EJB
    private MyEJB myEjB;
    public BeanHelper() {
        super();
    public MyEJB getMyEJB()
          return myEJB;
}In my adfc managed bean i use
MyEJB myEJB = (MyEJB)JSFUtils.get("#{BeanHelper.myEJB}");This is working fine.
This way i no longer need to use a direct lookup and i don't need to know the exact path and so on for the EJB.
Thanks Frank!
Is there a way to let Oracle update the bug with this workaround so if other people find the bug, they know how to implement a workaround?

Problem Binding Parent Taskflow's Bean with Included Page's UI component

Hi,
I am using JDev 11.1.1.5.
I would like to ask *2* things:
Number 1
I have a Parent page (parentPage.jsff) which is inside the taskflow (parentTaskFlow). parentTaskFlow has a managed bean (ParentBean.java) with BackingBean Scope.
Inside the parentPage.jsff, a child page (childPage.jsff) is included using Dynamic Declarative Component. +*<af:declarativeComponent viewId="/childFragments/childPage.jsff" id="dc1"/>*+
When I tried to bind a ui component from childPage.jsff to ParentBean, it is returning null for this component.
Could you please help me with this issue? Thanks.
Number 2
The other important thing that I want to know is that when a page fragment (jsff) is included with Dynamic Declarative Component, Is the PageDef of that page fragment is the same as that of parent page or not? Please explain me about this also.
Thanks & Regards,
cmoster

Hi Frank,
Thanks for your explanation.
For Number 1
I will explain you the problem in detail:
As I mentioned in my previous post, I tried to bind a ui component from childPage.jsff to ParentBean.
In parentPage.jsff, there is a commandButton whose actionListener is bound to backing bean method. And inside this actionListener method, the binding for ui component is Null. That's the problem I'm facing. When I debug, the setter of the ui component is run. But in actionListener method, it returns null.
I made another test. In childPage.jsff, there is a commandButton whose actionListener is bound to backing bean method. But inside this actionListener method, the binding for ui component is NOT Null.
Can you help me with this issue? Thanks a lot.
Best Regards,
cmoster

Dynamic Declarative Component managed bean returned null

Hi,
In a project from an application a DDC component is defined. This component uses a managed/backing bean with view scope.
Using this component inside this project is working fine. This component should be used in other view controller projects, and here where the problems are.
This project(let's call it Common) is deployed as ADF Library jar, and used in the other V-C projects.
The big problem is that the managed bean defined for the logic of this component is not 'reacheable'.
(Another problem is that the attribute value is not seen as its EL expression but as string, for this i found a workaround.)
In project Common the adfc-config.xml file:
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
<managed-bean id="__4">
    <managed-bean-name id="__2">ExtendedShuttle</managed-bean-name>
    <managed-bean-class id="__1">com.xyz.portal.taskflow.common.extendedshuttle.ExtendedShuttle</managed-bean-class>
    <managed-bean-scope id="__3">view</managed-bean-scope>
</managed-bean>
</adfc-config>A part from component declaration:
      <af:table var="row" rowBandingInterval="0" id="ta"
                              rowSelection="multiple" columnStretching="last"
                              disableColumnReordering="true" fetchSize="-1"
                              binding="#{viewScope.ExtendedShuttle.allItemsTable}"
                              value="#{viewScope.ExtendedShuttle.allModel}"
                              partialTriggers="::dc_cb5 ::dc_cb3"
                              filterVisible="true"/>The root exception is :
javax.el.PropertyNotFoundException: Target Unreachable, 'ExtendedShuttle' returned null
This exception is throw on com.sun.faces.application.ApplicationImpl.createComponent when *#{viewScope.ExtendedShuttle.allItemsTable}* is evaluated.
Caused By: javax.faces.FacesException: javax.el.PropertyNotFoundException: Target Unreachable, 'ExtendedShuttle' returned null
     at com.sun.faces.application.ApplicationImpl.createComponent(ApplicationImpl.java:262)
     at javax.faces.webapp.UIComponentELTag.createComponent(UIComponentELTag.java:222)
     at javax.faces.webapp.UIComponentClassicTagBase.createFacet(UIComponentClassicTagBase.java:510)
     at javax.faces.webapp.UIComponentClassicTagBase.findComponent(UIComponentClassicTagBase.java:661)
     at javax.faces.webapp.UIComponentClassicTagBase.doStartTag(UIComponentClassicTagBase.java:1142)
     at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.doStartTag(UIXComponentELTag.java:70)
     at oracle.adfinternal.view.faces.taglib.UIXTableTag.doStartTag(UIXTableTag.java:41)
     at oracle.adfinternal.view.faces.unified.taglib.data.UnifiedTableTag.doStartTag(UnifiedTableTag.java:50)
     at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:50)
Caused By: javax.faces.FacesException: javax.el.PropertyNotFoundException: Target Unreachable, 'ExtendedShuttle' returned null
     at com.sun.faces.application.ApplicationImpl.createComponent(ApplicationImpl.java:262)
     at javax.faces.webapp.UIComponentELTag.createComponent(UIComponentELTag.java:222)
     at javax.faces.webapp.UIComponentClassicTagBase.createFacet(UIComponentClassicTagBase.java:510)
     at javax.faces.webapp.UIComponentClassicTagBase.findComponent(UIComponentClassicTagBase.java:661)
     at javax.faces.webapp.UIComponentClassicTagBase.doStartTag(UIComponentClassicTagBase.java:1142)
     at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.doStartTag(UIXComponentELTag.java:70)
     at oracle.adfinternal.view.faces.taglib.UIXTableTag.doStartTag(UIXTableTag.java:41)
     at oracle.adfinternal.view.faces.unified.taglib.data.UnifiedTableTag.doStartTag(UnifiedTableTag.java:50)
     at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:50)
Caused by: javax.el.PropertyNotFoundException: Target Unreachable, 'ExtendedShuttle' returned null
     at com.sun.el.parser.AstValue.getTarget(AstValue.java:88)
     at com.sun.el.parser.AstValue.setValue(AstValue.java:133)
     at com.sun.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:255)
     at com.sun.faces.application.ApplicationImpl.createComponent(ApplicationImpl.java:259)
Can you help figure it out, why is not working or why the managed bean is not visible in other projects but only in the one where the component is defined?
Thank you for your time,
Bogdan
ps: how can i format the source code, on this fourm?

Hi Frank,
Thank you for the answer.
I must say i'm quite new with ADF technology and maybe my questions are silly.
Here is a Quote from "Oracle Fusion Developer Guide - Building Rich Internet Application with Oracle ADF" by Frank Nimphius and Lynn Munsinger Chapter 15 page 498:
"You build dynamic declarative components *instead* of tag library based declarative components, if component resuse is required *only within the application* that has the component defined."
Maybe i misunderstand the meaning of application from this sentence, but i need this component in several ViewController projects from only one application (ADF application).
Tag lib declarative component I would not like to have, since the (automtically) build process is not my responsability and it will take some time till is pinpointed, but still is a last resort.
Anyway two things are strange:
1. Why the component is still available in other projects(and the beans not)?
2. Why when a binding variable (for example: of type FaceCtrlHierBinding) has the correct type in the declarative project and in the order projects is of type String and its value is the variable name?
Example:
<af:declarativeComponent ...
AllItems="#{bindings.Action}"
In project where the component is declared its value is an instance of FacesCtrlHierBinding and in the rest of the projects is of type String with value "Action".
Once again thank you a lot,
Bogdan

I want to get a adf component in managed bean with jsff. What can I do?

I want to get a adf component using FacesContext.getCurrentInstance().getViewRoot().findComponent("my component id").
It's ok in taskflow with jspx, but I can't get the component correctly in my managed bean in taskflow using page fragment.
The error is "can not find view root".

What features do you need in the discussion board and how big do you forecast the community to be?
I gather that you really want a free solution.
No software is perfect but when you pay for software you generally get features and the expectation of a certain minimum level of support.
With open source, you get free, features and some support but you also get constant security fixes, regular update patches, plus lots of trawling through online forums looking for tweaks and workarounds. Expect to invest lots of time maintaining it.
I've used phpBB in the past but never had issues with DW touching the coding. It served its purpose for me and the community at the time but the issues I dealt with regularly were the constant updates/bugfixes and never ending spam, spam, spam.

Enable/disable via managed bean

Hi
using jdev 11.1.1.3
Can anyone tell me how to disable/enable a input textfield from a managed bean which should happen on a button click.
The fields are already populated with data and is editable, and is part of a taskflow.
any help will be helpfull
thanks

Hi bigchill,
a possible solution could be:
1. create a bean containing following methods & attributes
public class MyBean
     // initial value
     private boolean disabled= true;
     public String doSomething()
          this.disabled= false;
          return null;
     public void setDisabled(boolean pDisabled)
          this.disabled= pDisabled;
     public boolean isDisabled()
          return disabled;
}2. Create an instance of the bean on a certain scope (depending on your requirements)
3. Link the disabled attribute of the input component with the disabled property of the bean and link the "doSomething" bean method with the action attribute of the commandButton:
<af:inputText label="Some textfield" disabled="#{s_myBean.disabled}"/>
<af:commandButton action="#{s_myBean.doSomething}"/>That's it.
Kind regards,
Koen Verhulst

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

How to pop up a browser window from a managed bean?

I have a user case like this:
User login our home website. He/she clicks a button. Control flow goes to a managed bean (MB here after) to check some conditions. If conditions are met, instead of sending the user back to the home page, the user will be presented a new web site (e.g. forums.oracle.com) in a popup window on top of our home site.
Can we invoke a website in a adf popup? If so, how to do that? If not, any idea on how to develop this use case?
Any idea is appreciated.

Sorry, I have updated the previous reply with the required inputs.
For convenience, putting it again;
if you need to check for some condition and then invoke the browser, you could use the following code in your managed bean for af:commandButton for Action.
import javax.faces.context.FacesContext;
import org.apache.myfaces.trinidad.render.ExtendedRenderKitService;
import org.apache.myfaces.trinidad.util.Service;
public class TestURLPageBean {
public TestURLPageBean() {
super();
public String onClick() {
*// Check for the condition here and invoke the browser only if it is true*
if (true) {
ExtendedRenderKitService erks =
(ExtendedRenderKitService)Service.getRenderKitService(FacesContext.getCurrentInstance(),
ExtendedRenderKitService.class);
StringBuilder script = new StringBuilder();
script.append("window.open('http://www.google.com');");
erks.addScript(FacesContext.getCurrentInstance(),
script.toString());
return null;
Thanks,
Navaneeth

What is difference between Managed Bean and Backing Bean?

What is difference between Managed Bean and Backing Bean? Please guide me how to create them and when to use them?
Please post sample for both beans.

Hi,
managed beans and backing beans are quite the same in that the Java object is managed by the JavaServer Faces framework. Manage in this respect means instantiation. The difference is that backing beans contain component "binding" references, which managed beans usually don't. Do backing beans are page specific versions of managed beans.
Managed beans are configured either in the faces-config.xml file, or using ADF Faces and ADFc, in the adfc-config.xml file
Frank
Edited by: Frank Nimphius on Jan 31, 2011 8:49 AM

Taskflow managed bean

Similar Messages

Maybe you are looking for