Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: error (herse.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <67FA1FDB-756B-4710-8C0F-2BCDC8599C4E@pobox.com>
References: <67FA1FDB-756B-4710-8C0F-2BCDC8599C4E@pobox.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4266DF39-2E64-4807-A0B2-E6BC6BE49570@uiuc.edu>
Content-Transfer-Encoding: 7bit
From: Naveen Neelakantam <neelakan@uiuc.edu>
Subject: Re: [drlvm] The Return of the Hidden Classloader, Part II
Date: Wed, 7 Feb 2007 02:00:20 -0600
To: dev@harmony.apache.org


On Feb 6, 2007, at 10:18 PM, Geir Magnusson Jr. wrote:

> This is an oldie but goodie..
>
> We never solved the problem of how to hide non java*. packages that  
> are on the boot classpath from apps.  We talked about a few  
> possibilities :
>
> 1) repackage them to a different package namespace
>
> 2) have a "hidden" classloader that only the system classloader can  
> use.
>
> I like #2.  Has anyone looked into this or made any progress?  Do  
> people think this is as important as I do?\]

I like #2 also, but I haven't thought about what it would take to  
implement.

>
> geir
>