JBO-29114 ADFContext is not setup to process messages for this exception

Problem -
oracle.jbo.JboException: JBO-29114 ADFContext is not setup to process messages for this exception

Error Message -

oracle.jbo.JboException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-34010. Error message parameters are {0=com/mshs/pmgt/view/DataBindings.cpx, 1=jar:file:C:/Users/pdhayal/AppData/Roaming/JDeveloper/system12.2.1.3.42.170820.0914/DefaultDomain/servers/DefaultServer/tmp/_WL_user/MSHSPositionManagement/b25f7o/war/WEB-INF/lib/_wl_cls_gen.jar!/com/mshs/pmgt/view/DataBindings.cpx, 2=file:/C:/Users/pdhayal/AppData/Roaming/JDeveloper/system12.2.1.3.42.170820.0914/o.j2ee/drs/MSHSPositionManagement/MSHSPositionManagementUIWebApp.war/WEB-INF/classes/com/mshs/pmgt/view/DataBindings.cpx}
at oracle.jbo.uicli.mom.CpxUtils$Visitor.visit(CpxUtils.java:236)
at oracle.adf.share.common.rc.util.impl.MetadataRegistryImpl.visitRegistryPaths(MetadataRegistryImpl.java:169)
at oracle.adf.share.common.rc.util.impl.MetadataRegistryImpl.visitRegistryPaths(MetadataRegistryImpl.java:116)
at oracle.jbo.uicli.mom.CpxUtils.getCpxListFromMetadata(CpxUtils.java:491)
at oracle.jbo.uicli.mom.JUMetaObjectManager.loadCpx(JUMetaObjectManager.java:915)
at oracle.adf.model.BindingContext.initialize(BindingContext.java:472)
at oracle.adf.model.BindingRequestHandler.beginRequest(BindingRequestHandler.java:270)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:196)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:105)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:529)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:529)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:354)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:232)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.security.jps.ee.http.JpsAbsFilter$3.run(JpsAbsFilter.java:172)
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:650)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:110)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilterInternal(JpsAbsFilter.java:273)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:147)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:94)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:248)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:32)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3701)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3667)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2443)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2291)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2269)
at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1703)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1663)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:272)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)

------------------------------------------------------------------------------------------------------------

Reason -
DataBindingg.cpx is created as library in weblogic server

Solution -
C:\Users\pdhayal\AppData\Roaming\JDeveloper\system12.2.1.3.42.170820.0914\DefaultDomain\servers\DefaultServer\tmp\_WL_user
and delete folder created with Application Name

Invalid column type: getBigDecimal not implemented for class oracle.jdbc.driver.T4CDateAccessor in adf

Error -
Invalid column type: getBigDecimal not implemented for class oracle.jdbc.driver.T4CDateAccessor in adf

Possible similar errors-
Invalid column type: getString not implemented for class oracle.jdbc.driver.T4CBlobAccessor
Invalid column type: getInt not implemented for class oracle.jdbc.driver.T4CRowidAccessor

Reason -
 This type of error will come when you will update your existing query by adding some extra columns

Solution -
The error because newly added columns came in the attribute list and in your java impl files,but they went off from your query.
So go the source of your VO.xml and added those newly added columns their again and run again you won't get that error again.

Reset Code for Reset View Object

This code you have to write in the bean created


public Object resolvElDC(String data) {
        FacesContext fc = FacesContext.getCurrentInstance();
        Application app = fc.getApplication();
        ExpressionFactory elFactory = app.getExpressionFactory();
        ELContext elContext = fc.getELContext();
        ValueExpression valueExp =
            elFactory.createValueExpression(elContext, "#{data." + data + ".dataProvider}", Object.class);
        return valueExp.getValue(elContext);
    }

    public void resetButton(ActionEvent actionEvent) {
        searchAMImpl am = (searchAMImpl)resolvElDC("ApplicationDataControl");
        ViewObject empVo = am.getEmployees1();
        ViewObject attrVo=am.getattr1();
        empVo.setNamedWhereClauseParam("EmpIdBind", null);
        empVo.setNamedWhereClauseParam("FirstNmBind", null);
        empVo.setNamedWhereClauseParam("EmailBind", null);
        empVo.setNamedWhereClauseParam("SalaryBind", null);
        empVo.executeQuery();
        attrVo.executeQuery();
   
    }

Deployment cancelled - oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer

Problem

Deployment cancelled.
[12:12:27 PM] ---- Deployment incomplete ----.
[12:12:27 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer) #### Cannot run application Application1 due to error deploying to IntegratedWebLogicServer.
[12:12:27 PM] Cancel requested

------------------------------------------------------------------------------------------------------------------------


Cause 1

The application is not undeployed properly in the last processes of terminating the application from Integrated Web Logic Server.

Solution 1

Terminate the Integrated Web Logic Server and try to start the again.
It will resolve the issue.

------------------------------------------------------------------------------------------------------------------------

Cause 2

Integrated Web Logic Server deployment property is not setted properly.

Solution 2

Step 1
        Open Application properties in JDeveloper for application by clicking on Application Icon available in          Menu  Bar(4th from Left) and select Application Properties from the popup(third last).
Step 2
        Goto to the weblogic option available inside Deployment and uncheck the below highlighted check box.

Step 3
        Click Ok and save your application again and run.