[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ecf-dev] distribution providers
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Wed, 9 Sep 2015 12:26:07 -0700
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
Over the past few weeks, I've used the new ECF 3.11.0 provider API to
create several new providers. First, I've created several providers
based upon Jax Rest Services (Jax RS) specification...specifically the
implementations from Jersey, CXF, and started one based upon RestEasy.
I designed these bundles to reuse common classes (dependent upon
Jax-RS...e.g. javax.ws.rs packages) so that it's now much easier to
introduce additional Jax-RS implementations (e.g. Restlet).
These JaxRS-based providers are in this repo , along with some examples.
I've also created some tutorials  describing how REST-standards-based
remote services can easily be created...and be completely independent of
any REST implementation, or even any remote services implementation.
I would like to request assistance from other committers and/or ECF
contributors in setting up the build/distribution meta-data for these
projects, so that we can build them and make them available as
bundles. The various Jax-RS implementations are relatively large (e.g.
Jersey, CXF, etc) and have quite a few dependencies of their own. The
good news is that at least Jersey bundles are available from Orbit, the
bad news is that the version in Orbit needs to be upgraded and the
original Orbit contributor needs some assistance with an upgrade of the
Jersey version in Orbit.
CXF is distributed as bundles, but it's not in Orbit. It is in maven
repos, as are most or maybe all of it's dependencies. It has a
significant number of dependencies and so getting all the versions
correct, etc. could be an effort for someone not familiar with CXF
As you can tell, there's a fair amount to do to build and deploy these
providers, provide a way for consumers to install all dependencies (via
both p2 repo and Karaf features). I request some help with that, as it
would be very nice for people to be able to easily switch among several
distribution providers for their remote services.
Thanksinadvance for your contributions.