[jira] [Created] (SMX4-1881) Spring 3.2.11 jar imports invalid JSTL version range [2.0,3.0)

["Matt Magoffin (JIRA)" <ji...@apache.org>]

Matt Magoffin created SMX4-1881:
-----------------------------------

             Summary: Spring 3.2.11 jar imports invalid JSTL version range [2.0,3.0)
                 Key: SMX4-1881
                 URL: https://issues.apache.org/jira/browse/SMX4-1881
             Project: ServiceMix 4
          Issue Type: Bug
          Components: Bundles
    Affects Versions: bundles-2014.09
            Reporter: Matt Magoffin


I am trying to deploy the ServiceMix Spring WebMVC 3.2.11 bundle into an existing OSGi web app but it fails because it can't find the javax.servlet.jsp.jstl.core.Config class, even though my web bundle imports the various JSTL packages. I think it is because the WebMVC bundle manifest imports JSTL packages as

javax.servlet.jsp.jstl.core;resolution:=optional;version="[2.0.0,3.0.0)",
javax.servlet.jsp.jstl.fmt;resolution:=optional;version="[2.0.0,3.0.0)"

There is no version 2.0 of JSTL, so this import would fail to find anything. I then noticed in the spring-webmvc POM this configuration:

{code:xml}
<servicemix.osgi.import.pkg>
javax.servlet.jsp.*;version="[2.0.0, 3.0.0)";resolution:=optional
</servicemix.osgi.import.pkg>
{code}

Perhaps it needs another qualifier, like

{code:xml}
<servicemix.osgi.import.pkg>
javax.servlet.jsp.*;version="[2.0.0, 3.0.0)";resolution:=optional,
javax.servlet.jsp.jstl*;version="[1.1.2, 2.0.0)";resolution:=optional
</servicemix.osgi.import.pkg>
{code}





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)