Noel, there's a lot a like about this approach. You have the convience class 'XMLResources' that hides a lot of the heavy lifting, and makes the client's task easy.
As i noted before in the ListManager proposal, anything to get the custom resources out of the class path, and into an adminstratively editable place was crucial to making the listManager useful. Also, i really like the 'overloading' concept of the 'for' attribute in regards to the matcher. That provides a nice way to customize the resources on a per group basis. The only thing that i don't like, is mixing in actual content (the CDATA) into the xml. It's not that i object to the location of the CDATA, it just makes for some ugly looking xml. It's really just a minor nit, and at this point, the positives far outweigh the negatives. Nice work. How do you want to proceed with this improvement? -----Original Message----- From: Noel J. Bergman [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 8:17 PM To: James Developers List Subject: RE: XMLResources and demo mailet > I haven't gotten the responses.properties table in there They are present in the revision attached. My expectation is that the groups would be used to organize messages for each command, and the "for" matching would be used to allow a particular mailing list to replace one or more message resources. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
