I’m very happy that one of my upstream issues was fixed in yesterday’s release 2.6.1 of Apache CXF.

I’m very happy that one of my upstream issues was fixed in yesterday’s release 2.6.1 of Apache CXF. This is a problem related to implementation hiding that primarily manifests under OSGi.

If you have a REST client that wants to invoke a service coded with the JAX-RS API it was previously impossible for it to be completely unaware that the client is being backed by CXF (as opposed to Jersey, RestEasy, etc) because there has to be a classloader that can see both the CXF client package and the domain-specific REST interface. Now, you can dynamically create a classloader that can see both and inject that classloader into CXF.

Thank you Sergey Beryozkin!

And thank you Peter KriensĀ for the idea for how to solve via your 2008 article http://blog.osgi.org/2008/08/classy-solutions-to-tricky-proxies.html

https://issues.apache.org/jira/browse/CXF-4290