1 ADF_FACES-00001 to ADF_FACES-60098
- ADF_FACES-00003: Unable to mark future region component client IDs that might be added to the RegionModel as needing a redraw because it is not supported in this implementation of the RegionModel.
-
Cause: The RegionModel was incorrectly subclassed.
-
Action: Contact Oracle Support Services.
Level: 1
Type: INCIDENT_ERROR
Impact: Logging
- ADF_FACES-00017: eventContext is set to launcher, but no launch ID is available. To use eventContext launcher the popup must be launched on the client with the hint AdfDhtmlPopupWindow.HINT_LAUNCH_SOURCE_ID set. See the popup doc for more information.
-
Cause: the eventContext was set to launcher, but no launch ID is available.
-
Action: To use eventContext launcher the popup must be launched on the client with the hint AdfDhtmlPopupWindow.HINT_LAUNCH_SOURCE_ID set. See the popup doc for more information.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-00018: The launcherVar attribute is set, but the eventContext attribute is not set to launcher. LauncherVar is only made available when eventContext is set to launcher.
-
Cause: The launcherVar attribute was set, but the eventContext attribute was not set to launcher.
-
Action: Remove launcherVar attribute or set eventContext attribute to launcher.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-00020: invokeOnComponent() is being called on the region with id {0} from inside of its RegionModel's processBeginRegion()
-
Cause: This happens when the RegionModel implementation calls invokeOnComponent() before returning from its RegionModel's processBeginRegion(), typically because the application has used the expression language to bind a task flow parameter to a function that call invokeOnComponent().
-
Action: Instead of dynamically retrieving the component state with invokeOnComponent(), stash the value in application state, where it can be retrieved directly.
Level: 1
Type: NOTIFICATION
Impact: Logging
- ADF_FACES-00021: The value {0} passed as identifier name to MoveChildComponentChange is not valid. Defaulting to 'id'.
-
Cause: This happens when a MoveChildComponentChange is constructed with a value other than 'id' for identifier.
-
Action: Pass 'id' as the value.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-00023: The MethodExpression wrapper of an include component was not able to locate the component after being deserialized. The expression will not be functional. Client ID not found was {0}
-
Cause: Method expression was not deserialized when the include for its component was in the current component tree.
-
Action: The method expressions of properties of include components may only be desirialized when their component trees are the current ones.
Level: 2
Type: WARNING
Impact: Logging
- ADF_FACES-10021: During the processing of the include component, the context change found did not match the current component.
-
Cause: DDuring the processing of the include component, the context change found did not match the current component.
-
Action: Contact Oracle Support Services.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-10023: readObject not supported for deserialization, SerializationProxy Required.
-
Cause: An attempt was made to call readObject on a class that uses a SerializationProxy, therefore readObject should never be called.
-
Action: Contact Oracle Support Services.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-10024: The implemementation of AdfFacesContext was not found. If this is a rich client application, it will not function. This is expected for Trinidad applications.
-
Cause: AdfFacesContextImpl was not found on the class path.
-
Action: Contact Oracle Support Services if this is a rich client application.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-30001: invalid value for configuration parameter Estimated Number of Pages Per Channel: {0}
-
Cause: Configuration of estimated number of pages per channel in adf-config.xml has exceeded 2,147,483,647.
-
Action: Fix configuration of pages-per-channel to a reasonable value.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30044: Invalid model provided to progressIndicator (should be a BoundedRangeModel); progressIndicator ID: {0}.
-
Cause: The value of the progressIndicator was not a BoundedRangeModel.
-
Action: Use the development tools to open the page and fix the progressIndicator.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30048: Could not launch window, as render kit does not support the ExtendedRenderKitService.
-
Cause: Launching a window required the ExtendedRenderKitService, but the current render kit does not support this service.
-
Action: Switch the RenderKitId to point to a render kit that supports the ExtendedRenderKitService.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30052: The group attribute on the selectBooleanRadio component is null. It must be set to a non-null value for the selectBooleanRadio component to function properly.
-
Cause: No group attribute was set on selectBooleanRadio.
-
Action: Set the group value on the selectBooleanRadio component.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30057: Table inlineStyle will be ignored because width:auto is not supported.
-
Cause: The inline CSS property width:auto was ignored because it is not supported on table component to control its size.
-
Action: Remove the inlineStyle property on the table component.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30102: The rich text editor is not supported in the specified agent: {0}.
-
Cause: An attempt was made to use the rich text editor component in an unsupported web browser.
-
Action: Ensure that the browser used is supported by this rich text editor component.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-30107: The view state of the page has expired. Reload the page.
-
Cause: The UI state of the view has expired, either because the back button has been used too many times, too many page submissions have occurred on ther pages, or because of an underlying bug in the view code.
-
Action: The application using ADF should install an ADFc error handler for JSF ViewExpiredExceptions, or configure the org.apache.myfaces.trinidad.CLIENT_STATE_MAX_TOKENS web.xml parameter to a larger value.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-30108: The view state of the page has expired because of inactivity. Reload the page.
-
Cause: The UI state of the view has expired because the session has expired.
-
Action: The application using ADF should install an ADFc error handler for JSF ViewExpiredExceptions.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-30109: Conversion failed while trying to synchronize value from client. Attempted to convert: {0}, Component ID: {1}.
-
Cause: An attempt was made to set a value on the client that could not be converted on the server.
-
Action: Make sure application setting legal value on client.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30114: The converter supplied for inputDate with ID: {0} is not an instance of javax.DateTimeConverter: {1}. This input field will only support showing dates. To get time and/or timezone support, subclass the converter from javax.DateTimeConverter.DateTimeConverter or obtain the converter using Application.createConverter (preferred).
-
Cause: The supplied converter was not a subclass of javax.DateTimeConverter.
-
Action: Use the converter supplied by javax.faces.application.Application.createConverter, or make the custom converter subclass javax.DateTimeConverter.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30115: The converter supplied for InputDate with ID: {0} does not implement the ClientConverter interface: {1}. The input field will not support client conversion or validation, and only the input field will be displayed (no date-picker popup). To get client conversion and validation support, implement the org.apache.myfaces.trinidad.convert.ClientConverter interface or obtain the converter using javax.faces.application.Application.createConverter (preferred). If you just want to set the converter pattern programmatically, obtain it using createConverter and call setPattern() on it.
-
Cause: The supplied converter does not implement the ClientConverter interface.
-
Action: Use the converter supplied by Application.createConverter, or make the custom converter implement org.apache.myfaces.trinidad.convert.ClientConverter.
Level: 1
Type: ERROR
Impact: Logging
- ADF_FACES-30116: User activity information for the {0} request is not available.
-
Cause: User activity Information was null when logging this information to monitoring service.
-
Action: Ensure that user activity information is not null when monitoring service is enabled.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30121: No af:document ancestor for af:skipLinkTarget in component: {0}. af:skipLinkTarget must be used in conjunction with af:document.
-
Cause: Missing af:document ancestor for af:skipLinkTarget.
-
Action: Remove af:skipLinkTarget, or move inside of an af:document.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30122: Invalid parent for af:skipLinkTarget in component: {0}. af:skipLinkTarget must placed inside of a component that generates content.
-
Cause: af:skipLinkTarget must be placed inside of a component that generates content.
-
Action: Remove the af:skipLinkTarget, or move it inside of a parent which generates content.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30123: Invalid facet size for af:panelStretchLayout: {0}. {1} is not a valid CSS length.
-
Cause: An invalid value was specified for a panelStretchLayout size (topHeight, bottomHeight, startWidth, endWidth) attribute.
-
Action: Specify valid CSS lengths for the panelStretchLayout size (topHeight, bottomHeight, startWidth, endWidth) attributes.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30124: Multiple forms detected on viewId: {0}. Rich client currently has some limitations in dealing with multiple forms.
-
Cause: An ADFFaces page was detect with multiple forms on the same page. Currently there are a number of issues associated with multiple forms on the same page and this should be done with caution.
-
Action: Reorganize page so that it contains only one form.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30125: Exported rows type: {0} is not supported by exportCollectionActionListener.
-
Cause: Unsupported exported rows type was specified.
-
Action: Use one of the supported exported rows types as specified in exportCollectionActionListener tag documentation.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-30138: Ignoring AdfBootstrap feature in partition {0}. The AdfBootstrapFeature must reside in its own partition.
-
Cause: A partition was defined which contains both the AdfBootstrap feature as well as other features.
-
Action: The AdfBootstrap feature should be moved to its own partition.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30139: Could not find the component with relative ID {0} from {1}. This method will try to locate the component for the given ID by calling findComponent on its parent NamingContainer as a final attempt.
-
Cause: The identifier provided did not account for NamingContainers properly.
-
Action: Ensure that the relative ID specified is correct and the component with that ID exists.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30140: The slider component with label {0} has too many ticks that are rendered. This will have a huge performance impact.
-
Cause: The provided minimum is too small or the provided maximum is too large.
-
Action: Provide a better range for the slider by modifying the maximum and/or minimum attributes.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30141: Unable to remove the criterion with rowKey {0} because a criterion with the specified rowKey could not be located.
-
Cause: This could happen if an attempt is made to remove an already removed criterion and likely in slow performing applications
-
Action: Ensure that criterion fields are removed only once.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30145: A duplicate definition for the feature "{0}" has been found at {1}, line {2}. A feature with the same name was originally defined at {3}, line {4}. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
-
Cause: This occurs when there are multiple copies of a jar file containing the same adf-js-features.xml on the class path. Or, alternatively, this may come up if different adf-js-features.xml use the same feature name.
-
Action: Check for multiple copies of the jar containing the feature definition on the class path. Or, check to see whether feature names are unique.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30147: The converter supplied for InputColor with ID: {0} does not implement the ClientConverter interface: {1}. The input field will not support client conversion or validation, and only the input field will be displayed (no color-picker popup). To get client conversion and validation support, implement the org.apache.myfaces.trinidad.convert.ClientConverter interface or obtain the converter using javax.faces.application.Application.createConverter (preferred). If you just want to set the converter pattern programmatically, obtain it using createConverter and call setPattern() on it.
-
Cause: The supplied converter does not implement the ClientConverter interface.
-
Action: Use the converter supplied by Application.createConverter, or make the custom converter implement org.apache.myfaces.trinidad.convert.ClientConverter.
Level: 1
Type: ERROR
Impact: Logging
- ADF_FACES-30148: The supplied converter {1} with ID {0} does not implement the ClientConverter interface. The input field will not support client conversion or validation. Only normal string to number conversion will be supported, such as "5" to 5, but not "five" to 5. To get client conversion and validation support, implement the org.apache.myfaces.trinidad.convert.ClientConverter interface or obtain the converter using javax.faces.application.Application.createConverter (preferred). If you just want to set the converter pattern programmatically, obtain it using createConverter and call setPattern() on it.
-
Cause: The supplied converter does not implement the ClientConverter interface.
-
Action: Use the converter supplied by Application.createConverter, or make the custom converter implement org.apache.myfaces.trinidad.convert.ClientConverter.
Level: 1
Type: ERROR
Impact: Logging
- ADF_FACES-30149: No PartitionManager found, possibly due to passivation or failover. Re-creating the PartitionManager.
-
Cause: The PartitionManager object is null, either due to passivation or failover.
-
Action: No action required. The PartitionManager will be re-created.
Level: 1
Type: NOTIFICATION
Impact: Logging
- ADF_FACES-30152: The Calendar Toolbox Layout contains 'all' as well as built-in value {0}. 'all' will be used.
-
Cause: If the toolboxLayout contains 'all', the other built-in values should not be used.
-
Action: Correct the toolboxLayout attribute to specify 'all' or the built-in value desired.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30153: Unable to find facet corresponding to Calendar custom toolboxLayout value {0}.
-
Cause: A custom value was encountered for the toolboxLayout but no corresponding facet was found.
-
Action: Check that the facet has been added and that its name matches the value specified in toolboxLayout.
Level: 1
Type: SEVERE
Impact: Logging
- ADF_FACES-30156: The ALLDAY activity {0} has an invalid start and end date and it may not render correctly. See the CalendarActivity Javadoc for information about valid values for startDate and endDate for an ALLDAY activity.
-
Cause: A null value was supplied for the activity's activityId.
-
Action: Check the activity source and ensure the activityId is not null.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30157: The ChooseColor component with client id {0} has width {1} which is too large. This will have a huge performance impact. In Design mode, the component will render with maximum width {2}
-
Cause: The provided width is too large.
-
Action: Reduce the width attribute of the component.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30159: Invalid value {0} specified for the oracle.adf.view.rich.SUPPRESS_IDS context parameter.
-
Cause: Invalid value specified for the oracle.adf.view.rich.SUPPRESS_IDS context parameter.
-
Action: Check web.xml file to verify that a valid SUPPRESS_IDS value is specified.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30160: Invalid value {0} specified for calendar attribute 'availableViews'.
-
Cause: The value specified for calendar attribute 'availableViews' was not recognized.
-
Action: Correct the 'availableViews' attribute to one of the following: all, day, week, month, list
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30161: The availableViews attribute contains 'all' as well as built-in value {0}. 'all' will be used.
-
Cause: If availableViews contains 'all', the other built-in values should not be used.
-
Action: Correct the availableViews attribute to specify 'all' or the built-in value desired.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30162: The 'view' attribute {0} does not correspond to one of the built-in availableViews. The calendar will display {1}.
-
Cause: The 'view' attribute should correspond to one of the views specified in 'availableViews'. If 'availableViews' is unspecified or set to 'all', the 'view' attribute should be one of the built-in views: day, week, month, list.
-
Action: Correct the 'view' attribute to be one of the views displayed in 'availableViews'.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30163: The application is running with the new window detect flag off. It is highly recommended that this flag be turned on to ensure proper functioning of your application when new browser windows are launched. In web.xml set the context parameter oracle.adf.view.rich.newWindowDetect.OPTIONS to 'on'.
-
Cause: When new window detection is turned off, browser window dialog may not work as expected.
-
Action: Trun on new window detection by adding context paramter oracle.adf.view.rich.newWindowDetect.OPTIONS to web.xml with a value of on.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30174: An invalid or null contextId was provided when logging userActivity information for the previous request.
-
Cause: This may occur if the previous response sent to the client included a null contextId or an error occurred in the client when retrieving the userActivity info.
-
Action: None.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30175: A null contextId was returned by the service provider implementation for the ExecutionContextProvider.
-
Cause: A null contextId was returned by the ExecutionContextProvider implementation.
-
Action: Ensure that a proper service provider has been registered in META-INF/services.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-30180: Circular dependency detected in the geometry management configuration of component id {0}.
-
Cause: The component has an attribute assignment that resulted in a circular dependency.
-
Action: See the geometry management section of that component's tag documentation for more information.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-60059: A null QueryModel object was found.
-
Cause: Either a QueryModel was not set on the query component, or the expression for the model property resolved to a null or invalid object.
-
Action: Use the development tools to open the page and fix the query.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-60060: A null ListOfValuesModel object was encountered.
-
Cause: Either a ListOfValuesModel object was not set on the lov component, or the expression for the model property resolved to a null or invalid object.
-
Action: Use the development tools to open the page and fix the list of values component.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-60063: Invalid facet size for af:decorativeBox: {0}. {1} is not a valid CSS length.
-
Cause: An invalid value was specified for a decorativeBox size (e.g. topHeight) attribute.
-
Action: Specify valid CSS lengths for the decorativeBox size (e.g. topHeight) attributes.
Level: 1
Type: WARNING
Impact: Logging
- ADF_FACES-60068: attempting to add setPropertyListener with type set to valueChange to component that is not editableValueHolder
-
Cause: Attempted to add setPropertyListener with type set to valueChange to component that is not editableValueHolder.
-
Action: Move the setPropertyListener tag or change the type event it is listening for.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-60070: Attempting to add requested listener to component of type: {0} has failed. For the type: {1}, the setPropertyListener tag requires that the component have a method: {2}.
-
Cause: For the type given, there was no appropriately named add method for the setPropertyListener to call in order to add itself as a listener.
-
Action: Change the type attribute to an event type that is supported on the component, or remove the setPropertyListener tag.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-60074: attempting to add setPropertyListener with type set to action to component that is not actionSource
-
Cause: Attempted to add setPropertyListener with type set to action to component that is not actionSource.
-
Action: Move the setPropertyListener tag or change the type event it is listening for.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-60079: The 'availableViews' attribute of the calendar contains 'month' but not 'day'. If 'month' is present, 'day' is required as well.
-
Cause: The calendar 'availableViews' is configured to show month view but not day view.
-
Action: Correct the availableViews attribute to include 'day'.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-60080: The 'availableViews' attribute of the calendar does not contain any valid values.
-
Cause: The calendar 'availableViews' attribute is specified but does not contain any recognized values.
-
Action: Correct the availableViews attribute to use a valid combination of values (all, day, month, week, list) or leave unspecified to show the default views (all) .
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-60089: An attempt to store a file larger than the configured value ({0}) for oracle.adf.view.rich.portal.FILE_DOWNLOAD_MAX_DISK_SPACE was encountered.
-
Cause: A call to a method on a FileDownloadActionListener resulted in a file being stored on the file system. The oracle.adf.view.rich.portal.FILE_DOWNLOAD_MAX_DISK_SPACE parameter in web.xml was either not configured so the default limit of 2MB was exceeded, or the file was larger than the configured value.
-
Action: Either add or update the oracle.adf.view.rich.portal.FILE_DOWNLOAD_MAX_DISK_SPACE context-param in web.xml to allow for the desired max file size.
Level: 2
Type: ERROR
Impact: Logging
- ADF_FACES-60094: Unrecognized feature in PanelCollection featuresOff attribute: {0}.
-
Cause: An invalid feature name used in PanelCollection featuresOff attribute.
-
Action: Use a valid feature name. Feature names are case-sensitive. Refer to the PanelCollection tag docs.
Level: 1
Type: WARNING
Impact: Logging