Swami created CONNECTORS-568:
--------------------------------

             Summary: The mcf-combined-service war doesn't work with Tomcat 7.0
                 Key: CONNECTORS-568
                 URL: https://issues.apache.org/jira/browse/CONNECTORS-568
             Project: ManifoldCF
          Issue Type: Bug
          Components: API, Framework core, Site
    Affects Versions: ManifoldCF 1.0.1
         Environment: Tomcat 7 on Windows 2008 R2
            Reporter: Swami
            Priority: Critical
             Fix For: ManifoldCF 1.1


Deploying mcf-combined-service to Tomcat 7 causes the following error when 
loading the UI.

type Exception report

message /index.jsp (line: 1, column: 1) The absolute uri: 
http://java.sun.com/jstl/core cannot be resolved in either web.xml or the jar 
files deployed with this application

description The server encountered an internal error that prevented it from 
fulfilling this request.

exception 

org.apache.jasper.JasperException: /index.jsp (line: 1, column: 1) The absolute 
uri: http://java.sun.com/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:42)
        
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:408)
        
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:89)
        
org.apache.jasper.compiler.Parser.processIncludeDirective(Parser.java:324)
        org.apache.jasper.compiler.Parser.parseIncludeDirective(Parser.java:357)
        org.apache.jasper.compiler.Parser.parseDirective(Parser.java:467)
        org.apache.jasper.compiler.Parser.parseElements(Parser.java:1427)
        org.apache.jasper.compiler.Parser.parse(Parser.java:138)
        
org.apache.jasper.compiler.ParserController.doParse(ParserController.java:242)
        
org.apache.jasper.compiler.ParserController.parse(ParserController.java:102)
        org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:198)
        org.apache.jasper.compiler.Compiler.compile(Compiler.java:373)
        org.apache.jasper.compiler.Compiler.compile(Compiler.java:353)
        org.apache.jasper.compiler.Compiler.compile(Compiler.java:340)
        
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:646)
        
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)
        org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
        org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:722)


To fix the issue the workaround I had created was to merge the web.xml in the 
mcf-crawler-ui.war and then modify the root <web-app> node attribute as follows
<web-app xmlns="http://java.sun.com/xml/ns/javaee";
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
  http://java.sun.com/xml.ns/javaee/web-app_2_5.xsd"; version="2.5">

Add the following taglib entries 

    <taglib>
    <taglib-uri>http://java.sun.com/jstl/core</taglib-uri>
    <taglib-location>/WEB-INF/jsp/c.tld</taglib-location>
    </taglib>

    <taglib>
    <taglib-uri>http://java.sun.com/jstl/fmt</taglib-uri>
    <taglib-location>/WEB-INF/jsp/fmt.tld</taglib-location>
    </taglib>

    <taglib>
    <taglib-uri>http://java.sun.com/jstl/xml</taglib-uri>
    <taglib-location>/WEB-INF/jsp/x.tld</taglib-location>
    </taglib>

    <taglib>
    <taglib-uri>http://java.sun.com/jstl/sql</taglib-uri>
    <taglib-location>/WEB-INF/jsp/sql.tld</taglib-location>
    </taglib>

Following which I had to modify the web-inf\jsp\*.tld files to have the 
<taglib> element attributes change

<taglib xmlns="http://java.sun.com/xml/ns/j2ee";
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee 
http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_1.xsd";
    version="2.0">

--
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

Reply via email to