]
Frank Langelage updated WFLY-1172:
----------------------------------
Attachment: ExternalTld.txt
ExternalTldParsingDeploymentProcessor.java.diff
The .diff file shows the messages I put in.
The .txt file shows the messages from server.log for any web module of my ear.
mechanism to load tag libraries from module
-------------------------------------------
Key: WFLY-1172
URL:
https://issues.jboss.org/browse/WFLY-1172
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web (Undertow)
Reporter: Ivica Loncar
Assignee: Stuart Douglas
Priority: Critical
Labels: modules, tag, taglib, tld
Fix For: 9.0.0.Beta1
Attachments: ExternalTld.txt, ExternalTldParsingDeploymentProcessor.java.diff
Original Estimate: 1 day
Remaining Estimate: 1 day
tag libraries are scanned only if they appear in jar inside WEB-INF/lib or are defined in
tld under WEB-INF.
The simplest scenario to explain why this is a problem: portlet 2 defines standard
portlet taglib, but the classes in this file come from concrete implementations. Currently
I see no way to use 2 different portals in a portable way.
Please provide a way to notify a relevant subsystem for web applications that specific
module contains a .tld.