The following tables describe all of the error messages that the tools return. Aside from these, the tool also uses the message returned by any Java Exceptions or errors that are caught. Where a number appears in {} brackets, this will be replaced with an appropriate string (for example, a file name).
Message | Reason |
---|---|
File {0} does not exist | The specified file does not exist on the file system. |
Error initializing Forms JDAPI: | The tools all attempt to initialize JDAPI as a first step. The Java message for the initialization failure follows this error message. |
Invalid XML - file {0} does not validate against Forms XML Schema: | The specified file does not validate against the XML Schema for Forms. This message will follow an output of errors from the Schema validator. |
Error the document XML element must be "Module" | The XML document/root/top-most element must be a "Module" element. |
Nothing to do. | The tool on the command line has not been given anything to process. |
Ignoring invalid option: {0} | The tool on the command line has been passed an invalid argument. The tool will continue processing. |
ERROR - an exception has been encountered: | This message is returned when the tool has failed unexpectedly. |
Message | Reason |
---|---|
File {0} must be a FormModule, ObjectLibrary, or MenuModule | The given file on the command line must be of the specified
types (that is, it must have the extension .fmb , .olb
or .mmb ). |
Error reading property {0} on {1} | Returned when the dumper encounters a problem reading the specified property on the specified object. This indicates that something is wrong in the metadata or with the Form itself. |
Message | Reason |
---|---|
File {0} does not contain valid XML | The specified file is not an XML file. |
Error attaching PL/SQL library {0}, check your FORMS_PATH | The specified PL/SQL library could not be found, which means
that ti is not on the FORMS_PATH . |
Error constructing object | There was an error constructing a Form Object. This error should not occur because of the introduction of the Forms XML Schema. |
Unable to find constructor for {0} | The tool was asked to construct a Forms Object whose class name does not exist. This error should not occur because of the introduction of the Forms XML Schema. |
Error connecting to database | There was an error connecting with the string passed on the command line. This error is followed by the Java Exception message from the failed connection. |
Continuing with no DB connection (Record Group Queries will be lost) | Following the above error. |
Record Group Column {0} not found. Check database query. | Used for Record Group of type Query . If both
the RecordGroupColumnRow and the query was given, then this
error is returned if the rows returned by the query and the RecordGroupColumnRow
elements do not match. This could be caused by an invalid query. The Rows
do not need to be in the XML, but may be from a dump. |
No database connection, Record Group Column {0} not found. |
Similar to the above error but this is returned when there
is no database connection and the XML contains RecordGroupColumnRows
dependent on a Query . |
Subclassing error: Check that your FORMS_PATH contains all parent modules. | A parent module could not be found on the FORMS_PATH . |
Could not find existing sub-object {0} on owner {1} | Output when subclassed sub-object {0} could not be found on owner {1} which has already been subclassed from another object. This will occur if the XML was invalid regarding the sub-object, or if the parent module could not be found. |
Unable to find class {0} | The specified class name is not valid. This error should not occur because of the introduction of the Forms XML Schema. |
File {0} already exists. Use argument OVERWRITE=YES to replace. | An attempt was made to overwrite a file that already exists. To replace the existing file, use the option OVERWRITE=YES. |
ERROR on graphics {0} - cannot find image file {1} | The given graphics object is of type image
and the file name specified in the XML cannot be found. |
ERROR - an exception has been encountered: null | An attempt was made when trying to convert XML to FMB when a form-level property class is present. When reusing property classes, first create a new FormModule and property class within it. Then, set the subclass information on the newly created Property Class. |
Using the Forms to XML Conversion Tool
Using the XML to Forms Conversion Tool
Using the Schema Generator Tool