Colin, Fortress ultimately uses one configuration file. As Hamett suggests, entities are definitely one way to handle it. Another alternative would be to use a combination of Ant (concat task) or Maven, or a custom XML-configuration-merger based on the excalibur-configuration (unfortunately, currently deprecated) library to merge your configuration prior to starting Fortress.
Shash > Hello Colin, > I've used standard XML entities to split the configuration file. But > it requires that fortress set an entity resolver in the > ConfigurationBuilder > (IIRC). Probably the version available for download don't have this code. > Well, grab yours from SVN :-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
