atom feed17 messages in org.apache.struts.dev[PROPOSAL] XMLMessageResources
FromSent OnAttachments
mart...@tumbleweed.comOct 10, 2001 11:07 pm 
James HolmesOct 11, 2001 3:46 am 
Young, WayneOct 11, 2001 5:32 am 
Curt HagenlocherOct 11, 2001 6:31 am 
SCHACHTER,MICHAEL (HP-NewJersey,ex2)Oct 11, 2001 9:11 am 
Craig R. McClanahanOct 11, 2001 10:35 am 
mart...@tumbleweed.comOct 11, 2001 11:09 am 
mart...@tumbleweed.comOct 11, 2001 11:25 am 
Craig R. McClanahanOct 11, 2001 1:37 pm 
Ted HustedOct 13, 2001 2:58 am 
James HolmesOct 13, 2001 4:29 pm 
mart...@tumbleweed.comOct 13, 2001 9:33 pm 
mart...@tumbleweed.comOct 13, 2001 9:57 pm 
Ted HustedOct 14, 2001 2:26 am 
James HolmesOct 15, 2001 6:17 am 
Petr JirickaOct 16, 2001 5:30 am 
mart...@tumbleweed.comOct 16, 2001 3:14 pm 
Subject:[PROPOSAL] XMLMessageResources
From:mart...@tumbleweed.com (mart@tumbleweed.com)
Date:Oct 10, 2001 11:07:58 pm
List:org.apache.struts.dev

The Struts 1.1 TODO list contains the following item:

"XmlMessageResources. Implementation of MessageResources and MessageResourcesFactory that loads message keys and strings from one or more XML resources or files."

I have an implementation of this which I would like to contribute to Struts. The implementation is a drop-in replacement for the existing PropertyMessageResources. In fact, it is derived from it, and so shares the same file naming scheme for locale-specific messages.

Here's a simple example of what an XML message file would look like:

---------- begin example ---------- <?xml version="1.0" encoding="ISO-8859-1"?>

<messages> <message key="validation.username.required">You must enter a username</message> <message key="validation.password.required">You must enter a password</message> <message key="validation.password.match">Confirmation password does not match</message> </messages> ---------- end example ----------

The first line of the example provides a hint as to why I did not attempt to incorporate messages for more than one locale into a single XML file. Messages for different locales may well be specified using different character encodings. In addition, maintaining the messages from each locale in a different XML file avoids loading locales unnecessarily.

To use this implementation, all that is required is to specify the 'factory' init-param in your web.xml file, and to make sure that the 'application' init-param refers to an XML resource.

What do people think about incorporating this into the Struts 1.1 code base?