Bernhard Hablesreiter created MYFACES-4767:
----------------------------------------------
Summary: Custom taglib.xml files are not working
Key: MYFACES-4767
URL: https://issues.apache.org/jira/browse/MYFACES-4767
Project: MyFaces Core
Issue Type: Bug
Affects Versions: 4.1.4
Environment: Wildfly 41.0.1, PrimeFaces 16, MyFaces 4.1.4
Reporter: Bernhard Hablesreiter
After switching from MyFaces 4.1.3 to 4.1.4 we noticed that our custom
taglib-files in /lib/*.jar(/META_INF/.*taglib.xml) are not picked up anymore.
This might be related to some changes made to the
DefaultFacesConfigurationProvider in combination with the MetaInfResourceCache.
We found out that some primefaces taglibs are picked up, but not our custom
taglibs in one of our jar-files. We cannot figure out why this is happening as
the . For some reason the classloader is not able to return those files in
loader.getResources(name).
The following primefaces-taglibs are loaded:
/META-INF/primefaces.taglib.xml
/META-INF/primefaces.urn.taglib.xml
However, when debugging, these files are found twice, once as shown above and
once with the full jar-path (e.g.
/lib/primefaces-16.0.0.jar/META-INF/primefaces.taglib.xml) and the files with
the full path are also not loaded correclty, although we don't know why they
are appearing twice in the MetaInfEntryNames.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)