Allow the ability to load/parse externalized XML configs

Description

I've read the google groups and there doesn't seem to be many ppl asking for this - mainly because the use cases don't seem to be there. However, externalized XML config files are useful in the enterprise where automated systems (like a build system) need to modify aspects of the code without compilation. Some use cases include: inserting build numbers, providing dynamic content (integrated at build time), and the ability to automatically switch to backup servers when the main server goes down.

As an avid user of Swiz, I personally see this feature as the one reason why anyone would flock to Parsley or SpringAS over Swiz in their current releases.

Environment

None

Status

Assignee

ChrisC

Reporter

Duncan W.

Labels

None

Affects versions

Priority

Minor
Configure