You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ivan (JIRA)" <ji...@apache.org> on 2011/03/01 02:20:36 UTC

[jira] Commented: (GERONIMO-5836) Identify migration differences from 2.x to 3.0

    [ https://issues.apache.org/jira/browse/GERONIMO-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000647#comment-13000647 ] 

Ivan commented on GERONIMO-5836:
--------------------------------

For the classloading options,
a. hidden-classes. Now the deployment codes will covert the old hidden-classes configuration to the new import-package style.
<hidden-classes>javax.faces</hidden-classes> would be <import-package>!javax.faces</import-package>. 
b. non-overridable-classes, no support now, do not see a possible way in OSGi environment.
c. private-classes, think that all the packages are private if they are not exported. Might support once we have rules for what packages would be exported.
d. inverse-classloading, no support now, one possible way is to move all the import packages to dynamicImport-packages, but that would be issue for split-packages and BundleClassLoader cache.

> Identify migration differences from 2.x to 3.0
> ----------------------------------------------
>
>                 Key: GERONIMO-5836
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5836
>             Project: Geronimo
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>    Affects Versions: 3.0
>            Reporter: Chi Runhua
>            Priority: Minor
>
> We need to identify the migration differences from 2.X to 3.0 and work out a piece of document for that.
> As far as I know that inverse-classloading doesn't work in 3.0. 
> There might be more, please update the JIRA if you find any.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira