Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <437E6EAC.3090802@apache.org>
Date: Fri, 18 Nov 2005 17:15:40 -0700
From: Jeff Genender <jgenender@apache.org>
Reply-To: jgenender@apache.org
Organization: Apache Geronimo
User-Agent: Thunderbird 1.5 (Macintosh/20051025)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: Proposed changes to plan elements related to classloaders.
References: <8bc846c9aa3d3c8afe71c987aa0e7a13@yahoo.com>
 <437E6C46.2090204@apache.org> <7564d66dd224287bc449e842f65d0575@yahoo.com>
In-Reply-To: <7564d66dd224287bc449e842f65d0575@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Yes! ;-)

David Jencks wrote:
> 
> On Nov 18, 2005, at 4:05 PM, Jeff Genender wrote:
> 
>> There is a JIRA issue I re-opened on those classes tags.  They are 
>> duped in Tomcat and Jetty.  I would like to see them at the web 
>> builder level.
> 
> I noticed they were missing from the generic schema.  My local changes 
> use the same group everywhere including web-builder, so this would fix 
> your issue?
> 
> thanks
> david jencks
> 
>>
>> David Jencks wrote:
>>> It's become apparent recently that some of the elements in our plans 
>>> related to classloading are a bit confusing.  In particular, there is 
>>> an include element that no one is sure what is for and is not used, 
>>> and a similarly named import element that is like the parentId, only 
>>> better :-).  Also the lists of special classes for the classloader 
>>> are in between the import and dependency elements.
>>> I'd like to change the schema for all plans to use this:
>>>     <xs:group name="classloader-infoGroup">
>>>         <xs:sequence>
>>>             <xs:element ref="sys:parent" minOccurs="0" 
>>> maxOccurs="unbounded"/>
>>>             <!--            <xs:element name="include" 
>>> type="sys:dependencyType" minOccurs="0" maxOccurs="unbounded"/>-->
>>>             <xs:element ref="sys:dependency" minOccurs="0" 
>>> maxOccurs="unbounded"/>
>>>             <xs:element ref="sys:hidden-classes" minOccurs="0" 
>>> maxOccurs="unbounded"/>
>>>             <xs:element ref="sys:non-overridable-classes" 
>>> minOccurs="0" maxOccurs="unbounded"/>
>>>         </xs:sequence>
>>>     </xs:group>
>>> The differences are that:
>>> import is renamed parent.  This seems less confusing to me.  I can 
>>> support backwards compatibility in most plans, although perhaps not 
>>> plain gbean plans.
>>> include is removed.
>>> the class lists are moved to the end.  This makes more sense to me, 
>>> in that first we have the info on what goes into the current 
>>> classloader in the way of parents and contents, and then we have the 
>>> modifications to that list.
>>> Comments?
>>> thanks
>>> david jencks
>>