XMLdriven

XMLdriven refers to software systems whose configuration, structure, or behavior is defined primarily through XML documents rather than through hard-coded logic. In an XMLdriven approach, runtime components read and interpret XML files to assemble objects, configure services, or drive workflows.

Common contexts include application configuration (dependency wiring, feature flags), data transformation pipelines, and declarative user interfaces. An XML schema or DTD specifies allowed elements; a parser validates and builds a runtime representation, which a framework uses to instantiate components or perform actions. Example domains include build tools with XML-based project files, UI toolkits that describe layouts in XML, and integration platforms that define routing and transformations in XML.

Historical and current ecosystems with XML-driven configurations include Spring's XML bean definitions, Ant build files, and Android's layout XML. XSLT and other XML-based formalisms may also be used to transform or describe data pipelines.

Advantages of XMLdriven systems include a clear separation of configuration from code, easier environment-specific customization, and the possibility for non-developers to adjust settings without recompiling. Drawbacks include parsing overhead, verbose syntax, maintenance challenges with large configurations, potential for schema drift, and security considerations when processing untrusted XML.

Related concepts include XML configuration, declarative programming, and configuration management. As with other declarative approaches, XMLdriven designs emphasize describing desired outcomes rather than implementing step-by-step logic.