Re: Alternative E loader [patch]

On Feb 19, 2010, at 7:45 AM, Thomas Leonard wrote:

> On Thu, 2010-02-11 at 16:50 +0000, Thomas Leonard wrote:
>> Hi all,
>> 
>> The E documentation (e.g. the Walnut guide) suggests that .emaker files
>> should be placed somewhere in classpath and then imported using
>> <import:mypackage.myMaker>.
>> 
>> If I want to depend on someone else's library then presumably I'm
>> supposed to add their jar or directory to my classpath. However:
>> 
>> - The classpath is a global (process-wide) namespace, so their emakers
>> may override or conflict with existing ones.
>> 
>> - Their jar may also introduce other files that affect the whole process
>> (e.g. .safej files, giving their emakers access to unsafe Java code).
>> 
>> - I have to mess around with extra -cpa options in the launcher scripts
>> (which always has to be duplicated, to support Linux and Windows).
>> 
>> - I can't add extra modules at runtime.
>> 
>> - I can't depend on two libraries that use the same class names (e.g.
>> two different versions of the same library).
Have you looked at OSGi?  Are you using OSGi in your solution?

John