3 ADFC-00001 to ADFC-14018
- ADFC-00005: The ADF Controller cannot execute task flow template ''{0}''.
-
Cause: An attempt was made to execute a task flow template. Task flow templates cannot be executed.
-
Action: Correct the associated task flow call activity to refer to a task flow definition.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-00010: A DataControlFrame savepoint handle does not exist.
-
Cause: Restore of a DataControlFrame savepoint was attempted when a savepoint handle did not exist. Savepoint handle can become null after an ADFc save for later savepoint was restored.
-
Action: Contact the system administrator.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-00011: The ADF Controller is unable to create an MDSSession. See exception for details.
-
Cause: The ADF Controller requires an MDSSession to locate metadata. An attempt to create an MDSSession failed. This could be caused by a number of problems.
-
Action: See the accompanying exception.
Level: 2
Type: ERROR
Impact: Configuration
- ADFC-00019: An incorrect object is specified by EL expression ''{0}'' for a URL parameter converter.
-
Cause: An object was specified by the EL expression that did not implement the oracle.adf.controller.UrlParameterConverter interface.
-
Action: Specify an object that implements the oracle.adf.controller.UrlParameterConverter interface.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-00020: Task flow ''{0}'' requires a new transaction, but a transaction is already open on the frame.
-
Cause: A new transaction could not be started on the frame because a transaction was already open.
-
Action: Correct the application's flow or the task flow's metadata.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-00021: Task flow ''{0}'' requires a shared DataControlFrame but parent frame is null.
-
Cause: The task flow is configured to share its DataControl scope with its parent. The parent DataControlFrame is null.
-
Action: Correct the application's flow or the task flow's metadata.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-00025: The ADF controller has not been successfully initialized.
-
Cause: The ADF controller has not been successfully initialized, probably due to a configuration error.
-
Action: Contact the system administrator and inspect the server logs for information on why the initialization failed.
Level: 2
Type: ERROR
Impact: Configuration
- ADFC-00028: The ADF controller encountered an error while parsing the /WEB-INF/web.xml file.
-
Cause: The ADF controller encountered an error while parsing the /WEB-INF/web.xml file.
-
Action: Review the /WEB-INF/webg.xml file and inspect the server logs for information on why the parsing failed.
Level: 2
Type: ERROR
Impact: Configuration
- ADFC-00029: Attempt to acquire the root view port request lock failed due to a timeout.
-
Cause: Typically caused by another thread holding the request lock for to long, possible due to a deadlock.
-
Action: Contact the system administrator and inspect the server logs.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-00030: The ADF Page Flow functionality requires the full ADF Faces runtime which does not appear to be present, application configuration is invalid.
-
Cause: The ADF Page Flow feature was not able to verify a fully functional ADF Faces runtime is present.
-
Action: Update the application's deployment configuration to include the full ADF Faces runtime.
Level: 2
Type: ERROR
Impact: Installation
- ADFC-00626: ADF does not support calling ConfigurableNavigationHandler.performNavigation() after the INVOKE_APPLICATION phase has completed.
-
Cause: A call to ConfigurableNavigationHandler.performNavigation() was made during an incorrect phase of the request lifecycle.
-
Action: Contact the system administrator.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-02016: A possible cyclic reference to template ''{0}'' is detected when parsing ''{1}''.
-
Cause: The task flow metadata references a template that is already referenced by this task flow.
-
Action: Verify that the task flow templates do not reference each other in a cyclic manner.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-04003: The PagePhaseListener of type ''{0}'' with listener ID of ''{1}'' cannot be registered because it is part of the internal API.
-
Cause: The ADF Controller was unable to register an internal PagePhaseListener using the public API.
-
Action: Use a PagePhaseListener that is not internal.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-04005: The PagePhaseListener with ID ''{0}'' is internal and cannot be removed.
-
Cause: A failed attempt was made to remove an internal PagePhaseListener. This operation is not supported.
-
Action: Ensure that a PagePhaseListener is public, not internal, before attempting to remove it.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-04007: The FacesPageLifecycleContext does not exist yet.
-
Cause: An attempt was made to retrieve the FacesPageLifecycleContext before it was created.
-
Action: Wait until the RestoreView phase of the JavaServer Faces lifecycle to retrieve the FacesPageLifecycleContext.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-06000: The ADF Controller caught exception ''{0}'' while performing control flow routing. See the stack trace for details.
-
Cause: An unhandled exception occurred while the ADF Controller was executing the application's control flow.
-
Action: See the associated exception. Verify that the navigation rules are correctly specified. Verify that the correct outcome was generated to trigger routing.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-06002: unhandled exception
-
Cause: The ADF Controller encountered an exception. Either no exception handler activity was defined or the ADF Controller and task flow were not configured to catch this exception.
-
Action: See the associated exception. Verify that the exception handler activity is correctly defined. Contact the system administrator.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-06005: The ADF Controller is unable to invoke URL parameter validator.
-
Cause: A view activity defines one or more parameter validators. Invoking the parameter validator failed.
-
Action: See the associated exception. Verify that the metadata refers to the correct class and method.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-06006: An exception occurred when evaluating method expression ''{0}'' specified for ''{1}'' defined in ''{2}''.
-
Cause: A view activity defines a bookmark method. Invoking the specified method failed.
-
Action: See the associated exception. Verify that the metadata refers to the correct class and method.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-06007: The ADF Controller is unable to copy task flow input parameters. Objects must be serializable.
-
Cause: The task flow call activity specifies one or more input parameters. The ADF Controller was unable to copy the specified values.
-
Action: See the associated exception. Verify that the metadata refers to the correct class and method. Verify that the specified objects are serializable.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-06012: Task flow ID returned from a remote call does not match the called task flow's ID, calledId= ''{0}'', returnedId= ''{1}''.
-
Cause: The task flow ID returned from a remote task flow call did not match the ID of the task flow that was called.
-
Action: Contact the system administrator.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-08005: Exception occured when evaluating an expression used for savepoint ID.
-
Cause: The task flow contains at least one save point restore activity. An attempt to evaluate the value for savepoint ID failed.
-
Action: See the associated exception. Check the task flow metadata.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-08010: The ADF Controller was unable to find the JOC-based state manager implementation.
-
Cause: The ADF Controller was unable to use the Java Object Cache to store savepoints.
-
Action: Make sure that the JOC is available. Contact the system administrator.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-08013: The ADF Controller is unable to query the database for the current user's savepoint IDs.
-
Cause: The ADF Controller was unable to query the database for the set of savepoints.
-
Action: See the associated exception. Contact the system administrator.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-08014: The ADF Controller is unable to execute the save point restore activity.
-
Cause: The task flow contains a savepoint restore activity. An attempt to execute that activity failed.
-
Action: See the associated exception. Verify that the metadata is correct. Contact the system administrator.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-08023: The ADF Controller is encountering an error while invoking a savepoint restore finalizer.
-
Cause: The task flow specifies a savepoint restore finalizer. Execution of the finalizer raised an exception.
-
Action: See the associated exception. Verify that the metadata references the correct class and method.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-10007: A possible cyclic reference to managed bean ''{0}'' is detected.
-
Cause: The task flow metadata referenced a managed bean that was already referenced by this task flow.
-
Action: Verify that the managed bean is not already specified in a referenced template.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-10008: Outcome to-string metadata cannot be specified for a method call activity that points to a void Java method. Activity ID: ''{0}''.
-
Cause: The method call activity outcome metadata specified to-string.
-
Action: Change the method outcome metadata to use fixed-outcome, or change the Java to return a java.lang.String value.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-12000: State ID in request is invalid for the current session.
-
Cause: The request contained a state instance ID, but it did not exist in the session, nor was this a request for a bookmarked resource. This might be due to a session timeout.
-
Action: Contact the system administrator.
Level: 2
Type: ERROR
Impact: Session
- ADFC-12006: The scope of the referenced object ''{0}'' is shorter than the referring object ''{1}''.
-
Cause: An attempt was made to access a managed bean outside its scope.
-
Action: See the associated exception. Verify that the managed bean is correctly defined and that the reference is valid.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-12009: An application is accessing the page flow scope prematurely.
-
Cause: An application attempted to access the page flow scope early in the request lifecycle, before the page flow scope was available.
-
Action: Modify the application to access the page flow scope later in the request lifecycle.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-14003: Region does not have or cannot reach a view activity.
-
Cause: The region specified a task flow where no view activities could be reached.
-
Action: Verify that the correct task flow is specified. Verify that the task flow has at least one navigable view.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-14004: The ADF Controller cannot execute task flow ''{0}'' that uses page fragments in the root view port.
-
Cause: The task flow definition declares this task flow as using page fragments. The root viewport can only run task flows that use pages, not page fragments.
-
Action: Remove the use-page-fragments flag from the task flow definition ''{0}''.
Level: 2
Type: ERROR
Impact: Programmatic
- ADFC-14018: Cannot create a taskflow binding with a null id. Check taskFlowList attribute for multi task flow binding ''{0}''.
-
Cause: The expression of the taskFlowList attribute evaluate to a list that contain a TaskFlowBindingAttributes with a null id.
-
Action: Contact the system administrator.
Level: 2
Type: ERROR
Impact: Programmatic