Hi guys,
quick update about this. I removed the blueprint dependency to use the same
approach as other Karaf modules (BaseActivator). I also started to use the JAXRS
spec instead of CXFRS backend.
I started an local integration branch this morning. I should create a PR
including utests/itests, fea
I agree that Aries JAXRS whiteboard currently might not be in good enough
shape to already use it. I am pretty sure though that it can be fixed to
fit nicely to what we need.
I think the embedding is on purpose to make it easy to deploy jax-rs
whiteboard to platforms outside of karaf. Maybe it can
Yeah, it's where I'm struggling, it requires some private package, and so.
I'm not a big fan right now to be honest.
Regards
JB
On 01/19/2018 02:33 PM, Daniel Kulp wrote:
JAX-RS whiteboard currently has a few other issues, mostly due to the
implementation in Aries. Probably should find some
JAX-RS whiteboard currently has a few other issues, mostly due to the
implementation in Aries. Probably should find some time to work on that.
The main issue is that, right now, it embeds parts of CXF but then exports a
few packages. Thus, getting it and a “real” CXF application working toge
I'm agree with Guillaume, CXF could be the default implementation but
not be mandatory.
Le 19/01/2018 à 16:54, Guillaume Nodet a écrit :
> 2018-01-19 13:45 GMT+01:00 Daniel Kulp :
>
>>
>>> On Jan 19, 2018, at 4:00 AM, Guillaume Nodet wrote:
>>>
>>> * investigate the use of JaxRS 2.0 api instead
Actually, it's what I started to check using Aries JAXRS.
I will give you an update with the different options I'm evaluating.
Regards
JB
On 01/19/2018 02:01 PM, Christian Schneider wrote:
How about implementing jax-rs services using the OSGi jax-rs whiteboard
spec? So the implementation would
How about implementing jax-rs services using the OSGi jax-rs whiteboard
spec? So the implementation would be CXF but the code would ideally only be
tied to the jax-rs spec and the jax-rs whiteboard spec.
Cheers
Christian
2018-01-19 13:54 GMT+01:00 Guillaume Nodet :
> 2018-01-19 13:45 GMT+01:00 D
2018-01-19 13:45 GMT+01:00 Daniel Kulp :
>
>
> > On Jan 19, 2018, at 4:00 AM, Guillaume Nodet wrote:
> >
> > * investigate the use of JaxRS 2.0 api instead of the CXF dependency (to
> > be more flexible and also because it would create yet another circular
> > dependency)
>
> I’m not sure I get
> On Jan 19, 2018, at 4:00 AM, Guillaume Nodet wrote:
>
> * investigate the use of JaxRS 2.0 api instead of the CXF dependency (to
> be more flexible and also because it would create yet another circular
> dependency)
I’m not sure I get this….. Even if you use the JAX-RS 2.0 API, you still
Thanks for the feedback, and fully agree.
I'm planning to do that for the PR.
Regards
JB
On 01/19/2018 10:00 AM, Guillaume Nodet wrote:
Sounds good to me.
I think there's a few technical things that need to be addressed while
merging:
* remove blueprint dependency
* use a single bundle
Sounds good to me.
I think there's a few technical things that need to be addressed while
merging:
* remove blueprint dependency
* use a single bundle (i don't see any benefit in splitting this feature
in multiple bundles)
* investigate the use of JaxRS 2.0 api instead of the CXF dependency
+1 sound like an interesting idea i'd like to see.
2018-01-18 11:15 GMT+01:00 Andrea Cosentino :
> +1 :-)
>
> --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @osc
+1 :-)
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Thursday, January 18, 2018, 10:38:03 AM GMT+1, Jean-Baptiste Onofré
wrote:
Hi,
Hi JB,
I think it's a good idea !
I'm agree with adding docker as a dedicated module in Karaf container
because it just use docker.
It would be also interesting to be able to create an image of Karaf from
the running instance :)
François
Le 18/01/2018 à 13:37, Jean-Baptiste Onofré a écrit :
>
Hi,
Some days ago, we discussed about Decanter 2.0.0 and using "external" instances
of used engines, like Elasticsearch or Kibana.
Basically, the main reason is that some engines are not easy to embed in Karaf.
It's the case of Kibana as it uses node.js.
However, one of the big advantage o
15 matches
Mail list logo
