>>>>> Nhut Thai Le <[email protected]>:

> I had some REST api hosted by jersey running on a stand alone version of
> jetty but when we moved to paxweb, i was not able to make it work anymore,
> so i end up switching to aries-jax-rs-whiteboard.

I have Jersey in Karaf working in two different places:
 https://github.com/steinarb/ukelonn/tree/master/ukelonn.web.services
 https://github.com/steinarb/jersey-demo

The jersey-demo is a minimal example of how to do jersey in karaf, there
is also a PR in progress to turn the jersey-demo into an example in
karaf:
        https://github.com/apache/karaf/pull/633

I was able to load and run the project with the problem in karaf actual,
but the pax exam test of the bundle failed.

The reason for the test startup failure was that this maven dependency
in the pax exam test project, had transitive dependencies to bundles in
karaf 4.1.1 and that caused pax exam to fail on startup:
        <dependency>
            <groupId>org.ops4j.pax.jdbc</groupId>
            <artifactId>pax-jdbc-features</artifactId>
            <version>1.3.1</version>
            <type>xml</type>
            <classifier>features</classifier>
        </dependency>

Adding an <exclusion> for the root transitive dependency made the pax
exam test start without failing:
        <dependency>
            <groupId>org.ops4j.pax.jdbc</groupId>
            <artifactId>pax-jdbc-features</artifactId>
            <version>1.3.1</version>
            <type>xml</type>
            <classifier>features</classifier>
            <exclusions>
                <exclusion>
                    <groupId>org.apache.karaf</groupId>
                    <artifactId>org.apache.karaf.client</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

This is the same as the other pax exam issue I had, ie. that just having
a maven dependency to something affect the way pax exam starts (or:
affects the way karaf starts in pax exam (I'm not sure exactly what the
problem is?)).

Ie. it's not a dependency *in* the features repository the maven
dependency loads, that is the problem.  It's the maven dependency
*itself* that causes the pax exam startup problems.

(And this is unexpected and can be tricky to find)

Perhaps I should open a JIRA for this?

-- 
-- 
------------------
OPS4J - http://www.ops4j.org - [email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to