[
https://issues.jboss.org/browse/JBAS-8916?page=com.atlassian.jira.plugin....
]
Stan Silvert commented on JBAS-8916:
------------------------------------
Yes, that's a good idea. The SCI for JSF could also be shared.
This might be a bit off topic, but the best way for this to work would be to add the TLDs
only when needed. In the case of the JSF TLDs, that would mean adding them to the
deployment after the JSF SCI has run. Once web.xml, web-fragment.xml, and the JSF SCI
have been processed you can know for sure if this is a JSF deployment by detecting the
declaration of a FacesServlet.
Need shared TLD's for JSTL and JSF
----------------------------------
Key: JBAS-8916
URL:
https://issues.jboss.org/browse/JBAS-8916
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JSF, Web (Tomcat) service
Affects Versions: 7.0.0.Alpha1
Reporter: Stan Silvert
Assignee: Remy Maucherat
Priority: Critical
Attachments: jsfwithjsp.war
JSTL applications and JSP-based JSF applications will fail because the TLD's are not
processed for WARs that need them. We need a shared TLD facility similar to previous AS
versions so that these tag libs are parsed only once and then shared with every WAR.
I'm attaching a simple WAR to smoke-test JSTL and JSP-based JSF. With the attached
WAR, The following URLs will yield the following errors:
http://localhost:8080/jsfwithjsp/hellojsf.faces
org.apache.jasper.JasperException: The absolute uri:
http://java.sun.com/jsf/html cannot
be resolved in either web.xml or the jar files deployed with this application
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:116)
org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:239)
http://localhost:8080/jsfwithjsp/hellojstl.jsp
org.apache.jasper.JasperException: The absolute uri:
http://java.sun.com/jsp/jstl/core
cannot be resolved in either web.xml or the jar files deployed with this application
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:116)
org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:239)
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira