Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Mon, 12 Mar 2012 14:48:37 +0000 (UTC)
From: "Thomas Diesler (Commented) (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: 
 <1223488213.2907.1331563717886.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <365218273.2165.1331557137726.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (FELIX-3388) Complex uses resolver failure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227577#comment-13227577 ] 

Thomas Diesler commented on FELIX-3388:
---------------------------------------

> Is this not correct? 

Yes, that would be correct. However, the standalone resolver code base, which I'm testing with would return something like

DEBUG: WIRE: [8.0] osgi.wiring.package; (&(osgi.wiring.package=javax.servlet)(version>=2.3.0)(!(version>=3.0.0))) -> [7.0] 

> no the environment should NOT return substituted capabilities

My question was about, whether the Environment should even offer the javax.servlet package capability from http.service.provider? 
It knows that http.service.provider imports that package from javax.servlet.api. i.e. should the Environment consider existing wirings when finding providers or should it return the providers based on matching only. In the latter case the Resolver would have to deal with the exiting wirings

What do you say to the potential fix that I provided above?
                
> Complex uses resolver failure
> -----------------------------
>
>                 Key: FELIX-3388
>                 URL: https://issues.apache.org/jira/browse/FELIX-3388
>             Project: Felix
>          Issue Type: Bug
>            Reporter: Thomas Diesler
>         Attachments: test.log
>
>
> Consider this
>         // Bundle-SymbolicName: javax.servlet.api
>         // ExportPackage: javax.servlet;version=2.5
>         // Bundle-SymbolicName: enterprise.jar
>         // ExportPackage: org.osgi.service.http;version=1.2.1;uses:=javax.servlet
>         // ImportPackage: javax.servlet;resolution:=optional
>         // Bundle-SymbolicName: http.service.provider
>         // ExportPackage: javax.servlet;version=2.5
>         // ExportPackage: org.ops4j.pax.web.service;uses:=javax.servlet
>         // ExportPackage: org.osgi.service.http;version=1.2.0;uses:=javax.servlet
>         // ImportPackage: javax.servlet;version="[2.3.0,2.6.0)";resolution:=optional
> Install, resolve and apply results for the above. 
> Verify that package requirement javax.servlet wires to javax.servlet.api
>         // Bundle-SymbolicName: war.extender.jar
>         // ImportPackage: org.ops4j.pax.web.service
>         // ImportPackage: javax.servlet;version="[2.3,3.0)"
> Install, resolve and apply results for the above. 
> Verify that package requirement javax.servlet wires to javax.servlet.api
> The test is here: https://github.com/tdiesler/jbosgi-resolver/blob/master/felix/src/test/java/org/jboss/test/osgi/resolver/UsesDirectiveResolverTest.java

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