After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 541938 - External loader per context
External loader per context
Status: RESOLVED OBSOLETE
Product: libxml2
Classification: Platform
Component: general
2.6.x
Other All
: Normal enhancement
: ---
Assigned To: Daniel Veillard
libxml QA maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-07 19:04 UTC by Wade Tregaskis
Modified: 2021-07-05 13:24 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Wade Tregaskis 2008-07-07 19:04:46 UTC 
xmlSetExternalEntityLoader poses a lot of practical issues for use.  There's the potential for conflict between two libraries, used by the same application, that both want to use their own loaders.  The recommended 'solution' of chaining them is neither thread-safe nor a general solution, nor applicable in all cases.

It would make much more sense if each parser context could have a callback set for this (which could optionally defer to the global loader if it chose).
Comment 1 GNOME Infrastructure Team 2021-07-05 13:24:10 UTC 
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/libxml2/-/issues/

Thank you for your understanding and your help.