JaxRS Remote Services using latest Jersey or Apache CXF

Hi Folks, There's a new version of the ECF JaxRS Distribution Provider [1].   This provider implements OSGi R7 Remote Services [2] via the JaxRS support in new Jersey 2.28 or Apache CXF 3.3. In practice, this means that any JaxRS-annotated service can be exported as a spec-compliant Remote

Re: Home and End key bindings in karaf 4.2.3

Hi Jean-Baptiste, I experience a similar problem with Karaf 4.2.3 on Ubuntu 18.04 and Red Hat 6.9. Trying TERM values "xterm", "xterm-color" and "xterm-color256", I captured what I see in screen recordings (https://imgur.com/a/5GRrP05). Regards, -Max On 2/25/19 9:11 PM, Jean-Baptiste Onofré

Re: websocket not working in karaf 422

Hi, You can take a look at the Karaf examples: https://github.com/apache/karaf/tree/master/examples/karaf-websocket-example regards, François Papon fpa...@apache.org Le 26/02/2019 à 18:27, munishgupta.asr a écrit : > Hi Team > > I upgraded my karaf from 3.x to 4.2.2 and after that one of my

Re: Modular graphic interface

Long long time ago we made an attempt to push concept of modular console forward: https://github.com/apache/karaf-webconsole. This project is archived for quite long time as it didn't get beyond Karaf. As you might expect other communities favored their own tools. Above is based on wicket, still

websocket not working in karaf 422

Hi Team I upgraded my karaf from 3.x to 4.2.2 and after that one of my bundles where websocket is there is not working. After some changes able to make the my websocket server up but when tried to connect that from client plugin it was not happening. In developer tools , network tab the

Re: KARAF-5742 quick question

Just add the variable definition to etc/shell.init.script Guillaume Le mar. 26 févr. 2019 à 12:25, Daniel Estermann a écrit : > Thanks for the example, I see know what "em", "ee" and "st" stand for. > But there was a little misunderstanding. I wanted to have that session > variable set

Re: KARAF-5742 quick question

Thanks for the example, I see know what "em", "ee" and "st" stand for. But there was a little misunderstanding. I wanted to have that session variable set permanently, not for a single session. How to achieve it? Am Di., 26. Feb. 2019 um 12:00 Uhr schrieb Guillaume Nodet < gno...@apache.org>: >

Re: KARAF-5742 quick question

Fwding to user@k.a.o Le mar. 26 févr. 2019 à 11:03, Daniel Estermann a écrit : > Hi Guillaume, > > you have fixed the above mentioned issue >

Re: JAXB 2.2 and 2.3 in Karaf 4.1.5

If the headers are clean, yes it should work. Le 26 févr. 2019 à 10:41, à 10:41, Oliver Wulff a écrit: >Hi JB > > >Will it also work to deploy JAXB 2.2 and 2.3 in Karaf 4.1.5 when I >ensure that the import headers are correct? > > >Thanks > >Oli > > >Von:

AW: JAXB 2.2 and 2.3 in Karaf 4.1.5

Hi JB Will it also work to deploy JAXB 2.2 and 2.3 in Karaf 4.1.5 when I ensure that the import headers are correct? Thanks Oli Von: Jean-Baptiste Onofré Gesendet: Dienstag, 26. Februar 2019 10:03:14 An: user@karaf.apache.org Betreff: Re: JAXB 2.2 and 2.3

Re: JAXB 2.2 and 2.3 in Karaf 4.1.5

Hi Oliver, yes you can still install JAXB 2.2 bundle (or via feature). Regards JB On 26/02/2019 09:59, Oliver Wulff wrote: > Hi there > > > Recently I run into an issue with OpenAPI implemenation (Swagger3 2.0.6) > due to a dependency to JAXB 2.3 in Karaf 4.1.5. Some bundles require > version

JAXB 2.2 and 2.3 in Karaf 4.1.5

Hi there Recently I run into an issue with OpenAPI implemenation (Swagger3 2.0.6) due to a dependency to JAXB 2.3 in Karaf 4.1.5. Some bundles require version 2.2 and Swagger 3 2.0.6 requires JAXB 2.3. This was the error message: >>> org.apache.karaf.features.internal.util.MultiException: