[JELLY-180] ClassLoader Problems with XMLParser and XMLParser reuse

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: core / taglib.core
• Assignee: Unassigned
• Reporter: dion gillard
• Created: 04/Jan/05 16:13
• Updated: 12/Nov/08 09:55

Description

– Moved from bugzilla issue 17619 –

Hello,

i had problems integrating jelly because of the ClassLoader set to the
JellyContext is not promoted to the XMLParser. That leads to
ClassNotFoundExceptions in resolving custom TagLibs. This should be added in
JellyContext compileScript methods.

The use of XMLParser in JellyContext needs a little more documentation not
only because of
a new XMLParser is always instantiated in compileScript(String uri) and
compileScript(URL url) uses the per thread instance. Is it ok that the
ImportTag therefore indirectly uses the same thread instance parser?