[Eclipsedotnet-developers] AssemblyLoader mechanism improved

[<jpp...@gm...>]

Hi. Just to tell you that I just committed some changes I made to the
AssemblyLoader mechanism.

The changes I made are basically the following:

- the log files are written to a directory called Logs. Each execution of
the platform generates 2 new log files (for the Console.Out and
Console.Error streams), and the name of the files are "log_<day>_<time>_[Out
| Error].txt".

- I somewhat improved the AssemblyLoader mechanism:

	- Java.Lang.Loader is now called Java.Lang.LoaderRegistry (I think
this name is much more straightforward than the previous one)

	- DelegatingLoader now serves a purpose similar to Eclipse's
DelegatingURLClassLoader: to handle the plugin's requirements (i.e., plugin
imports). So, in a nutshell, DelegatingLoader handles plugin's requirements
(imported plugins, through the <requires> and <import> tags in the plugin
manifest), and PluginLoader handles plugin's runtime loading (assemblies
that should be loaded, through the <runtime> and <library> tags).

	- I removed some hacks I had previously introduced to make the
previous version work. Hopefully, this new version is (much) cleaner and
easier to understand.



This was also to start paving the way to using AppDomains in the platform,
although I still have a lot to read regarding this subject, as it can have
great effects on the platform.

Well, I'm tired and hungry. Going home :) .

Regards,
JS


P.S.: I will update the AssemblyLoader documentation in the pdf file when I
have the chance. Until so, feel free to email me with any questions.

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.13.12/194 - Release Date: 07-12-2005