Hello Sven, that is not possible. XIncludes are resolved by DOM, and we have no control over the recursion, so we cannot nest into deeper-level XInclude declarations and expand the directives in those paths.
Note that XIncludes are supposed to support relative paths, so that might help in this situation - you could simply do ../../../libraries/ plugin/autoload.xml, that should work. If not, let us know. Also, mind you that you can use Agavi's parent config feature: <configurations xmlns="http://agavi.org/agavi/1.0/config"; parent="%app.global_libraries_dir%/plugin/autoload.xml" /> Hope that helps, David Am 11.07.2008 um 17:42 schrieb Sven Kretschmann: > Hi there, > > I just ran into a problem using agavi directives in xincluded > configuration files. To show my problem here's the sketch of the > configuration files setup > > app/config/autoload.xml xincludes > app/config/project/autoload.xml xincludes > libraries/plugin/autoload.xml > > The xinclude from the project autoload to the plugin autoload should > be done using the directive %app.global_libraries_dir%, defined in > the dispatcher file. > > Sadly, this leads to a "Failed build URL" error, as the xinclude > seems to recurse and try to follow the path %app.global_libraries_dir > %/plugin/autoload.xml. > The expansion of the directives is only done for config/autoload.xml. > > Is there any way to use these directives in xincluded files? Or does > XInclude itself prevent that? > > Greets, Sven > > _______________________________________________ > users mailing list > [email protected] > http://lists.agavi.org/mailman/listinfo/users > _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
