Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

System Messages

To change system messages

The file at the root of the project will need to be edited. This file is referenced by the class. This class contains a list of public static final Strings which form the keys. These keys are used in the code to reference a system message. The values for these keys are the keys of the file.

If the String value that is used in the code is known, the error message can be found by finding the line in that contains that String. The key which matches the value of the String can then be found in the file and the value of the system message changed there.

If the text of the message is known, then the process may be simpler. Find the line in that has the value of the system message desired. Make any changes necessary. (Note: many system messages contain replacement parameters from java.text.MessageFormat.)


Here is an example of how the can be used to add an error to the global error map.

In this example, the KFSKeyConstants.ERROR_DV_BANK_ROUTING_NUMBER parameter is passed in as the key that will be used to reference the associated error message in

Note: See Validation and Error Handling 2#Adding Error Messages for additional information regarding adding error messages to the error map.


You may wish to verify that you have changed the correct line, since it is possible for there to be duplicate instances of the same message listed under different keys.

To add a new message

Add the appropriate values to and files. (See above for details) Cite the new message using the line

Note: <KeyString> is the key defined in the file.

The property.files key in the file controls this behavior. It accepts a comma delimited list of URL's that are used by Spring's Resource loader. This format has a special protocol of classpath for resources that are on the classpath (See the javadoc for The remainder of the URL being the relative location with respect to the classpath. Use the file protocol for resources that are on the file system, but not on the classpath. Changing or adding to the value of this key will change where Kuali looks for these properties. See rfc3986 for details on URL's.

Struts Messages

The struts.message.resources value in the file is used to define a comma delimited list of properties files that contain messages that struts can provide to jsp tags. The items in this list implement the java.util.PropertyResourceBundle convention. The usual value is located in and so struts (in version 1.x, this behavior is changed slightly in version 2.x) will use the file to find message Strings. To change the message, modify the String value in for the appropriate key.

The key is determined by inspecting the jsp tag. For example:


In this code excerpt

the keys in this html statement are '' and ''.

As before, if the message is known, may be searched and directly modified.


The same caveats for KeyConstants apply: messages may contain java.text.MessageFormat placeholders and therefore, there may be duplicate messages.

To create a new message, add an appropriate entry in and use it in the jsp tag as shown below:

Unable to render {include} The included page could not be found.
  • No labels