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

Similar Messages

Hot-(re)deploy classes on OC4J / JDeveloper

Using JDeveloper 11
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

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

Problem getting bindings in managed bean after deployment on remote weblogic

We have a Fusion Web application successfully running on Jdev 12c and its integrated wls server with Oracle 12c database configured as a DataSource. We created an ear file from JDev and deployed it on remote wls servers. The initial login .jspx page came up without any issues. Upon entering the login credentials in the browser and trying to enter the application, we are getting a Null Pointer exception. Looking at the logs, the null pointer is thrown when its trying to get the bindings in the managed bean.
       BindingContext bctx;
        bctx = BindingContext.getCurrent();
        DCBindingContainer bc =(DCBindingContainer)getBindings();
        DCBindingContainer bindings = (DCBindingContainer)bctx.getCurrentBindingsEntry();
        DCDataControl dataControl = bindings.findDataControl("LoginAMDataControl");
variable bindings is Null. What needs to be configured/changed while packaging the ear file for deployment on remote wls 12c? Please advise and appreciate your response.

try this...
      public String test() {
      DCIteratorBinding binding= getItrtBindings("findAdByNumberIterator");
      Row row = binding.getCurrentRow();
      String dn = (String)row.getAttribute("docNumber");
      System.out.println("docNumber " + dn);
      return dn;
       private BindingContainer bindings;
       public BindingContainer getBindings() {
          return this.bindings;
       public void setBindings(BindingContainer bindings) {
           this.bindings = bindings;
    protected DCIteratorBinding getItrtBindings(String binding){
        DCIteratorBinding outIterBinding = getBindingsForDCB().findIteratorBinding(binding);
        return outIterBinding;
    public DCBindingContainer getBindingsForDCB() {
        if (this.bindings == null) {
            FacesContext fc = FacesContext.getCurrentInstance();
            this.bindings =(DCBindingContainer)fc.getApplication().evaluateExpressionGet(fc,"#{bindings}",DCBindingContainer.class);
        return (DCBindingContainer)this.bindings;
    }

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 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

Problem in deploy a entitiy bean in WAS5.0 (URGENT)

ANYONE Pl Give u r suggestions
I am trying to deploy a entitiy bean in WebSphere Application Version 5. I have followed all the steps provided by the User Interface. I am connecting to Oracle 9i driver. I am trying to validate and install the ear. the validation and installation are happenning properly. but when I try to start the services, it is failing to start with the following exception:
com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is javax.naming.NamingException: Failed to lookup the object configured with a null or empty name
     at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:92)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
     at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
     at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:135)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1227)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
     at javax.naming.InitialContext.lookup(InitialContext.java:359)
     at com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanClassExtensionImpl.lookup(ConcreteBeanClassExtensionImpl.java:727)
     at com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanClassExtensionImpl.getConnectionFactory(ConcreteBeanClassExtensionImpl.java:260)
     at com.ibm.ws.ejbpersistence.beanextensions.PMModuleCookieImpl.beanInstall(PMModuleCookieImpl.java:98)
     at com.ibm.ws.ejbpersistence.beanextensions.PersistenceManagerImpl.beanInstall(PersistenceManagerImpl.java:69)
     at com.ibm.ejs.container.EJSContainer.loadBeanMetaData(EJSContainer.java:1293)
     at com.ibm.ejs.container.EJSContainer.getHomeWrapperCommon(EJSContainer.java:958)
     at com.ibm.ejs.container.EJSContainer.getHomeInstance(EJSContainer.java:881)
     at com.ibm.ejs.container.EJSContainer.startBean(EJSContainer.java:860)
     at com.ibm.ws.runtime.component.EJBContainerImpl.startBean(EJBContainerImpl.java:1249)
     at com.ibm.ws.runtime.component.EJBContainerImpl.install(EJBContainerImpl.java:982)
     at com.ibm.ws.runtime.component.EJBContainerImpl.start(EJBContainerImpl.java:1456)
     at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:401)
     at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:743)
     at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:337)
     at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:531)
     at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:254)
     at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:458)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.tivoli.jmx.modelmbean.MMBInvoker.invoke(MMBInvoker.java:46)
     at com.tivoli.jmx.modelmbean.MMBInvoker.invokeOperation(MMBInvoker.java:115)
     at com.tivoli.jmx.modelmbean.DynamicModelMBeanSupport.invoke(DynamicModelMBeanSupport.java:409)
     at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:323)
     at com.tivoli.jmx.GenericMBeanSupport.invoke(GenericMBeanSupport.java:178)
     at com.tivoli.jmx.MBeanAccess.invoke(MBeanAccess.java:113)
     at com.tivoli.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:290)
     at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:655)
     at com.ibm.ws.console.core.mbean.MBeanHelper.invoke(MBeanHelper.java:137)
     at com.ibm.ws.console.appdeployment.ApplicationDeploymentCollectionAction.perform(ApplicationDeploymentCollectionAction.java:239)
     at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:258)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:872)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:491)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:173)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:199)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:331)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:432)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:343)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)

hello there
when u are deploying ur component there will be a screen that will show components present in ur jar/ear and will ask for JNDI name.U will have to fill the JNDI name manually and deploy the bean..
If even after that u are facing the same problem, use AAT(Application Assembly Tool) to create ur jar / ear ... there is a seperate link for giving JNDI names (namely JNDI Bindings) .use this tab to specify ur JNDI name and create the jar/ear.deploy as such in WAS and i am sure the error will not occur
Ganesh V

Share stateful session bean in JSF managed beans with different scope

Hi,
I have a JSF application and I want to try to use of stateful session beans.
So I created a new stateful session bean and its local interface.
@Stateful
public class StatefulSessionBean implements StatefulSessionBeanLocalInterface{
private String name;
@Local
public interface StatefulSessionBeanLocalInterface {
...In my JSF application I have a mananed bean with session context which registers the new interface by
this annotation
@EJB(name="sessionbeanref", beanInterface=StatefulSessionBeanLocalInterface.class) and set the name to something.
Now I want to fetch this name in another managed bean with request scope. So I looked up the bean and tried to get the name.
StatefulSessionBeanLocalInterface = (StatefulSessionBeanLocalInterface) new InitialContext().lookup("java:comp/env/sessionbeanref");
System.out.println(currentmailingbean.getName());but the name is null.
Why?

The xsd was created via the netbeans J2EE enterprise application dialog and I think its the most recent.
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">All other annotations seem to work.
Wouldnt the lookup completely fail if the deployment process thought that it is version 1.4 ?

Managed Bean in Task Form

Hi!Oracle Fusion Middleware 11.1.1.5.0, Oracle JDeveloper 11g.
I post this thread in this section because of the type of project I am working in (SOA Application).
I am trying to customize a BPEL Task Form.
After I made a project using Fusion Web Application, I could confirm that the managed beans for some ADF Faces components were working and the form (an .jspx page that I would run on Integrated Web Logic Server) was functional.
I made a project using SOA Application.
I made a BPEL Process with a Human Tak and using the Launch Task Form Wizard I made a form.
Then I started adding ADF Faces components that are using managed beans, just like in the other project.
When I deploy the project, all the components using the beans just dont show up. If I dont use the components with the managed beans the form appears normally.
Is there some additional requirement to make the bindings with the managed beans in the Task Form?
To clarify the question below I have some printscreens:
1. SelectOneChoice "Rubrica" component with value binding from the ActionListenerOK java class;
http://i43.tinypic.com/x4j0ol.jpg
2. Showing the Expression Builder for the above value binding;
http://i42.tinypic.com/14mdxqq.jpg
3. Method Expression Builder for a Button Component;
http://i41.tinypic.com/2r38tw2.jpg
4. The managed beans list for the form page;
http://i41.tinypic.com/rbjqt2.jpg
5. How the form appears when using the components with java bean bindings;
http://i39.tinypic.com/34pghh0.jpg
6. How the form appears when delete the components with tha java bindings;
http://i41.tinypic.com/2mwwkuo.jpg

<af:outputText value="Authenticated User: #{securityContext.userName}" id="ot2"/>
or via standard j2se apis (Subject.getSubject(..))
hth clemens (http://blogs.oracle.com/soabpm)

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

Manage bean methods not able to call application module methods

Hi,
I have an ADF application where in my managed bean method needs to call AppModuleImpl methods. I use the code as below:
public void getSummary() {
DCBindingContainer binding = (DCBindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry();
OperationBinding op = binding.getOperationBinding("getVOData");
op.execute();
The code works fine when I run the application in my IntegratedWeblogicServer and I am able to get the data on my .jsp pages.
I have installed weblogic server on another machine and I need to deploy and run my application on that server. But when I try doing that, the above code is not able to call the AppModule method and I see no data on my page (Also there is no error or exceptin thrown). Seems that the ViewController project is not able to interact with the Model project.
Is there any extra configuration to be done on the newly installed weblogic server to get this work? Or will some change in the application code help?
Please suggest.
Thanks and regards,
Ansh

Hi,
While creating the weblogic domain, we had the following checkboxes checked:
1. Basic weblogic server domain [wlserver_10.3]
2. Oracle JRF [oracle_common]
I hope this is what we need.
Yes, I also have the adf runtime installed.

EJB Injection in Seperated Managed Bean

Hi All,
I have a JSF project consisting of a number of different WARs, containing the Web logic, and a bunch of different JARs, containing the application logic; which are deployed together in a single EAR file. Thus far this approach has worked excellently, but I've now run into a problem. I would like to have a managed session-scoped bean which should be available to all the WARs' classes so that they can store cross-application data in it (for example the user's name and other details). I can do this by packaging that session-scoped bean, along with its faces-config.xml, into a JAR which is deployed through the EAR. This works fine, but EJB Injection in that session-scoped bean doesn't work - my bean interface instance always contains null.
Is there someway that I can have EJB Injection in this managed session-scoped bean contained in a JAR? I realize that EJB Injection requires a container, but seeing as it is a managed bean, even though it isn't inside a WAR, I thought this should work fine?
Thank you,
Ristretto

We tried almost every permutation and combination, but it did not work without that dummy servlet.
Then we had to look for a cleaner solution and we found one.
We are now using spring injection, to get the EJB injection in our session managed bean. This way the code is extensible and cleaner.
In future if you want something else(other than ejb lets say a web service), you will just change the Spring config file and it would't break anything.
Edited by: desu on Mar 14, 2008 4:20 AM

@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?

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.

Why can't Weblogic 12c find Managed Bean by annotation,which in a jar?

the detail:
why can't Weblogic 12c find Managed Bean by annotation,which in a jar?

Hi,
I got the same problem with weblogic 12c.
Somehow this guy got it working by using CDI and creating an empty beans.xml, it did not work for me.
i found the tricky problem is that should put a empty but include the <beans> tag beans.xml file.
http://www.coderanch.com/t/562233/JSF/java/WebLogic-Eclipse-Indigo-develop-JSF
I also tried to skip managedbean and use CDI ( @named ) but then I get some jboss weld exceptions on the value attribute of some jsf components.
I also saw this post
Can't seem to get a trivial CDI example to work on Weblogic 12c
I don't use OEPE very often so I'll need to kick this around a little when I get a chance.
Just as an out there kind of thought, OEPE does use the split-directory model for deployment by default -- perhaps try adjusting it to use the exploded archive model instead, just as a test to see if it removes the error?
Right click the server config and select Properties > WebLogic > Publishing > Publish as exploded archive
It seems like the Virtual Application deployment model of OEPE doesn't support CDI.
thanks
Edited by: Edwin Biemond on Dec 28, 2011 10:07 PM
Edited by: Edwin Biemond on Dec 28, 2011 10:25 PM

Duplicate managed bean definition

Hello,
This is my first time to post on this forum and I am very excited :). Thank you all in advance for your time to read my post.
We are developing an EJB/ADF faces application using JDeveloper 11.1.1.4.0. When I deploy the application, I get the following message:
<MetadataService$Bootstrap> <add> ADFc: Duplicate managed bean definition for 'nameOfMyBean' detected.
<MetadataService$Bootstrap> <add> ADFc: /WEB-INF/adfc-config.xml:
Can anyone help me how I can resolve this?
Thanks
Hemen

For people who has the same error message:
This could be a configuration error.
Take a look into the WAR file of the EAR which will be deployed. In my case was the WEB-INF folder copied into the CLASSES folder so that he adfc-config.xml was two times in the WAR-File.
WAR-File
¦   home.jspx
¦   ...
¦
+---WEB-INF
    ¦   adfc-config.xml
    ¦   faces-config.xml
    ¦   ...
    ¦
    +---classes
        +---META-INF
        ¦       adfm.xml
        ¦
        +---WEB-INF
                adfc-config.xml
                faces-config.xml
                ...In my case I had edit WAR-Deployment configuration of the ViewContorller projekt properties. There is a tree with a node "WEB-INF/classes", which has a child node "Filters". On the right you see the files which will be deployed. I've unchecked the WEB-INF subfolder and redeployed it.
Now the errors are gone.

Hot-(re)deploy of managed beans

Similar Messages

Maybe you are looking for