[jira] Commented: (GERONIMO-1824) geronimo-config-1.0.xsd incorrectly documents that classes can be comma-separated inside a filter element

["David Jencks (JIRA)" <de...@geronimo.apache.org>]

    [ http://issues.apache.org/jira/browse/GERONIMO-1824?page=comments#action_12374258 ] 

David Jencks commented on GERONIMO-1824:
----------------------------------------

I think we should not allow comma-separated filters, but require

  <hidden-classes>
    <filter>com.acme.producta</filter>
    <filter>com.acme.productb</filter>
  </hidden-classes>


> geronimo-config-1.0.xsd incorrectly documents that classes can be comma-separated inside 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
>     Assignee: 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".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira