[
https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261687#comment-13261687
]
Erlend Garåsen commented on CONNECTORS-467:
-------------------------------------------
It seems that we need to go for the first option instead in order to keep JSP
1.x compatibility. Since the tag libraries in JSTL 1.2 have new URIs (e.g.
http://java.sun.com/jsp/jstl/core), web containers will probably assume the new
URIs unless the old ones are specified.
I have placed the <taglib> directives inside a <jsp-config> directive and
tested MCF on Resin 4.0.19, Tomcat 7.0.6 and Jetty 7.5.4 without any problems.
If there are no comments, I will commit my changes tomorrow.
> Remove outdated taglib directives in web.xml
> --------------------------------------------
>
> Key: CONNECTORS-467
> URL: https://issues.apache.org/jira/browse/CONNECTORS-467
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework core
> Affects Versions: ManifoldCF 0.5
> Reporter: Erlend Garåsen
> Assignee: Erlend Garåsen
> Fix For: ManifoldCF 0.6
>
>
> Resin does not accept the web.xml file which belongs to the web-crawler-ui
> application and returns 500 Server error after deployment. Resin complains
> about an unexpected <taglib>-tag. The taglib directive is not longer needed
> in JSP 2.0 which we're now using. Some information about how we can configure
> MCF properly for JSP 2.0:
> http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml
> It's probably possible to place the taglib directives inside a <jsp-config>
> directive as a quick fix as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
