You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rick McGuire (JIRA)" <ji...@apache.org> on 2010/05/27 12:24:37 UTC

[jira] Updated: (GERONIMO-4992) Tomcat StandardContext use of Class.forName(className) doesn't work well in osgi

     [ https://issues.apache.org/jira/browse/GERONIMO-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick McGuire updated GERONIMO-4992:
-----------------------------------

    Fix Version/s: 3.0-M1
                       (was: 3.0)

> Tomcat StandardContext use of Class.forName(className) doesn't work well in osgi
> --------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4992
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4992
>             Project: Geronimo
>          Issue Type: Sub-task
>      Security Level: public(Regular issues) 
>          Components: osgi, Tomcat
>    Affects Versions: 3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0-M1
>
>
> Tomcat 7's StandardContext.createWrapper() method uses a lot of Class.forName(fooName).  This doesn't work for us since some of the listeners are in the geronimo-tomcat7 bundle, not tomcat itself.
> Using the InstanceManager works fine for us.  I've overridden the method in GeronimoStandardContext.  We should talk to tomcat about fixing this in tomcat itslef.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.