Can you wrap up your example into a package and place on Google drive so community can download it and use it. We may be able to find the solution with the package.  I want to test this.

Just to confirm - Core Image component uses a PathField to select the image - this confirms its best practice to select images via a dialog. This has been a good discussion...

I created an OSGi that contains just the cxf-rt-frontend-jaxrs-3.1.10.jar.  It deployed without an issue and did not effect other bundles. Look here...

For this 1 JAR (cxf-rt-frontend-jaxrs-3.1.10.jar) - have you tried to wrap this one in a separate OSGi bundle and deploy it?

We are checking internally - we do not have any doc on this other then Javadocs.

Its the best way for AEM 6.4 development. Trying to make a project built for an older AEM version work in the current version is error prone.Much better to build an AEM project with its corresponding Maven Archetype project. For 6.4 - its Archetype 13.

I believe its an addon to AEM as opposed to a standalone core service like Target.

If you are going to base your components on an out of the box component - look at the Core components. Start by looking at the Image COre Component and see how that component is setting an image. (I still think its better to set images via a path browser in the component dialog however)

Its still best practice to allow component values - like text, images, videos, to be set by the component dialog. In terms of an image - a Pathbrowser resource type should be used.This is essentially best practice for AEM components to be built.  If you are not using a component dialog - how do you ...