[jira] [Commented] (CONNECTORS-648) Wars fail to deploy in Tomcat 7
[
https://issues.apache.org/jira/browse/CONNECTORS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581233#comment-13581233
]
Erlend Garåsen commented on CONNECTORS-648:
---
Resin does not complain about this error when I deploy version 1.1.1 using the
combined war. Usually, Resin is very strict about such things, so
interestingly, this was not the case here.
The patch runs fine on Resin as well, so thanks for your contribution (checked
by doing svn up since Karl has committed it).
Wars fail to deploy in Tomcat 7
---
Key: CONNECTORS-648
URL: https://issues.apache.org/jira/browse/CONNECTORS-648
Project: ManifoldCF
Issue Type: Bug
Affects Versions: ManifoldCF 1.1.1
Reporter: Jan Høydahl
Assignee: Karl Wright
Labels: Tomcat7
Fix For: ManifoldCF 1.2
Attachments: CONNECTORS-648.patch, CONNECTORS-648.patch
This is a followup on CONNECTORS-568, which I believe is still not solved.
I deploy mcf-combined-service.war in Tomcat 7.0.35, and I get the error
{noformat}
IllegalArgumentException: taglib definition not consistent with specification
version
{noformat}
Then I unpack the WAR and removes the whole {{jsp-config}} and
{{taglibs}} from it, as adviced in
http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml
Restarting, and successful startup, but trying to hit
http://localhost:8080/mcf/ brings this error from ./index.jsp line 1
{noformat}
org.apache.jasper.JasperException:
The absolute uri: http://java.sun.com/jstl/core cannot be resolved
in either web.xml or the jar files deployed with this application
{noformat}
So then I open the JSPs and see that the taglib refs in {{adminDefaults.jsp}}
and {{adminHeaders.jsp}} refer to {{http://java.sun.com/jstl/core}} which is
wrong. According to http://stackoverflow.com/tags/jstl/info since JSTL1.1 the
path must have /jsp/ in the path. Changing that and restarting brings up the
GUI just fine!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-648) Wars fail to deploy in Tomcat 7
[
https://issues.apache.org/jira/browse/CONNECTORS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580354#comment-13580354
]
Karl Wright commented on CONNECTORS-648:
Hmm - had no reports of difficulty for quite some time having to do with this.
Have tested on jetty and Resin fairly extensively.
I'll try the patch locally here to see if there are any Jetty issues. If not,
will try Resin and will commit if Resin too is happy.
Wars fail to deploy in Tomcat 7
---
Key: CONNECTORS-648
URL: https://issues.apache.org/jira/browse/CONNECTORS-648
Project: ManifoldCF
Issue Type: Bug
Affects Versions: ManifoldCF 1.1.1
Reporter: Jan Høydahl
Labels: Tomcat7
Attachments: CONNECTORS-648.patch
This is a followup on CONNECTORS-568, which I believe is still not solved.
I deploy mcf-combined-service.war in Tomcat 7.0.35, and I get the error
{noformat}
IllegalArgumentException: taglib definition not consistent with specification
version
{noformat}
Then I unpack the WAR and removes the whole {{jsp-config}} and
{{taglibs}} from it, as adviced in
http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml
Restarting, and successful startup, but trying to hit
http://localhost:8080/mcf/ brings this error from ./index.jsp line 1
{noformat}
org.apache.jasper.JasperException:
The absolute uri: http://java.sun.com/jstl/core cannot be resolved
in either web.xml or the jar files deployed with this application
{noformat}
So then I open the JSPs and see that the taglib refs in {{adminDefaults.jsp}}
and {{adminHeaders.jsp}} refer to {{http://java.sun.com/jstl/core}} which is
wrong. According to http://stackoverflow.com/tags/jstl/info since JSTL1.1 the
path must have /jsp/ in the path. Changing that and restarting brings up the
GUI just fine!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
