Re: [Agavi-Dev] Move autoload.xml loading to bootstrap()

Thu, 14 Jan 2010 12:07:01 -0800

The first config compilation triggers the compilation of config_handlers.xml (which is done through a static mapping for the config handler definition). After that, autoload.xml is compiled, then settings.xml. The settings.xml compilation might depend on autoloads (e.g. for the assigned config handler). I'd rather not change that order... 

On 14.01.2010, at 18:28, Mike Seth wrote:


David Zülke wrote:

http://pastie.org/770456

Any objections?


Perhaps it would be better to do this *after* settings.xml and not  
before? Reading settings.xml would almost certainly yield
no runtime effects that need something out of the autoload list to  
be loaded; on the other hand, autoload.xml may use configuration

values declared in settings.xml. I imagine this is conceivable:


<autoload name="Dogtrine">/tmp/argh/Dogtrine/ 
%org.rage.wtf.version_that_works_today%/Dogtrine.class.php</autoload>


_______________________________________________
Agavi Dev Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/dev






Attachment:
smime.p7s

Description: S/MIME cryptographic signature


_______________________________________________
Agavi Dev Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/dev






















					Reply via email to