You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "dion gillard (JIRA)" <co...@jakarta.apache.org> on 2005/01/04 08:18:12 UTC

[jira] Created: (JELLY-180) ClassLoader Problems with XMLParser and XMLParser reuse

ClassLoader Problems with XMLParser and XMLParser reuse
-------------------------------------------------------

         Key: JELLY-180
         URL: http://issues.apache.org/jira/browse/JELLY-180
     Project: jelly
        Type: Bug
  Components: core / taglib.core  
    Reporter: dion gillard


-- 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?



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org