2 ADF_TRINID-00001 to ADF_TRINID-30336
- ADF_TRINID-00016: Could not get resource key {0} from skin {1}
-
Cause: ResourceBundle key does not exist in any resource bundle in framework or skin.
-
Action: Log a bug against the application or make sure the resource key exists in skin by checking the skin resource files (see trinidad-skins.xml).
Level: 1
Type: ERROR
Impact: Logging
- ADF_TRINID-00020: Failed to get hold of DecimalFormat for type: {0} decimal separator, number grouping separator, currency code will be defaulted based on locale {1}
-
Cause: DecimalFormat not set up
-
Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-00021: RequestContext is null: decimal separator, number grouping separator, currency code will be defaulted based on locale
-
Cause: RequestContext was not set up yet.
-
Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-00026: The viewId property in ViewIdPropertyMenuModel is null. The viewId property is needed to find the focus rowKey.
-
Cause: viewIdProperty that is used to retrieve the viewId from a node in the tree is null.
-
Action: Set the viewIdProperty to be non-null or log a bug against the application.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-00037: Unable to find ResourceLoader for ResourceServlet at servlet path:{0} Cause: Could not find resource:{1}
-
Cause: Resource missing
-
Action: Make sure the resource can be found. Make sure the jars are installed correctly. Log a bug against the application.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-00038: Trinidad ResourceServlet is running in debug mode. Do not use in a production environment. See the {0} parameter in /WEB-INF/web.xml
-
Cause: Application is running in debug mode.
-
Action: Change the parameter in web.xml so that it is not running in debug mode.
Level: 1
Type: NOTIFICATION
Impact: Logging
- ADF_TRINID-00043: Event {0} was delivered to a showDetail already in that disclosure state.
-
Cause: Renderer delivered an unnecessary event or it set disclosed on its own instead of waiting for the disclosure event.
-
Action: Check the showDetail renderer code or log a bug against the application.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-00059: Cannot construct an ChangeComponentProxy with null uiComponent.
-
Cause: ChangeManager, IllegalArgumentException, constructor error
-
Action: Use a non null UIComponent parameter in the ChangeComponentProxy. Check the API. Log a bug against the application.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-00066: Cannot construct an AddFacetChange with either of facetName or facetComponent being null.
-
Cause: ChangeManager, IllegalArgumentException, constructor error
-
Action: Fix the constructor to use a non-null facetName or facetComponent or log a bug against the application.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-00073: Trying to release a different RenderingContext than the current context.
-
Cause: An attempt was made to release a RenderingContext that is not the current RenderingContext.
-
Action: Fix the code that tried to release the RenderingContext or log a bug against the application.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-00074: This is not an error. This trace is for debugging.
-
Cause: This is not an error. This trace is for debugging the RequestContext class.
-
Action: No action needed since this is a debugging log message only. You can set the LOG to greater than FINEST to turn off the message.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-00075: Trying to release a different RequestContext than the current context.
-
Cause: An attempt was made to release a RequestContext that is not the current RequestContext.
-
Action: Make sure the release method was called by the same code that created the RequestContext or log a bug against the application.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-00076: Factory already available for this class loader.
-
Cause: IllegalStateException, an attempt was made to set in a map a RequestContextFactory that already exists for this classloader
-
Action: Do not call setFactory(RequestContextFactory factory) with a RequestContextFactory that already exists for the class loader or log a bug against the application.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-00118: The default FacesMessage.FACES_MESSAGES cannot be found
-
Cause: NullPointerException. FacesMessage.FACES_MESSAGES from the jsf spec could not be found.
-
Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-00120: custom message should be of type ValueBinding or String
-
Cause: IllegalArgumentException, custom message in method was not of the correct type.
-
Action: Fix the customMessagePattern to be a ValueBinding or a String Object or log a bug against the application.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-00122: FacesContext.getRenderKit() returned null while trying to get the {0} service; please check your configuration.
-
Cause: IllegalStateException, while getting a service in the Service utility code.
-
Action: Log a bug against the application. Check your configuration and check that the jsf jars are all installed correctly.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-00123: FacesContext or Component is null
-
Cause: NullPointerException, the FacesContext or UIComponent passed to the method was null.
-
Action: Log a bug against the application. Check your configuration and check that the jsf jars are all installed correctly.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-00124: Encoding: {0} is unsupported by JVM
-
Cause: IllegalCharsetNameException while trying to encode in the ByteLength Validator using an encoding that is not supported by the JVM.
-
Action: Check the encoding and check the JVM. Otherwise log a bug against the application.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-30005: "Cannot resolve capabilities file"
-
Cause: Exception while attempting to load the Capabilities document META-INF/agent/capabilities.xml
-
Action: Make sure the Apache Trinidad framework jars are installed. Log a bug against the Apache Trinidad framework.
Level: 1
Type: ERROR
Impact: Logging
- ADF_TRINID-30010: Element {0} has missing (or empty) attributes
-
Cause: While attempting to parse a document, the element should have attributes but doesn't.
-
Action: Make sure the document that is being parsed has the correct syntax and attributes. Log a bug against the Apache Trinidad framework or the application.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30012: Unable to parse model string
-
Cause: Error occured while parsing the device nodes in the capabilities file
-
Action: Check the capabilities document. Make sure the capabilities document is valid xml. Log a bug against the Apache Trinidad framework.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30019: Apache Trinidad is running with time-stamp checking enabled. This should not be used in a production environment. See the {0} property in WEB-INF/web.xml
-
Cause: time-stamp checking is enabled in web.xml.
-
Action: Turn off time-stamp checking in a production environment.
Level: 1
Type: NOTIFICATION
Impact: Logging
- ADF_TRINID-30028: RequestContext had not been properly released on earlier request.
-
Cause: RequestContext was checked to see if it was released and it wasn't.
-
Action: No action needed, since the code will clean this up. Check the code to make sure it is properly releasing the RequestContext.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30029: Unable to set request character encoding to {0}, because request parameters have already been read.
-
Cause: Attempting to set the character encoding after parameters have been retrieved.
-
Action: Log a bug against the Apache Trinidad framework because the code is calling setCharacterEncoding at the wrong time.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30032: RenderKit {0} does not support DialogRenderKitService, and cannot be used to launch dialogs; using a single window instead.
-
Cause: Attempting to launch dialog.
-
Action: Use a renderkit that supports DialogRenderKitService or don't use DialogRenderKitService.
Level: 1
Type: NOTIFICATION
Impact: Logging
- ADF_TRINID-30035: Could not find partial trigger {0} from {1}
-
Cause: Attempting to find partial trigger.
-
Action: Make sure the partialTriggers are set to an existing component's id. View the jspx page in JDeveloper and JDeveloper will flag the errors for you. Log a bug against the application.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30050: The value of the "{0}" attribute starts with "javascript:"; this is unnecessary, and in fact can lead to Javascript errors.
-
Cause: Attempting to write the html to the page.
-
Action: Fix the attribute in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1
Type: NOTIFICATION
Impact: Logging
- ADF_TRINID-30055: Attribute "{0}" output twice; writing attribute as "duplicate_{1}" instead.
-
Cause: Attempting to write the html to the page.
-
Action: Fix this in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30069: Renderer '{0}' not found for component family '{1}'
-
Cause: Attempting to instantiate a Renderer failed.
-
Action: Check that your renderer is registered correctly in faces-config.xml. Log a bug against the application or Apache Trinidad framework.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30071: The skin {0} specified on the requestMap will not be used because the styleSheetDocument id on the requestMap does not match the local skin's styleSheetDocument's id.
-
Cause: A skin was specified on the requestMap but it can't be used.
-
Action: Log a bug against the application. Check to make sure the jars on the portal server match the jars on the portlet server to make the skin's styleSheetDocument ids match.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30072: The skin {0} specified on the requestMap will not be used because its styleSheetDocument id was not in the requestMap and it is needed to compare with the local skin's styleSheetDocument's id to make sure the skins are the same.
-
Cause: A skin was specified on the requestMap but it can't be used.
-
Action: Log a bug against the application. Check to make sure the jars on the portal server match the jars on the portlet server to make the skin's styleSheetDocument ids match. Also, send the styleSheetDocument id to the server as well as the skin id.
Level: 1
Type: ERROR
Impact: Logging
- ADF_TRINID-30073: The skin {0} specified on the requestMap will not be used because it does not exist.
-
Cause: A skin was specified on the requestMap but it can't be used because it does not exist on the server.
-
Action: Log a bug against the application. Check to make sure the jars on the portal server match the jars on the portlet server to make the skin's styleSheetDocument ids match.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30094: There is already a converter on "{0}". There should only be one converter per component.
-
Cause: More than one converter found on a component.
-
Action: Log a bug against the application. Ensure you have only one converter per component in your page.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30096: Warning: illegal component hierarchy detected, expected UIXCommand but found another type of component instead.
-
Cause: Did not find the expected command component in the hierarchy.
-
Action: Log a bug against the application. Check your component hierarchy in your page.
Level: 1
Type: ERROR
Impact: Logging
- ADF_TRINID-30097: Warning: NavigationLevelRenderer was looking for child property "{0}" but none was found, it is likely that an unexpected child component was found (expected CommandNavigationItem).
-
Cause: Rendering navigationLevel component and did not find expected child.
-
Action: Log a bug against the application. Make sure CommandNavigationItem is a child of the navigationLevel component
Level: 1
Type: ERROR
Impact: Logging
- ADF_TRINID-30101: The number of items selected for shuttle '{0}' exceeds the total number of items in the shuttle. No selected items will be returned.
-
Cause: Rendering the shuttle component and the selected items.
-
Action: Log a bug against the application. Check the shuttle component and its children.
Level: 1
Type: ERROR
Impact: Logging
- ADF_TRINID-30109: Apache Trinidad is running with debug javascript. Do not use in a production environment. See the "+_DEBUG_JAVASCRIPT+" parameter in /WEB-INF/web.xml
-
Cause: debug javascript is enabled in web.xml.
-
Action: Turn off debug javascript checking in a production environment in web.xml.
Level: 1
Type: NOTIFICATION
Impact: Logging
- ADF_TRINID-30112: tableSelect components may only be used inside table and treeTable
-
Cause: While rendering tableSelect component the valid parent component was not found.
-
Action: Log a bug against the application. Make sure tableSelect components are inside table or treeTable.
Level: 1
Type: ERROR
Impact: Logging
- ADF_TRINID-30113: nodeStamp facet on treeTable:{0} is missing or not of type UIXColumn
-
Cause: While rendering a treeTable component, a problem with the nodeStamp facet was found.
-
Action: Log a bug against the application. See the treeTable documentation and check your jspx page.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30114: Unexpected tree state: focus rowKey is empty on an expand/collapse all request.
-
Cause: While rendering a tree component an unexpected tree state was found.
-
Action: Log a bug against the application. See the treeTable or tree documentation and check your jspx page.
Level: 1
Type: ERROR
Impact: Logging
- ADF_TRINID-30128: Error when parsing the skin css file. The property's name cannot be null or the empty string. The parser will ignore it. name is '{0}' and value is '{1}'
-
Cause: While parsing the skin css file, an error was found.
-
Action: Log a bug against the application. Check your skin css file.
Level: 1
Type: ERROR
Impact: Logging
- ADF_TRINID-30133: Can't find a skin that matches family {0} and renderkit {1}, so we will use the simple skin
-
Cause: While retrieving a skin, an error was found.
-
Action: Log a bug against the application. Check your trinidad-skins.xml file to make sure the skin is defined correctly. Check trinidad-config and the skin-family element. Make sure the skin's renderkitid matches the current renderkit id
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30134: Could not get the stylesheet document's timestamp because we couldn't open the connection.
-
Cause: Trying to get the skin's stylesheet document's timestamp failed.
-
Action: Log a bug against the application. Check the stylesheet document file and directory to make sure it can be opened.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30135: The following skins extend each other in a circular fashion or the skin they extend does not exist:{0}
-
Cause: While registering the skins from the trinidad-skins.xml files, an error was found.
-
Action: Log a bug against the application. Check all the trinidad-skins.xml files (even the ones in jars on the classpath) to fix any skins that extend others in a circular fashion.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30136: Unable to locate base skin "{0}" for use in defining skin of id "{1}", family "{2}", renderkit ID "{3}". Using the default base skin "{4}".
-
Cause: While registering the skins from the trinidad-skins.xml files, an error was found.
-
Action: Log a bug against the application. Check all the trinidad-skins.xml files (even the ones in jars on the classpath) to make sure the base skin exists and do not extend a skin that doesn't exist.
Level: 1
Type: ERROR
Impact: Logging
- ADF_TRINID-30143: Unable to generate the style sheet {0} in cache directory {1}.Please make sure that the cache directory exists and is writable.
-
Cause: Error while generating skin's stylesheet.
-
Action: Log a bug against the application. Make sure that the cache directory exists and is writable.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30145: The css file has hit IE's limit of 4095 CSS selectors. It has {0} selectors. The selectors after that will be ignored.
-
Cause: Error while generating the skin's stylesheet.
-
Action: Log a bug against the application. You will need to simplify your skinning file if possible. Otherwise log a bug against Apache Trinidad.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30146: Consecutive sub-element (::) syntax used in selector {0}. This is not supported.
-
Cause: Problem found in skin's stylesheet css file.
-
Action: Log a bug against the application. The skin's css file has two pseudo-elements in one selector and that is illegal in CSS.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30192: Encoding {0} is not supported at the client side. This will skip client side validation.
-
Cause: Attempting to use an encoding the client doesn't support.
-
Action: Contact the system administrator to see if the encoding is supposed to be supported.
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30193: The TrinidadFilter has not been installed. Apache Trinidad requires this filter for proper execution.
-
Cause: Detected that the TrinidadFilter was not installed.
-
Action: Log a bug against the application. Install the TrinidadFilter; see web.xml
Level: 1
Type: WARNING
Impact: Logging
- ADF_TRINID-30218: putAll operation not supported for WrappingMap
-
Cause: UnsupportedOperationException, the WrappingMap which implements Map does not support the putAll operation and it was called.
-
Action: Log a bug against the Apache Trinidad framework. Fix code to not call putAll.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-30219: clear operation not supported for WrappingMap
-
Cause: UnsupportedOperationException, the WrappingMap which implements Map does not support the clear operation and it was called.
-
Action: Log a bug against the Apache Trinidad framework. Fix code to not call clear.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-30228: No returnId is available for returning from the dialog; this usually means that you aren't in a dialog in the first place.
-
Cause: Returning from a dialog and found no returnId.
-
Action: Log a bug against the application. To return from a dialog, you need to be in a dialog, or make the pageFlowScope available
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-30230: SelectOne submittedValue's index {0} is out of bounds. It should be between 0 and {1}
-
Cause: Rendering the selectOne component, the submittedValue was out of bounds from what it should be.
-
Action: Log a bug against the application. Possibly the model changed when it shouldn't have, so check the model.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-30231: SelectOne could not convert submittedValue's index {0} into int {1}
-
Cause: While rendering the selectOne component, the submittedValue couldn't be converted to an int.
-
Action: Log a bug against the application. Check the selectOne component's model.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-30261: Uploaded file of length {0} bytes exceeded maximum allowed length ({1} bytes)
-
Cause: EOFException while attempting to create a MultipartFormHandler for the given InputStream and content
-
Action: Use smaller files. Log a bug against the application.
Level: 2
Type: ERROR
Impact: Logging
- ADF_TRINID-30279: PropertyNode's name cannot be null or the empty string.name is ''{0}'' and value is ''{1}''
-
Cause: While trying to parse an include from an xss file a null property name was found.
-
Action: Log a bug against the application. Check the xss file being parsed for a null property name.
Level: 2
Type: ERROR
Impact: Logging