hi,

Today I stumbled upon a confusing situation involving an application (Forum) that has a jar that contains it's own taglibcontent.xml file. This file was found (by the classloader) before the taglibcontent.xml in mmbase-taglib.jar was found and caused the new 'links' escaper not to be found anymore.

I now have a conflicting situation: the mmbase-taglib.jar contains some needed settins, and the mmbase-mmbob.jar (the jar holding the Forum application) _also_ contains some needed settings, but there is no way to use both, and no way to know which one will be found first (unless you know the way the appserver's classloader works).

Probably a system where applications can define their own extensions for the taglibcontent.xml file is needed.

I think that if you want to signal possible versioning conflicts with multiple taglibcontent.xml's in the current situation it's probably best to seal the org.mmbase.bridge.jsp.taglib.resources package, this will at least give you an error while starting mmbase instead of an error somewhere in a page after you add a jar.

Simon



Reply via email to