I was looking at the Aries JAXRS whiteboard example to see how it differs
from just using CXF directly. It looks interesting. My one main concern
would be around the Aries whiteboard bundle needing to repackage cxf
dependencies. Could that be a hinderance around CXF version upgrades when
used in
Hi,
I feel that the best place to ask this question would be the Apache Aries mail
list (given that it’s an Aries project). I’m therefore cross posting this back
to the Aries list.
In general repackaging a library is intended to shield users from the
underlying implementation details. In the
Yes, you are correct Tim. I forgot there is an Aries list, my bad!
Thank you for the explanation Tim, that makes perfect sense to me :) It's
pretty cool to be able to whip up some jaxrs classes without the extra
boiler plate.
Ryan
On Mon, Jun 17, 2019 at 5:30 AM Timothy Ward
wrote:
> Hi,
>
Yes, we’re really proud of the JAX-RS whiteboard - particularly when you can
use it with the DS 1.4 Component Property annotations. It’s brilliantly simple
to use.
All the best,
Tim
> On 19 Jun 2019, at 14:32, Ryan Moquin wrote:
>
> Yes, you are correct Tim. I forgot there is an Aries list,
Yes, it's an impressive accomplishment, I hope I didn't come off the wrong
way with my questions. I wanted to figure out how the JAX-RS whiteboard
stuff might play together with the CXF REST services I already have. I'll
make sure to ask any further questions in the Aries list.
Ryan
On Wed, Jun
Just FYI: ECF's impl of OSGi R7 Remote Services has a CXF [1] as Karaf
features.
This uses only Jax-RS 2 annotations rather than the OSGI annotations,
and since OSGi spec'd works seamlessly with DS.
There's a tutorial here [2] that uses either Jersey or CXF. Of course
any existing servic