[jira] Updated: (JELLY-44) [jelly] ClassLoader Problems with XMLParser and XMLParser reuse

[ji...@codehaus.org]

The following issue has been updated:

    Updater: Morgan Delagrange (mailto:mdelagra@yahoo.com)
       Date: Thu, 4 Sep 2003 4:18 PM
    Changes:
             timeoriginalestimate changed from 0
             timeestimate changed from 0 minutes
             Component changed to core / taglib.core
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=JELLY-44&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=JELLY-44


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JELLY-44
    Summary: [jelly] ClassLoader Problems with XMLParser and XMLParser reuse
       Type: Bug

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

    Project: jelly
 Components: 
             core / taglib.core

   Assignee: 
   Reporter: Vincenz Braun

    Created: Thu, 20 Mar 2003 1:48 PM
    Updated: Thu, 4 Sep 2003 4:18 PM

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

----
the use of the thread instance parser was changed in HEAD


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira