I also seems that you can't get round it. As it uses the composite file name to identify the directory to look in. Adding a directory path in front of the file name will have no effect as it just removes the directory path as well when constructing the root directory to start looking in so you end up picking up everything again.
The other alternative would be to use the 3 parameter API but in this case the location only seems to come into play if you specify an absolute path, i.e. file:/my/test/dir etc. Not ideal in our testing environment So, it's always difficult to reverse engineer the original intention by looking at the code but I expect it's to do with making sure that the system knows about everything you might inlude from your composite file. I'm sure Luciano wrote some pages about this kind of thing but I can't find them. I think we should make the default domain just load what you have asked it to load. I note that Sebastien is proposing to do some on-demand contribution code so I'm not going to dive into the code and start changing things just at the moment. I've worked round this for the time being by putting everything I need in a single composite file and making sure that works. Simon
