incubator-wink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] Commented: (WINK-226) need fallback for Class.forName in J2EE environments
Date Wed, 04 Nov 2009 21:41:32 GMT


Hudson commented on WINK-226:

Integrated in Wink-Trunk-JDK1.5 #237 (See [])
    : need fallback for Class.forName in J2EE environments

> need fallback for Class.forName in J2EE environments
> ----------------------------------------------------
>                 Key: WINK-226
>                 URL:
>             Project: Wink
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.1
>            Reporter: Mike Rheinheimer
>             Fix For: 1.1
>         Attachments: WINK-226.patch
> In J2EE environments, the Wink libraries may be managed by a different classloader (A)
than the Application subclass (B).  In these cases, (A) needs to load (B) by way of Class.forName(B).
 However, due to the J2EE environment, and classloader hierarchies, (A) does not have visibility
into (B).
> The solution is to use the thread context classloader instead of Class.forName, which
uses the system classloader.  This "try thread context classloader first, then fallback to
system classloader" functionality is built into org.apache.commons.lang.ClassUtils.getClass(String).
 We already have a dependency on Apache commons in wink-server, so I figure we can just use

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

View raw message