geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Sisson <jrsis...@gmail.com>
Subject Re: [jira] Created: (GERONIMO-1824) geronimo-config-1.0.xsd incorrectly documents that classes can be comma-separated inside a a filter element
Date Tue, 11 Apr 2006 00:49:45 GMT
Should we just update the documentation in the schema to reflect the 
code?  Should we be avoiding having XML elements that require further 
parsing (e.g. for comma-separated values) so that other tools can 
process the XML easily?

John

John Sisson (JIRA) wrote:
> geronimo-config-1.0.xsd incorrectly documents that classes can be comma-separated inside
a a filter element
> -----------------------------------------------------------------------------------------------------------
>
>          Key: GERONIMO-1824
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1824
>      Project: Geronimo
>         Type: Bug
>     Security: public (Regular issues) 
>   Components: deployment, kernel  
>     Versions: 1.0    
>     Reporter: John Sisson
>     Priority: Minor
>      Fix For: 1.1
>
>
> The current implementation of MultiparentClassloader does not parse comma-separated values.
 Therefore if you specify a filter such as:
>
>   <hidden-classes>
>     <filter>com.acme.producta,com.acme.productb</filter>
>   </hidden-classes>
>
> Then when loading the class "com.acme.productb" it will not match the hidden-classes
filter as the MultiParentClassloader logic just does a simple name.startsWith(hiddenClasses[i])
test, where hiddenClasses[0] will be "com.acme.producta,com.acme.productb".
>
>
>   


Mime
View raw message