Java XML Parser Messages

Java XML Parser Messages 1-81

Note: When Java XML parser messages are listed in the user log (ULOG), the messages have the prefix IJXML_CAT. For example, message 1 is listed as IJXML_CAT:1.

1	"INFO: 1 warning"
	Description	There was one warning during the execution of buildjavaserver. The warning was reported in a previous message.
	Action	None.

2	"INFO: {1} warnings"
	Description	There were multiple warnings during the execution of buildjavaserver. The warnings were reported in previous messages. The {1} value is replaced with the number of warnings.
	Action	None.

3	"INFO: 1 error"
	Description	There was one error during the execution of buildjavaserver. The error was reported in a previous message. No output files were generated.
	Action	Fix the error and execute buildjavaserver again.

4	"INFO: 1 error, 1 warning"
	Description	There was one error and one warning during the execution of buildjavaserver. The error and the warning were reported in a previous message. No output files were generated.
	Action	Fix the error and execute buildjavaserver again.

5	"INFO: 1 error, {1} warnings"
	Description	There was one error and multiple warnings during the execution of buildjavaserver. The error and the warnings were reported in a previous message. No output files were generated. The {1} value is replaced with the number of warnings.
	Action	Fix the error and execute buildjavaserver again.

6	"INFO: {0} errors"
	Description	There were multiple errors during the execution of buildjavaserver. The errors were reported in a previous message. No output files were generated. The {0} value is replaced by the number of errors.
	Action	Fix the errors and execute buildjavaserver again.

7	"INFO: {0} errors, 1 warning"
	Description	There were multiple errors and one warning during the execution of buildjavaserver. The errors and the warning were reported in a previous message. No output files were generated. The {0} value is replaced with the number of errors.
	Action	Fix the errors and execute buildjavaserver again.

8	"INFO: {0} errors, {1} warnings"
	Description	There were multiple errors and multiple warnings during the execution of buildjavaserver. The errors and the warnings were reported in a previous message. No output files were generated. The {0} value is replaced with the number of errors. The {1} value is replaced with the number of warnings.
	Action	Fix the errors and execute buildjavaserver again.

9	"ERROR: Missing argument to -s option"
	Description	The -s option to buildjavaserver must be followed by a search path similar to a Java class path. This argument was not specified on the command line.
	Action	Add the search path argument to the command line and run buildjavaserver again.

10	"ERROR: Invalid option {0}"
	Description	An invalid option was passed to buildjavaserver.
	Action	See the Java Programming Reference for the list of valid options to buildjavaserver, fix the command line, and run the command again.

11	"ERROR: Missing input file argument"
	Description	The last command line argument to buildjavaserver must be the name of an XML input file. That name is missing.
	Action	Add the input file name argument to the command line and run buildjavaserver again.

12	"ERROR: Cannot open {0}"
	Description	The XML input file {0} could not be opened for reading. No output file will be generated.
	Action	Make sure the input file {0} exists and is readable.

13	"ERROR: Unexpected EOF"
	Description	The XML parser reached the end of file unexpectedly. No output file will be generated.
	Action	Fix the XML syntax of the input file.

14	"ERROR: Unexpected {0}"
	Description	The XML parser found an unexpected token in the source. The {0} value is replaced by the token. Depending on the situation, parsing will continue after reporting the error or will stop immediately. In any case, no output file will be generated.
	Action	Fix the XML syntax of the input file.

15	"ERROR: I/O Error"
	Description	An I/O error occurred reading the XML input file. This is a fatal error. No more processing is attempted. No output file will be generated.
	Action	Check the XML input file for read access, bad blocks, locks, and so forth.

16	"WARNING: Illegal -- in comment"
	Description	It is illegal to have a double dash (--) in an XML comment, except to introduce the end of comment -->.
	Action	This is a warning. However, the comment should be fixed, because other XML parsers could reject the input.

17	"ERROR: End of file in comment"
	Description	The end of file was reached in a comment.
	Action	Look for any nonterminated comments in the input file.

18	"ERROR: Invalid character sequence <!-{0}"
	Description	The character {0} is not valid after <!-. The XML parser for buildjavaserver only supports <!-- to start comments.
	Action	Fix the XML syntax of the input file.

19	"ERROR: Unexpected character {0} after <!{1}"
	Description	A non-white-space character is present after <!{1}. The {1} value can be either ENTITY or DOCTYPE.
	Action	Fix the XML syntax of the input file.

20	"ERROR: Unsupported keyword {0}"
	Description	A <! is followed by a keyword that was neither ENTITY nor DOCTYPE. The {0} value is replaced with the offending keyword.
	Action	Fix the XML syntax of the input file.

21	"ERROR: Unsupported processing instruction {0}"
	Description	A <? can be followed only by xml. The {0} value is replaced with the three characters at the beginning of the offending word.
	Action	Fix the XML syntax of the input file.

22	"ERROR: Unexpected {0} after </"
	Description	An invalid character (such as a white-space character) follows </.
	Action	Fix the XML syntax of the input file.

23	"ERROR: Unexpected {0} after </{1}"
	Description	An element closing tag must end with >. An invalid character (such as a white-space character) follows </{1}. The {1} value is replaced with the keyword in the closing tag.
	Action	Fix the XML syntax of the input file.

24	"ERROR: Unexpected </{0}> closing tag"
	Description	The {0} value is an unknown element tag.
	Action	Fix the XML syntax of the input file.

25	"ERROR: Unexpected {0} after <"
	Description	An invalid character (such as a white-space character) follows a <. The {0} value is replaced with the offending character.
	Action	Fix the XML syntax of the input file.

26	"ERROR: Unexpected <{0}> element"
	Description	The {0} value is an unknown element tag.
	Action	Fix the XML syntax of the input file.

27	"ERROR: Unexpected {0} after ?"
	Description	The {0} value is an invalid character after the question mark character (?). Only > can follow a ?.
	Action	Fix the XML syntax of the input file.

28	"ERROR: Unexpected {0} after /"
	Description	The {0} value is an invalid character after /. Only > can follow a /, except in an element closing tag.
	Action	Fix the XML syntax of the input file.

29	"ERROR: Missing XML declaration"
	Description	Every XML document must begin with an XML declaration <?xml version="1.0"?>.
	Action	Fix the XML syntax of the input file.

30	"ERROR: Unexpected {0} in XML declaration"
	Description	Only the version declaration is valid in the XML declaration. The {0} value is replaced with the offending declaration keyword.
	Action	Fix the XML syntax of the input file.

31	"ERROR: Missing = after version in XML declaration"
	Description	The version declaration must be followed by the = sign in the XML declaration.
	Action	Fix the XML syntax of the input file.

32	"ERROR: Only supported version of XML is 1.0"
	Description	The only version recognized by the XML parser is 1.0.
	Action	Fix the XML syntax of the input file.

33	"ERROR: Missing end of XML declaration"
	Description	The ?> is missing at the end of the XML declaration.
	Action	Fix the XML syntax of the input file.

34	"ERROR: Invalid value {0} for {1}"
	Description	Value {0} is invalid for attribute or entity {1}.
	Action	Fix the XML syntax of the input file.

35	"ERROR: Cannot load class {0}"
	Description	buildjavaserver failed to load class {0}.
	Action	Make sure class {0} can be reached from the CLASSPATH or from the search path specified with the -s option to buildjavaserver.

36	"ERROR: Unexpected ENTITY definition {0}"
	Description	The only two entities that can be redefined in the internal subset are transaction_policy and activation_policy. The {0} value is replaced with the unexpected ENTITY name.
	Action	Fix the XML syntax of the input file.

37	"ERROR: Unexpected {0} in internal subset"
	Description	Only entities can be redefined in the internal subset. The {0} value is the start of a nonentity definition.
	Action	Fix the XML syntax of the input file.

38	"WARNING: Missing DOCTYPE. Assuming M3-SERVER"
	Description	No <!DOCTYPE declaration was specified in the XML file. buildjavaserver assumes that the document is of type M3-SERVER.
	Action	None.

39	"ERROR: Only supported document type is M3-SERVER"
	Description	When specifying a DOCTYPE declaration in the XML file, the document type must be M3-SERVER.
	Action	Fix the XML syntax of the input file.

40	"ERROR: Expected SYSTEM after M3-SERVER"
	Description	The M3-SERVER DTD has no URL. The DOCTYPE declaration must always use the SYSTEM identifier.
	Action	Fix the XML syntax of the input file.

41	"ERROR: Expected "m3.dtd" after SYSTEM"
	Description	The string after SYSTEM in the DOCTYPE must be "m3.dtd".
	Action	Fix the XML syntax of the input file.

42	"ERROR: Unexpected {0} at end of DOCTYPE"
	Description	The DOCTYPE declaration must end with >. The {0} value is replaced with the offending character.
	Action	Fix the XML syntax of the input file.

43	"ERROR: Expected <M3-SERVER> tag instead of {0}"
	Description	The document tag must be M3-SERVER. The {0} value is replaced with the name of the offending tag.
	Action	Fix the XML syntax of the input file.

44	"ERROR: Cannot find directory for {0}"
	Description	The absolute pathname for file. The {0} value cannot be retrieved.
	Action	Make sure there are no access restrictions for the current user on the directory.

45	"ERROR: Invalid attribute {0} in <{1}>"
	Description	The attribute name {0} is invalid for element {1}.
	Action	Fix the XML syntax of the input file.

46	"ERROR: Unexpected {0} in <{1}>"
	Description	The token {0} is unexpected in element {1}.
	Action	Fix the XML syntax of the input file.

47	"ERROR: The <ARCHIVE> tag must appear last in <M3-SERVER>"
	Description	If the <ARCHIVE> element is specified in an XML input file, the element must be the last one inside an <M3-SERVER> element.
	Action	Move the archive element to the end of the <M3-SERVER> element.

48	"ERROR: Only one <ARCHIVE> tag allowed in <M3-SERVER>"
	Description	Only one archive element is allowed inside an <M3-SERVER> element.
	Action	Remove the duplicate archive element.

49	"ERROR: Unexpected {0} in <M3-SERVER>"
	Description	The element {0} is invalid in an <M3-SERVER> element.
	Action	Fix the XML syntax of the input file.

50	"WARNING: No server-implementation in <M3-SERVER>. Defaulting to 'com.beasys.Tobj.Server'"
	Description	If no server-implementation attribute is present in the <M3-SERVER> element, buildjavaserver defaults to com.beasys.Tobj.Server.
	Action	None.

51	"WARNING: No server-descriptor-name in <M3-SERVER>. Defaulting to Server.ser"
	Description	If no server-descriptor-name attribute is present in the <M3-SERVER> element, buildjavaserver defaults to Server.ser.
	Action	None.

52	"ERROR: Cannot create file {0}"
	Description	The file {0} cannot be created. The file is either the server descriptor or a temporary file created when preparing the archive.
	Action	Make sure there is no permission problem that may inhibit the creation of the file (such as an existing read-only file already in the same directory), and that the file system is not out of resources.

53	"ERROR: Multiple occurrences of {0} in <{1}>"
	Description	There is more than one occurrence of attribute {0} in element {1}.
	Action	Remove extra occurrence(s).

55	"ERROR: Missing attribute {0} in <{1}>"
	Description	There is no occurrence of the required attribute {0} in element {1}.
	Action	Add the missing attribute.

56	"ERROR: Redefinition of {0}"
	Description	The {0} value is being redefined as a different object. For instance, it was initially defined as a module, and it is now defined as in implementation, and vice versa.
	Action	Remove the extraneous definition.

57	"WARNING: <MODULE> {0} is empty"
	Description	Module {0} does not contain any implementations and could be removed from the XML file.
	Action	None.

58	"ERROR: Unexpected {0} at end of <{1}>"
	Description	This message is generated if a module or an archive definition does not end with the matching closing tag (for example, </ARCHIVE> for an archive). This message is also generated if an implementation element definition that does not end with /> (that is, as an empty tag) is not followed immediately with an implementation closing tag </IMPLEMENTATION>.
	Action	Fix the XML syntax of the input file.

60	"WARNING: File {0} already in archive {1} as {2}. Ignoring duplicate"
	Description	The file {0} is already in the archive {1}, coming from {2}, where {2} is either a full path name or a name inside a ZIP or JAR archive. The redefinition is ignored.
	Action	None.

61	"ERROR: Cannot find class file for {0}"
	Description	The class file for class {0} cannot be found on the search path.
	Action	Make sure the search path is correct. Check that the class name is correct.

62	"ERROR: Directory {0} not found"
	Description	The directory {0} cannot be found. The {0} value is created by the concatenation of a prefix and a name in a <DIRECTORY> element.
	Action	Make sure there are no access restrictions for the current user on the directory and that the name is spelled correctly.

63	"ERROR: {0} is not a directory"
	Description	The {0} value is not a directory. The {0} value is created by the concatenation of a prefix and a name in a <DIRECTORY> element.
	Action	Make sure the name is spelled correctly.

64	"ERROR: File {0} not found"
	Description	The file {0} cannot be found. The {0} value is created by the concatenation of a prefix and a name in a <FILE> element.
	Action	Make sure there are no access restrictions for the current user on the file and that the file name is spelled correctly.

65	"ERROR: {0} is not a regular file"
	Description	The {0} value is not a regular file. The {0} value is created by the concatenation of a prefix and a name in a <FILE> element.
	Action	Make sure the file name is spelled correctly.

66	"ERROR: Package {0} not found"
	Description	No class files could be found in Java package {0}. The {0} value comes from a <PACKAGE> or a <PACKAGE-RECURSIVE> element.
	Action	Make sure the class files for the packages can be found on the search path and that the package name is spelled correctly.

67	"ERROR: No classes in anonymous package"
	Description	No class files could be found for the anonymous package (that is, classes whose source file does not include a package statement). This message is generated when processing the <PACKAGE-ANONYMOUS> element.
	Action	Make sure the class files can be found on the search path.

68	"ERROR: Directory ''{0}'' exists already"
	Description	The directory {0} should be used to prepare the creation of the archive, but the name already exists in the file system.
	Action	The existing directory must be removed or renamed. Alternatively, buildjavaserver can be executed from another directory that does not contain an entry by that name.

69	"ERROR: Cannot create directory {0}"
	Description	The {0} value is the name of a directory that is created when preparing the creation of the archive. The directory cannot be created.
	Action	Make sure there are no access restrictions on the directory for the current user and that the file system is not out of resources.

70	"ERROR: {0} exists and is not a directory"
	Description	The directory {0} is created when preparing the creation of the archive. Another file by that name has already been created, and the directory cannot be created.
	Action	Check the directory and the file name.

71	"ERROR: Cannot copy {0} to {1}"
	Description	The file {0} cannot be copied to {1} when preparing the creation of the archive. The {0} value is either an absolute file name or an entry in a ZIP or JAR archive.
	Action	Make sure there are no access restrictions on {0}and that the file system is not out of resources.

72	"ERROR: Cannot change to directory {0}"
	Description	buildjavaserver cannot set the current directory to {0}.
	Action	Check that there are no permission problems on the directory. Also make sure that the umask is not too restrictive when creating directories.

73	"ERROR: Cannot create archive {0}"
	Description	The execution of the jar command failed.The messages issued by the jar command provide more information.
	Action	Depends on the information given by the jar command. For information on the jar command, refer to the online documentation included with JDK 1.2 and the Java Programming Reference.

74	"WARNING: Cannot remove {0}"
	Description	The temporary file {0} cannot be removed.
	Action	Remove the leftover files after the buildjavaserver command completes.

75	"ERROR: Cannot write {0}"
	Description	There is an I/O error when the system attempts to write to temporary file {0}.
	Action	Check that there are sufficient resources in the file system.

76	"ERROR: Cannot open {0}"
	Description	The file {0} cannot be opened for reading.
	Action	Make sure the current user has read permission on the file.

77	"ERROR: Empty value for attribute {0}"
	Description	The value for attribute {0} is an empty string.
	Action	Add a valid value for the attribute.

78	"ERROR: Invalid value {0} for attribute {1}"
	Description	The value {0} is not valid for attribute {1}. Typically, the attribute should contain a Java class or a package name, and the name is not a valid dot-separated Java identifier.
	Action	Make sure the value is valid for the attribute.

79	"ERROR: Class {0} in server-implementation does not extend com.beasys.Tobj.Server"
	Description	The class whose name is specified in the server-implementation attribute of the <M3-SERVER> element must either derive from com.beasys.Tobj.Server or be the com.beasys.Tobj.Server class itself.
	Action	Check that the class name for the server-implementation attribute is correct. Make sure that the specified class extends com.beasys.Tobj.Server.

80	"ERROR: Class {0} in name is not a servant implementation"
	Description	The class {0} found in an implementation element does not derive from a skeleton generated by the m3idltojava compiler.
	Action	Make sure the base class for {0} is a valid skeleton.

81	"ERROR: ''implements'' value {0} does not match servant id {1}"
	Description	The implements attribute value {0} does not match the interface repository ID found in the implementation class being processed. The interface repository ID is actually part of the skeleton class used as the base class for the implementation class.
	Action	Make sure the interface repository ID is correct. Alternatively, the implements attribute can be omitted completely, in which case the value found in the implementation class will be used.