Thanks Achim. I have added:
<feature prerequisite="true">wrap</feature>
Updated the namespace to:
xmlns="http://karaf.apache.org/xmlns/features/v1.3.0”
That error goes away, but now the dependencies are not longer injected:
@Inject
protected FeaturesService featureService;
@Before
public void validateInjectedServices() throws Exception {
assertNotNull(featureService);
Assertion fails because the featureService is null.
Somehow adding a feature that contains the wrap protocol breaks the injection.
Best regards,
Alex soto
> On Nov 4, 2015, at 2:06 PM, Achim Nierbeck <[email protected]> wrote:
>
> Hi,
>
> yeah in your own feature.xml make sure the wrap feature is marked as a
> prerequisite=true feature.
> With that your feature will resolve just fine.
>
> regards, Achim
>
>
> 2015-11-04 20:05 GMT+01:00 Alex Soto <[email protected]
> <mailto:[email protected]>>:
> Hello,
>
> While trying to upgrade from Karaf 3.0.3 to 4.0.2, my integration test (now
> using Pax-Exam version 4.6.0) started to fail because of the wrap protocol is
> not known. One of the jars in my features.xml uses the “wrap” prefix.
>
> <bundle>wrap:mvn: ….
>
> An exception is thrown:
>
> Caused by: java.net.MalformedURLException: Unknown protocol: wrap
>
> This used to work just fine before the upgrade. Is there anything I need to
> specify so that the wrap protocol is recognized?
>
> Best regards,
> Alex Soto
>
>
>
>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/ <http://karaf.apache.org/>> Committer
> & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/
> <http://wiki.ops4j.org/display/paxweb/Pax+Web/>> Committer & Project Lead
> blog <http://notizblog.nierbeck.de/ <http://notizblog.nierbeck.de/>>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS
> <http://bit.ly/1ps9rkS>>
>
> Software Architect / Project Manager / Scrum Master
>
