Uploaded image for project: 'Commons Jelly'
  1. Commons Jelly
  2. JELLY-180

ClassLoader Problems with XMLParser and XMLParser reuse

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: core / taglib.core
    • Labels:
      None

      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?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              diongillard dion gillard
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: