Thank you for the response!
If I understand correctly, the idea would be to create an Enum model of each list, with the Enum elements being the keys used to fetch the localized string from the XML?
I do like this as an option if there were a small number of fairly short lists; however, if there are many & larger lists, then having to create an Enum with all the elements mapped per list, seems like it could get tedious. Ideally, we'd want a dev to be able to receive the XML from a BA, plug it in, and then be able to use the resources directly.
I was hoping there was some way to mark a list within the XML itself and have the resource manager pick out text by parent-list name; it doesn't look like that's currently possible though.
One alternative might be to have separate Localization Sources for each list, but to do this and still have a plug-and-play approach for the resource files, I could, for instance, loop through all resource-bearing folders in my app's "/localization" directory, using the folder names as source names. In this way, I could receive a "ListICD9" folder with localized XML files therein, add this to my "/localization" directory, and be able to retrieve the list values by calling the "ListICD9" source.
Do you think this approach would be workable?
