[
https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260373#comment-13260373
]
Erlend Garåsen commented on CONNECTORS-467:
---
bq. Alternatively, if there is a way to do the same thing without wrecking JSP
1.x compatibility, then we can just fix this.
JSP 1.2 TLD files, to which the path is referenced in our web.xml, should be
upward compatible. There should be no need to change them in order to be
compatible with JSP 2.0. Some web containers, such as Resin, complains because
we are now pointing to an XSD which does not have any reference to a taglib
alement:
{code}
http://java.sun.com/xml.ns/javaee/web-app_2_5.xsd; version=2.5
{code}
We have two options:
1. Place the taglib directives inside a jsp-config directive.
2. Just remove the taglibs directives. JSP containers should automatically look
for TLD files in all subfolders of app/WEB-INF which is the case for MCF
(they are placed inside the subfolder jsp).
I think we should go for the last option. I can try to deploy the application
on both Resin and Tomcat in order to test whether it works as expected. Do you
think we should open a vote thread for these two options mentioned above?
MCF version 0.5 does not run on Resin
-
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
