[DIGESTER-28] [digester] Default ClassLoader policy unusable in EAR archive

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6
• Fix Version/s: 3.0

Environment

Operating System: other
Platform: Other

• Bugzilla Id: 36387
• Assignee: Simone Tripodi
• Reporter: Craig Miller
• Created: 27/Aug/05 04:42
• Updated: 06/Jul/11 11:52
• Resolved: 26/Jun/11 17:27

Description

When used in an EAR archive the Digester default classloading/resource loading
implementation makes many major frameworks unusable. For Example, if I use
Struts/Tiles (uses digester) in Web App war files and use Digester from any EJB
component library or in the EAR classloader space either the Tiles definitions
cannot be loaded or other classes cannot be found. This is because Digester by
default sets useContextClassloader = false. Since most users and frameworks
(Struts, Tiles, JSF, etc) do not set useContextClassloader = true, Digester
essentially breaks enterprise Applications where the Digester is used from more
than one module. Note that end users do not control the uses of Digester, the
default useContextClassloader policy should = true.

Patch by changing:

useContextClassloader = false

to:

useContextClassloader = true

//
This solves the problem - which Google turns up endless hits.