On 04/11/16 16:11, Christian Schneider wrote:
> Have you actually tried the examples from CXF-DOSGi 2.0.0?
No, but they look pretty simple. However, I have used CXF-DOSGi for a
distributed services setup some years ago.
>
> Are they really too complicated?
I didn't say nor meant 'complicated'.
Have you actually tried the examples from CXF-DOSGi 2.0.0?
Are they really too complicated?
Christian
2016-11-04 12:20 GMT+01:00 Ancoron Luciferis <
ancoron.lucife...@googlemail.com>:
> Hi,
>
> I just went the DS-route myself with JAX-RS inside Karaf.
>
> If you just want to publish a ReST
On 11/4/2016 1:26 AM, Tim Ward wrote:
Whilst it is therefore true that a subset of JAX-RS resources can be exposed
using Remote Services, it's not necessarily a good option if you're looking to
put together a full REST API.
I suspect a lot of actual use cases (perhaps this one) would be
Hi,
I just went the DS-route myself with JAX-RS inside Karaf.
If you just want to publish a ReST endpoint going the remote services
route seems way too complex.
What I found very useful and reliable to work especially for the dynamic
resource service case is the following:
In case you're looking for a JAX-RS whiteboard implementation you could
have a look at https://amdatu.org/application/web/. It doesn't implement
the complete JAX-RS whiteboard draft spec. It does not have a
JaxRSServiceRuntime implementation yet and it's currently using Apache Wink
internally
I note that both of the Remote Services options provided have examples using
JAX-RS annotated service interfaces, which doesn't actually match the code
provided in the example below.
Using Remote Services also doesn't give you a standard way to handle request
scoped resources (i.e. prototype
On 11/3/2016 2:17 AM, Christian Schneider wrote:
You can use CXF-DOSGi to register your rest resource. You just need to
add some properties to your example component to make it work.
Another option is to use ECF's impl of OSGI Remote Services [1] with the
Jax-RS distribution provider
Tanvir,
Not a trivial issue as one needs to combine two injectors in a single
object.
You did not mention how you declare your REST resource class to Jersey
in your environment.
The process will probably at some point publish a servlet using new
You can use CXF-DOSGi to register your rest resource. You just need to
add some properties to your example component to make it work.
See
https://github.com/apache/cxf-dosgi/tree/master/samples
There is a also a bndrun file to easily run and package CXF-DOSGi for
bndtools.
There is an upcoming specification in OSGi R7 that allows you to define JAX RS
components using an OSGi whiteboard. This would completely solve your problem,
but the spec and implementation are still being developed.
For now you could fix this by registering your existing servlet as a service
I have a REST resource class, say Employees, and I need access to
another service using DS. Hence I have to make this call a component.
Now objects instantiated by @component and JAX-RS Servlet are not same.
I do not want to use static reference to the service as shown below. How
this can
11 matches
Mail list logo
