ECF's modular implementation of OSGi Remote Services supports the runtime selection of a distribution provider. Distribution providers are responsible for the underlying communication when a remote method call is made.
ECF commiters and contributors have been adding distribution providers, and we are now up to 9 publicly available providers: ECF generic, r-OSGi, websocket r-OSGi, JMS/ActiveMQ, MQTT/Paho, Jax-RS Jersey, Jax-RS CXF, Hazelcast, and REST-API-based providers,
We've documented these distribution providers, so that consumers may compare and contrast them, understand dependencies, and have working examples in case they choose to create their own distribution provider.
2 comments:
Hi,
I'm using CXF-DOSGI to publish webservices with an jaxws frontend.
Can ECF handle jaxws and are there similar providers?
Best regards
Ben
Hi Ben,
>I'm using CXF-DOSGI to publish webservices with an jaxws frontend.
>Can ECF handle jaxws and are there similar providers?
We have a provider for Jax-RS: https://github.com/ECF/JaxRSProviders
We don't yet have a provider for Jax-WS, but after writing the JaxRS provider, I can tell you that it's quite likely that creating a CXF-based Jax-WS provider would be straightforward (I can't say trivial because I don't know the CXF-jax-ws APIs). FWIW, the CXF-based jax-rs provider is quite small/simple (just a very few classes).
If you are interested in either collaborating on or contributing such a provider, I suggest that you join the ecf-dev mailing list: https://dev.eclipse.org/mailman/listinfo/ecf-dev and open an enhancement request: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=ECF
Thanks,
Scott
Post a Comment