ADF Mobile Browser - 12c invokeAction supported?

We are planning to upgrade our existing platform to Oracle 12C (from 11.1.2.3) , and are in the processing of migrating our applications in the Development environment.
One of the critical applications is an ADF Mobile Browser application. We use the invokeAction  executable heavily in our pages to execute actions on page load.
Now although the application run fine in the 12C environment, we get a warning that invokeAction is deprecated.
Question: whats the alternative to invokeAction in ADF Mobile Browser applications where we do not have taskflows?
Thank you...

Thanks Frank. When we first tried building our existing ADF application as a mobile browser app, the task flows did not work and we incorrectly assumed that task flows were not supported in ADF Mobile browser.
I read the documentation again, and it seems only certain aspects of task flows like regions and page fragments that are not supported.
We will re-write the logic to use task flows instead and try it out.

Similar Messages

  • Webcenter Portal Support for ADF Mobile Browser

    Hi All,
    I am currently working on an ADF Mobile Browser Application for WebCenter Portal.
    The main issue I face is that WebCenter has some really powerful taskflows and connectors. Is it possible for us to make use of these taskflows in ADF mobile browser? It seems that when used within the trinidad framework, the taskflows are broken.
    I understand from documentation that "Except for page fragments, pop-up in dialogs, and region support, you can use the ADF task flow to develop ADF Mobile browser applications. ADF Mobile browser application that use the ADF task flow only support the trinidad-simple skin family"
    Does this mean that taskflows that use the page fragments, pop up dialogs dont work or that you cant use them within jsff and pop ups?
    Sincerely appreciate any help! thanks

    Hi,
    You can reuse taskflows but you need to modify jsff pages with trinidad components.
    Thanks,
    Minal

  • Deploying ADF Mobile Browser Sample App in JDeveloper 11.1.2.3

    Hi,
    I had problem in deploying the sample app for ADF Mobile Browser in JDeveloper 11.1.2.3.
    I had tried every solution such as replacing web.xml for the Sample App with web.xml created in JDeveloper 11.1.2.3.
    I could not find the Jar file for the oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler in the web also.
    Please help to solve this problem as I had tried for many days.
    Thank you very much! =)
    ADF Mobile Browser Sample App URL:
    [ADF Mobile Browser Sample App|http://www.oracle.com/technetwork/developer-tools/adf/adf-mobile-browser-1864237.html]
    Error Log:_
    *<ConfigureListener> <contextInitialized> Critical error during deployment:*
    com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
         at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         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:1872)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         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:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         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:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         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:163)
         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:68)
         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)
    Caused by: java.lang.ClassNotFoundException: oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
         at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43)
         at com.sun.faces.util.Util.loadClass(Util.java:303)
         at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
         at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processHandlerClass(FaceletTaglibConfigProcessor.java:420)
         at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTags(FaceletTaglibConfigProcessor.java:371)
         at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTagLibrary(FaceletTaglibConfigProcessor.java:314)
         at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:263)
         at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:340)
         ... 38 more
    <Dec 10, 2012 12:20:15 PM IST> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler.
    java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:293)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
         Truncated. see log file for complete stacktrace
    Caused By: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357)
         at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:226)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
         Truncated. see log file for complete stacktrace
    >
    <FactoryFinder$FactoryManager> <getFactory> Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup.
    <ConfigureListener> <contextDestroyed> Unexpected exception when attempting to tear down the Mojarra runtime
    java.lang.IllegalStateException: Could not find backup for factory javax.faces.application.ApplicationFactory.
         at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:996)
         at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:331)
         at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:131)
         at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:329)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:482)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.EventsManager.notifyContextDestroyedEvent(EventsManager.java:200)
         at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:3224)
         at weblogic.servlet.internal.ServletContextManager.destroyContext(ServletContextManager.java:247)
         at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:461)
         at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:1535)
         at weblogic.servlet.internal.WebAppModule.deactivate(WebAppModule.java:507)
         at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
         at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
         at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
         at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
         at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:642)
         at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
         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:163)
         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:68)
         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)
    <Dec 10, 2012 12:20:15 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1355122207762' for task '3'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.adfinternal.view.faces.bi.facelets.graph.RichSeriesSetHandler
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
         Truncated. see log file for complete stacktrace
    >
    Edited by: 975879 on Dec 9, 2012 10:56 PM

    Hi Frank,
    Thanks for the fast response.
    Based on your advice, I had try to comment out all usage of graph in jsp, web.xml, and data binding file.
    But even after perform these, I still facing the same problem.
    For your information, RichSeriesSetHandler does not exist in the oracle.adfinternal.view.faces.bi.facelets.
    I suspecting RichSeriesSetHandler is configured in the app and it occur this error as it could not find the class.
    I had try to search this usage of this class in the app but there is no results found.

  • Error when starting ADF Mobile Browser Sample Application

    I had successfully deployed the Sample App downloaded from the Oracle ADF Mobile Browser Website in JDeveloper 11.1.2.2.
    This sample app is deployed successfully in IntegratedWebLogicServer as EAR.
    But when I trying to access the app in browser, it omit the following error:
    Error 500--Internal Server Error
    java.lang.NullPointerException
         at oracle.adfinternal.controller.util.AdfvInterfaceImpl.updateQueryParameters(AdfvInterfaceImpl.java:211)
         at oracle.adfinternal.controller.state.RequestState.updateUrlStateToken(RequestState.java:677)
         at oracle.adfinternal.controller.state.RequestState.setCurrentStateInstance(RequestState.java:188)
         at oracle.adfinternal.controller.state.RequestState.setCurrentViewPortContext(RequestState.java:215)
         at oracle.adfinternal.controller.state.ControllerState.setRequestState(ControllerState.java:877)
         at oracle.adfinternal.controller.state.ControllerState.initializeRootViewPort(ControllerState.java:646)
         at oracle.adfinternal.controller.state.ControllerState.synchronizeStatePart1(ControllerState.java:302)
         at oracle.adfinternal.controller.application.SyncNavigationStateListener.beforePhase(SyncNavigationStateListener.java:219)
         at oracle.adfinternal.controller.lifecycle.ADFLifecycleImpl$PagePhaseListenerWrapper.beforePhase(ADFLifecycleImpl.java:550)
         at oracle.adfinternal.controller.lifecycle.LifecycleImpl.internalDispatchBeforeEvent(LifecycleImpl.java:100)
         at oracle.adfinternal.controller.lifecycle.LifecycleImpl.dispatchBeforePagePhaseEvent(LifecycleImpl.java:147)
         at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$PhaseInvokerImpl.dispatchBeforePagePhaseEvent(ADFPhaseListener.java:119)
         at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.beforePhase(ADFPhaseListener.java:63)
         at oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener.beforePhase(ADFLifecyclePhaseListener.java:44)
         at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228)
         at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99)
         at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:111)
         at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:508)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:173)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:293)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:199)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

    Hi Sashank, Thank for your reply and advice.
    This is a mobile ADF browser which it is deployed in EAR in Weblogic.
    ADF Mobile browser is different with ADF Mobile as one is access through mobile browser and one is access as mobile app.
    Please correct me if I'm wrong in this.
    Thanks

  • How to test my ADF mobile browser application on Android emulator?

    Hi
    I have created a Mobile Browser Application. Could anyone please tell me how to test it on Android emulator?
    I read the information about downloading and configuring simulators(Blackberry) and emulators(Microsoft Windows) for ADF Mobile browser in "Running Mobile Device Simulators with ADF Mobile and JDeveloper". However they didn't mention details about downloading and configuring "*Android Emulators*". Could anyone please help me in this.
    Regards
    Raja

    Hi,
    thought you want to test a mobile BROWSER application on android emulator you have to use android JDK like mentioned by codigoadf.
    I guess also that the configuration (create virtual android device, ...) will be the same.
    You have to use the same URL for your application than on your PC but replace 127.0.0.1 by 10.0.2.2 (In case your WLS runs on the same machine as the android emulator)
    regards
    Peter

  • ADF MOBILE Browser application throwing Error HTTP 502 Bad Gateway

    Downloaded "mobile banking Sample" from ADF Mobile Homepage, imported into JDeveloper 11gR2. Started MDS-CS, started built-in Weblogic application server. The deployed application Welcome.jspx displays correctly in a stand alone browser. However, surprisingly the same URL when typed within Blackberry Simulator browser HTTP Error 502: Bad gateway is thrown. I know its not a proxy issue since I can navigate to google and MDSCS admin page. Please advise where we are going wrong?
    Note. since this is urgent I wanted to put across as much information as possible - so created a document with screen shots and added it as attechment to Oracle Support issue#3-4905845711.

    web browser returns 502 Bad Gateway errorHuh? I would expect a "page is taking too long to respond" error.
    Seems to me like you need support for background jobs. It would work something like this:
    - do request to server, either direct submit or Ajax call
    - that request, after validating of course, will start a background job. In a thread, through a job scheduler, whatever, as long as it is not the servlet that is actually executing the job. The servlet immediately returns after starting the background job.
    - webapp can show running jobs and through Ajax infrequently polls to see if running jobs are either done or they blew up with an error
    - you can see the results after a job has finished running
    This kind of "detached" system has many problems that need to be taken care of, for example taking care of resubmission. If you maintain persistent bookkeeping about jobs, a server shutdown can make the bookkeeping and the running state go out of sync. But programming is hard, this is the fun side of the job. Doing stuff you actually have to think about!

  • How to Access Web service with ADF Mobile Browser Application

    hi all,
    My Jdeveloper version is 11g 2 release(Version 11.1.2.2.0). I need to know If I create a web application and put it on a server as a web service., Then I create a Mobile browser application and need to access that web service.
    If it is possible, how should I do? version are same in both application.
    hopping any clue..
    Thxs.

    You can go thru the below links :
    ADF Mobile HowTos: Consuming SOAP web service in ADF Mobile using WS DC
    Oracle JDeveloper 11g Release 2 Tutorials - Building Mobile Applications with Oracle ADF Mobile

  • AdMob support in Oracle ADF mobile

    hi,
    i had posted this earlier but didn't get response at that time. so posting again.
    is there a way to integrate AdMob into Oracle ADF mobile application (on android)?
    regards,
    ad

    Hi,
    want to leave a final answer to someone from the mobile team but as it appears AdMob is native device code, which means it cannot be incorporated to ADF Mobile as it only supports JS, HTML 5, AMX and Java
    Frank

  • Mobile Browser and LOV

    Hello,
    I have a mobile browser application to develop and I need something like a LOV mechanism. I saw that the inputListOfValues tag is not supported. I can't use the selectOneChoice for all the fields since they may be very big (in terms of data returned) so is there any way to easily do this ?

    Thanks,
    By now my application does not include ADF tags but only Trinidad ones since I did like in tutorial [url http://www.oracle.com/technetwork/developer-tools/jdev/ccset51-all-102005.html]Tutorial: Building ADF Mobile Browser Application in ADF 11g
    I can add them and keep the application working in Mobile Browser ? (the mobile page gives only trinidad tr tags supported, not af ones)
    I used the Dialogs but only in a popup manner yet. To use it as you told me, I have to create a new page containing it or can I (must I) put it in the same page, in a tr:showDetail element for instance ?

  • ADF Mobile dead?

    Hallo,
    I have a client that wants me to make an ADF application for the Samsung Galaxy Note. I am trying to find information about ADF Mobile but all I can find is old information. The mobile blog hasn't been updated for almost a year, the "live demo site" is completely dead and I find conflicting information: I am now not sure whether to use Trinidad components because ADF Faces apparently isn't suited for mobile browsers, but the demo for the iPad does use ADF Faces because it supports touchscreens.
    I am using JDeveloper 11.1.1.6. Can anyone help me get more information or demos? Has anyone here built an application for a mobile browser, and if so, how?
    thanks for the information
    Wendy Tromp

    Thanks Shay, but I already saw that page and it doesn't have that much information. As I said, the link to the live demo site is dead and the blog hasn't been updated for almost a year. It seems to me that Oracle isn't really paying attention to the mobile market anymore.
    Right now the focus is on developing a webapp for a smaller screen basically, features like using GPS and the camera are a nice to have, we'll see about that later.
    I have fiddled with the trinidad components and with a firefox user agent switcher, but i see no difference, so what is the added value of ADF Mobile Browser? And if Jdeveloper 11gR1 and R2 are supposed to be the same release with the only difference of the JSF version why is the tutorial found on that site in R2 with completely different menu options and design view options from my 11.1.1.6 installation? All I can pick in design view is tiny resolutions, no larger than 320x320. Nobody uses that anymore.
    I a nutshell, Oracle Mobile seems to be forgotten by Oracle, I am really disappointed :(

  • Using database views in ADF mobile client application

    Hi,
    I am using Jdeveloper 11.1.1.4 and WLS 10.3.4.
    I have developed a POC in ADF mobile client application both with and without synchronization. However, both work with entity objects based on tables.
    I need to use database views instead of tables. When I try to include entity object (based on views) in the view object, it shows an error saying "Only the entity objects based on tables can be selected"
    Please guide me if there is a work around for this.
    Also, please let me know if there is way to develop an ADF mobile client application skipping the use of entity objects at all and using view objects directly to specify the database query and fetch data from the database.
    Thanks in advance.
    Ansh
    Edited by: ansh on Mar 28, 2011 5:40 AM

    Hi, Ansh:
    Currently, out of box, ADF Mobile Client does not support synchronization against Database Views. This is because Mobile Server imposes some schema restrictions to ensure synchronization with multi-table views would work correctly. This schema restriction requires, for example, the view must have a primary parent table with key defined, and also all base table must be included in the data publication. These dependencies requires manual resolution and advanced planning, and is managed outside of the ADF Mobile Client/JDeveloper project.
    To continue development, you would need to create server Entity Objects directly against the base tables. You can then create the mobile ADF Business Component (EOs, VOs, etc). You can then create View Objects in your ADF Mobile Client application based on the database views, in order to retrieve the data you need exactly. In other words, instead of basing EO on the database view, create View Objects in the mobile applicaiton to mimic what you had in the View Object.
    Is there any other reason why you would need to access data via database views, instead of directly against base tables?
    Thanks,
    Joe Huang

  • ADF Mobile : sample no Vegas

    hi
    Please consider this tweet by Duncan Mills
    " @fnimphiu so it's like Vegas - "what happens in a region - stays in a region" "
    at https://twitter.com/DuncanMills/status/255318833412308992
    I wonder how much this translates to bounded task-flows and using managed-beans in a bounded task-flow that are defined in a wider scope outside the bounded task-flow.
    In the ADF Mobile CompGallery sample application [1] the bounded task-flow "general-taskflow" has a view configured for the page "commandButton.amx".
    That "commandButton.amx" page has this button component:
    <amx:commandButton id="back" action="__back" text="General">
         <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.text}" from="#{pageFlowScope.pText}" type="action"/>
         <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.rendered}" from="#{pageFlowScope.pRendered}" type="action"/>
         <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.icon}" from="#{pageFlowScope.pIcon}" type="action"/>
         <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.iconPosition}" from="#{pageFlowScope.pIconPosition}" type="action"/>
         <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.styleClass}" from="#{pageFlowScope.pStyleClass}" type="action"/>
         <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.inlineStyle}" from="#{pageFlowScope.pInlineStyle}" type="action"/>
         <amx:setPropertyListener to="#{AmxProperties.commandButtonProperties.disabled}" from="#{pageFlowScope.pDisabled}" type="action"/>
    </amx:commandButton>The #{AmxProperties} managed-bean has been defined in adfc-mobile-config.xml like:
        <managed-bean id="__37">
            <managed-bean-name>AmxProperties</managed-bean-name>
            <managed-bean-class>mobile.AmxProperties</managed-bean-class>
            <managed-bean-scope>application</managed-bean-scope>
        </managed-bean>- (q1) Is using (depending on) an application-scoped managed-bean in a bounded task-flow view/page good practice (in ADF Mobile)?
    - [1] http://docs.oracle.com/cd/E35521_01/doc.111230/e24475/demoapps.htm#BACGDHDJ
    many thanks
    Jan Vervecken

    Hi,
    First let's forget region for a sec (or a while), since ADF Mobil has no region support. :-)
    Now, ADF Mobile primarily supports 3 types of scopes for managed bean: application, pageFlow, and view. The definition and scope for these scope variables are basically the same as the "big" ADF cousin, except "application" takes on a little more significance. In ADF Mobile applications, we introduced a concept called "features", where each feature can be implemented either in AMX, local HTML, or Remote HTML. To pass state between features, you would need to use application scope variables. This is how, for example, you can pass data from a Remote HTML feature into an app scope variable, and then have the AMX feature to consume it.
    Otherwise, the best practice is the same - application is to share data across the entire mobile app/between features, pageFlow is for a task flow, and view is for a view.
    In this case below, the intent for the property related managed beans is simply to retain property values as user select between different components (and corresponding task flows) to view how component behaves. The managed beans for DVT component data are set to be application scope, also to allow multiple DVT components and corresponding task flows to share the same data.
    Thanks,
    Joe Huang

  • ADF Mobile: Data synchronization

    Hi,
    I'm currently investigating some ADF Mobile related things for a client.
    One of these this is the synchronization of data. Since ADF Mobile (currently) doesn't support something ootb I'm checking my options here.
    What would you guys suggest (maybe an other suggestion)?
    Performance and reliability are important of course.
    Thanks in advance!

    Shay Shmeltzer wrote:
    For offline access you'll want to use the local SQLite DB.
    For synchronization you need decide if you just need a DB to DB synch and then you might be able to use Oracle Database Mobile Server 11g:
    http://www.oracle.com/technetwork/products/database-mobile-server/overview/index.html
    Thanks for your reply, I will take a look at the Oracle Database Mobile Server.
    Edit:
    After reading trough the documentation of Oracle Database Mobile Server (and googling) I found out that there is no support for iOS devices.
    Since we are using ADF Mobile for Android and iOS, we are looking for something that works on both devices.
    Any suggestion?

  • ADF Mobile on Android? Offline synchronization with the database?

    Hello,
    We are thinking about developing a project on Oracle ADF Mobile, and want it to run on both Android and IOS devices.
    And we want to be able to synchronize our database for offline mode.
    I read some docs, and they say Oracle does not have an Android version of ADF Mobile Client. It provides ADF Mobile Browser,
    but then it will not be possible to be synchronized with a remote database and run in offline mode.
    Is it possible to develop an application with Oracle ADF Mobile technology, that runs on Android and IOS phones,
    syncs with a remote database and run both online and offline mode, and uses device's services like GPS, camera, etc?
    Thanks,
    Bora Yuret
    Edited by: 919404 on 07.Mar.2012 09:01
    Edited by: 919404 on 07.Mar.2012 09:02

    Trinidad faces and JSF faces not optimized for android web-browser.

  • Regular Expression and jUnit in ADF Mobile

    Hi Guys,
    I tried to implement Regular Expression in ADF Mobile, but in my jUnit that I was configured to unit test purpose in my application.
    Shown error below inside jUnit plane.
    java.lang.NoClassDefFoundError: oracle/adfmf/util/regex/Pattern
    How to solve this issue for jUnit ?

    I'll start by answering your Q2 - while in theory you can use the same application for both accessing from a browser on a pc and on a phone - in reality the user experience on the phone is not going to be good because of the limitation of the screen size. Users will need to constantly zoom-in scroll around etc. This is why many people who target application for smart phones prefer to build a separate UI for the mobile device.
    Now question 4 which relates to 1 - We haven't tested the ADF Faces components on the browser of blackberry and so there is a chance that some of their functionality won't work there. We did test and certify the ADF Faces components with the safari mobile browser (iOS) - so this is why you see them work there better.
    This is why we recommend that if you are targeting a blackberry (and other mobile devices) you'll use the Trinidad set of components and in general ADF Mobile Browser project type.
    (see example here: https://blogs.oracle.com/shay/entry/building_iphone_interfaces_for_oracle ). This also means that you'll have the check box checked for mobile device when you create a JSF page.
    For question 3 - when the next ADF Mobile solution will be released you'll be able to create applications that install on the device itself.

Maybe you are looking for

  • Acrobat Pro Extended feature questions

    Hi, I am testing Adobe Acrobat Pro Extended to evaluate usability within the company I work for. During my testing, I have run across some questions about Pro Extended functionality. I would appreciate any information or suggestions you may have rega

  • How to send a fax

    my dell pc is in the wireless mode but my fax is connected to house phone. How to I connect to 2 so I can send and receive fax

  • Monitor Display Problems

    Just today my display developed a problem: about an inch up from the bottom it developed a very thin, black "line" going all the way across the screen. Further on the left side of the display is now a "gray" area about an inch wide from the edge, goi

  • Trouble mirroring chromebook to tv

    When I connect the chromebook cb35 to my tv and start mirroring, the tv doesn't respond.  (input is correct.)  Only the chromebook screen flashes on and off.

  • Existing Kompozer Website but Wish to Start Over W/CS4 Web Premium

    Hopefully, i am in the right place to ask these question. I'm a real novice but we needed a web presence and tried a hand at Kompozer. With no prior experience, or training actually managed to get something up. The site has only a single page at the