Re: Release plugin versus karaf plugin

You could try to add: -DpreparationGoals="clean install" 2015-10-21 19:52 GMT+02:00 Benson Margulies : > My assembly project depends on my feature project. When I try to run > release:prepare, I'm get this, where the build of the assembly project > is not finding the feature

Re: How to set the ssh authentication timeout?

> This can be a blocker if you try to set up Karaf in an automated way For my systems, I started using pre-generated keys. A big pro for security: I know if the client is using the correct key / is the correct one. Perhaps also a solution for your timeout.

Re: Status of OBR

> More than OBR, I would recommend to use Feature ResourcesRepository plug to > Cave. > > I'm preparing a blog post about that. That would be great. :)

Re: EIK: Karaf 4 support on Eclipse Mars

Thank you for your reply. I do not know how to debug a Eclipse Plug-In. Have you some lecture / steps how I could develop on / change lines of the EIK source code and debug the Plug-In in an installed and running Eclipse IDE. Have I to build it, install it, look at backtraces ... all manually or

Re: Karaf: How to get Equinox DS working correctly

Hi Achim, > well, the eventadmin is kind of special. Make sure you install the > eventadmin feature, > that one is felix and does provide the needed compendium classes. I am would like to move another project to use Karaf. For the first, I would like to kept all bundles but using Karaf for the

Re: Karaf: How to get Equinox DS working correctly

h...@googlemail.com>: > If you declare those packages as being exported in the maven-bundle-plugin > section and you only have the osgi jar as dependency in your maven > dependency, > that should do the trick already to only contain those packages which you > explicitly export. > &g

Re: Karaf: How to get Equinox DS working correctly

> Currently we start a customizef felix eventadmin in startup.properties. You > can start equinox eventadmin there instead. Das hat funktioniert. Danke

Re: EIK: Karaf 4 support on Eclipse Mars

So, no maven-bundle-plugin to build OSGi bundles? "The bnd-maven-plugin can build Bndtools projects from within Maven."

Re: EIK: Karaf 4 support on Eclipse Mars

h, I think that providing a nice integration with Karaf >> in BndTools might be a better approach than having a separate Karaf plugin. >> I suspect the level of effort to maintain an integration would be >> significantly less than maintaining an entire plugin. >> >> -Original

Re: adding 'just one thing' in an assembly

>> I might try sketching some code for this. That would be great. Perhaps we do not need the separate system property file anymore (@JBO: you created a JIRA shortly) >> >> On Sun, Sep 6, 2015 at 2:02 AM, Jean-Baptiste Onofré wrote: >>> >>> Hi Benson, >>> >>> if you talk about

Re: Configure Karaf Maven Plugin

I do not find a way to do that all stuff usong the karaf-maven-plugin. I am using the karaf-maven-plugin to do what it is currently doing (and doing it good). After that I have another artifact that depend on this one, that is using the maven-assembly-plugin and so on, and doing all the remaining

Re: Configure Karaf Maven Plugin

> Do you mind sharing yur maven > configuration so that I have an example of how to do that? https://github.com/maggu2810/openhab2/tree/master-for-karaf/distributions * openhab2-runtime-karaf is using the karaf-maven-plugin * openhab2-runtime is using the artifact of the previous one, the

Re: Custom distribution: change directory layout

I checked in an example, so you could reproduce it: https://github.com/maggu2810/karaf-custom-distribution/tree/dir-layout repo: g...@github.com:maggu2810/karaf-custom-distribution.git branch: dir-layout

Re: Custom distribution: change directory layout

possible as the kar already have the layout. > I will create Jira to improve that and allow the plugin to change the target > locations. > > The purpose of the current variables is more to be able to adapt to your > machine/administrator constraint: put KARAF_ETC in /etc/karaf, put

Re: Custom distribution: change directory layout

s to write to that directory (I believe this is the working dir). Is it wrong to set base != home or is this check of the instance helper not the best one? 2015-09-20 16:51 GMT+02:00 Markus Rathgeb <maggu2...@gmail.com>: > I checked in an example, so you could reproduce it: > https://gith

Re: Issue with creating apache felix commands using Declarative Services

Hi, I have done with DS referencing org.apache.karaf.shell.api.console.SessionFactory. and then using this: * customCommand is an object that class implements org.apache.karaf.shell.api.console.Command * final Registry registry = sessionFactory.getRegistry(); * registry.register(customCommand);

Re: Custom distribution: change directory layout

> I will try to include a fix for 4.0.2. Great, thanks!

Re: Custom distribution: change directory layout

Created a JIRA: https://issues.apache.org/jira/browse/KARAF-4005 2015-09-21 7:38 GMT+02:00 Markus Rathgeb <maggu2...@gmail.com>: > The instance helper uses "karafHome.equals(karafBase)" to identify the > root instance. > I cannot use the same directory for karaf base and

Custom distribution: change directory layout

Hello, I would like to change the directory layout of my custom distribution. Changing "etc/org.apache.felix.fileinstall-deploy.cfg" I could set another felix.fileinstall.dir. But how can I remove the "deploy" directory? Using bin/setsenv[.bat] I can change KARAF_BASE, KARAF_HOME and KARAF_ETC.

Re: Dynamic parameters in persistence.xml

Hi Jean-Baptiste, I think you read yesterday about it (in a abstracted context). ;) That is the same background I am using in: https://issues.apache.org/jira/browse/KARAF-4124

Re: karaf 4.0.4 clean not working

Why are two wildcards used at all? One should be sufficient. On unixoid systems the .* files are not removed using wildcards only. Will inspect this one and create a JIRA + PR. 2016-01-17 11:40 GMT+01:00 Markus Rathgeb <maggu2...@gmail.com>: > That is correct. The wildcard is in q

Re: karaf 4.0.4 clean not working

That is correct. The wildcard is in quotes, so it will not be evaluated by the shell. 2016-01-15 0:09 GMT+01:00 Pratt, Jason : > The clean flag is not working for bin/karaf or bin/start on linux and win7 > > When used all files/directories still remain in the data

Re: karaf 4.0.4 clean not working

JIRA created: https://issues.apache.org/jira/browse/KARAF-4278 2016-01-17 11:44 GMT+01:00 Markus Rathgeb <maggu2...@gmail.com>: > Why are two wildcards used at all? One should be sufficient. On > unixoid systems the .* files are not removed using wildcards only. > Will inspect this

Re: does EIK work with 4.0.4?

Hello, I asked a similar question August 2015: https://www.mail-archive.com/user@karaf.apache.org/msg11439.html The last commit has been done on Aug 13, 2014 (https://github.com/apache/karaf-eik/commits/master). So I don't think there has anything been changed and it is still not working using

Re: OSGi Compendium within a feature restarts the console

FYI "But what if you want to use the APIs at runtime? To support using the APIs at runtime, OSGi has now made the companion code for individual specifications available as individual companion code bundles." http://blog.osgi.org/2015/08/more-jars-on-maven-central-and-jcenter.html 2016-02-29 8:40

Re: OSGi Compendium within a feature restarts the console

It has been some time ago, I had to use the Equinox Event Admin and DS implementation. That bundles (I have not checked other versions) missing the APIs - they contain only the implementation. So I have to create a splitted compendium myself to get them working in Karaf. I read this blog and I am

Re: Karaf maven plugin package vs install

I ran into the same problem some time ago using the release plugin. To use the release plugin the preparation goal have to be set to execute the "install" phase. 2016-03-11 20:29 GMT+01:00 Raman Gupta : > My project builds assembly modules and then in another module runs

Re: Problems with feature repository in karaf 4.0.4

http://karaf.922171.n3.nabble.com/Installing-spring-web-via-feature-file-brings-in-multiple-versions-of-spring-td4045572.html 2016-04-11 22:38 GMT+02:00 flosee : > When I install manually the following features > > /feature:install spring-aspects/3.2.14.RELEASE_1 > feature:install

Re: OSGi Compendium within a feature restarts the console

Have you read this one: http://felix.apache.org/documentation/tutorials-examples-and-presentations/apache-felix-osgi-faq.html#should-a-service-providerconsumer-bundle-be-packaged-with-its-service-api-packages Christian Schneider posted the link already above If you have a look at

Re: karaf-maven-plugin multiple outputs with classifiers

Thanks Alex for sharing this! Will you create a PR Jira for the targetFile change and a PR. Perhaps it could be merged upstream.

Re: Can a karaf command be a DS service?

But a DS component could reference org.apache.karaf.shell.api.console.Registry and register an object (perhaps this) that implements the interface org.apache.karaf.shell.api.console.Command. At least it works for me in my "dynamically translate Equinox CommandProvider commands to Karaf commands".

Re: osgi.ee version

orking again. Thank you for taking the time to try and > help me. Have a great day. > > On Tue, Jul 5, 2016 at 12:37 PM, Markus Rathgeb <maggu2...@gmail.com> wrote: >> >> Or you can use: >> bundle:capabilities 0 >> >> 2016-07-05 18:35 GMT+02:00

Re: osgi.ee version

Hi David, what about: bundle:headers 0 Does this contain the information we are looking for? e.g. Provide-Capability = osgi.ee;osgi.ee=OSGi/Minimum;version:List="1.0,1.1,1.2", osgi.ee;osgi.ee=JavaSE;version:List="1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7,1.8",

Re: osgi.ee version

Or you can use: bundle:capabilities 0 2016-07-05 18:35 GMT+02:00 Markus Rathgeb <maggu2...@gmail.com>: > Hi David, > what about: > bundle:headers 0 > > Does this contain the information we are looking for? > > e.g. > Provide-Capability = > osgi.ee;

Re: JAX-RS Annotations and Apache Karaf 4.0.5

The Karaf Features provided by Holger Staudacher are using bundles that package a lot of other bundles in a single one. If you don't want to have such very big bundles in your runtime and prefer using the separate bundles (to be reused by other ones, etc.) you can have a look at the Features I

Re: JAX-RS Annotations and Apache Karaf 4.0.5

Hi Scott, my knowledge about ECF, CXF, JAX-RS is very very small. In the past I need to get the OSGi JAX-RS of hstaudacher working in Karaf (at least to support Karaf Features for the Eclipse SmartHome project and openHAB etc.). The projects already exist and already use JAX-RS. I started using

Re: JAX-RS Annotations and Apache Karaf 4.0.5

Hi Benson, the whole message list could be found here: http://karaf.922171.n3.nabble.com/JAX-RS-Annotations-and-Apache-Karaf-4-0-5-td4047001.html#a4047014

Karaf: feature satisfy requirements

inal/jbosgi-xerces-3.1.0.Final.jar mvn:org.osgi/org.osgi.util.xml/1.0.1 What am I doing wrong? Best regards, Markus Rathgeb

Re: Karaf: feature satisfy requirements

Ah, okay, I assume it is caused by the missing Provide-Capability of the Equinox bundle that it provides that service. Could this information be added by some configuration file without modify the Equinox bundle itself? 2017-02-05 11:49 GMT+01:00 Markus Rathgeb <maggu2...@gmail.com>: &

Re: Karaf: feature satisfy requirements

>> Should I create a Jira + PR if it is working? > Sure, but it would be interesting to do a complete pass on the services > provided by each framework for completeness. You could have a look at: https://issues.apache.org/jira/browse/KARAF-4980

Re: Karaf: feature satisfy requirements

t; configuration. If some service are provided by default by the framework and > are missing, > you may want to raise a JIRA issue and provide a patch / pull request. > > 2017-02-05 12:05 GMT+01:00 Markus Rathgeb <maggu2...@gmail.com>: >> >> Ah, okay, I assume it is

Re: Karaf: feature satisfy requirements

quinox-capabilities=\ > > osgi.service;effective:=active;objectClass=javax.xml.parsers.SAXParserFactory > > I haven't tested the above, but hopefully you'll get the idea. It's similar > to what's done for the ${jre-${java.specification.version}}... > > 2017-02-06 9:16 GMT+01:00 M

K410: Exception caused by Jetty bug

Hi, after I changed some stuff to use the recent Karaf 4.1.0 I realized an error in my log (see below if you are interested in the whole message). The error has been cased by a bug in the "org.eclipse.jetty.websocket.server" bundle (SPI without no-arg constructor). The issue has already been

Re: K410: Exception caused by Jetty bug

Hi Achim, I have created the issues: * https://ops4j1.jira.com/browse/PAXWEB-1065 * https://issues.apache.org/jira/browse/KARAF-4990 Best regards, Markus

Re: K410: Exception caused by Jetty bug

> will take care of that Thank you Achim

Re: Karaf 4.0.5 prerequisite feature not installed with correct version

By the way: Also for Maven a version 1.0 generally means 1.0 or a later version, if 1.0 is not available. https://docs.oracle.com/middleware/1212/core/MAVEN/maven_version.htm#MAVEN402 2016-08-30 21:59 GMT+02:00 Jean-Baptiste Onofré : > By the way: it's the OSGi convention. The

Re: What does effective:=active mean?

Hi, > > osgi.service;effective:=active;objectClass=myService > IIRC have never seen "effective:=active" in the Provide-Capability section. I only know about in the Require-Capability. Are you sure this is required? At least it works if it is missing for "provide". Best regard, Markus

K406 breaks custom distribution on ARM

Hello, I created a custom Karaf distribution using Karaf 4.0.5 since the release of this version. The custom distribution is created on a x86_64 linux machine. It run it on x86 and arm linux machines for a while. Recently I switched to Karaf 4.0.6 and I realized no problem. But today I tried to

Re: K406 breaks custom distribution on ARM

tActivator(SecureAction.java:697) at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226) ... 11 more === Best regards, Markus 2016-09-14 21:20 GMT+02:00 Markus Rathgeb <maggu2...@gmail.com>: > Hello, > > I created a custom Karaf distribution using Karaf 4.0.5 since the

Re: How t configure Karaf to not look for newest SNAPSHOTs

Hi, I assume he wants to configure the local repository as the only one that provides snapshots. So snapshots from .m2 are used, but no lookup for newer remote provided versions is done.

Re: A way to extend/parent "assembly-property-edits.xml"

Hi Jens, about the "enhance the list of ... from its parent": Have you tried using combine.children or combine.self? I assume you want to use the option append. Have a look at here: https://maven.apache.org/pom.html#Plugins Best regards, Markus

Re: K406 breaks custom distribution on ARM

Hi JB, as written above K405 works fine. K406 doesn't work. Best regards, Markus

Re: K406 breaks custom distribution on ARM

Hi, > I don't remember we upgraded Jansi for 4.0.6. I gonna check and eventually > downgrade. I will let you know. Thank you. I also don't find a version bump. $ git diff karaf-4.0.5..karaf-4.0.6 | grep -i jansi import org.fusesource.jansi.AnsiConsole; 1.11 +

Re: Unable to resolve 'org.osgi.service.component.annotations'

Hi Jens, > So as I understood it the annotations should not be imported. Yes, there is no need to import the component service annotations. As already written, this annotations are used a compile time to generate the XML files for DS. Best regards, Markus

Re: A way to extend/parent "assembly-property-edits.xml"

Hi Jens, I run into that "property file edit single location" problem myself from time to time. I planed to create a patch for that but haven't found any time for this, yet. Best regards, Markus

Re: Is anybody using Jetty client from Karaf?

Will have a look at tomorrow, but I am pretty sure I am using the jetty client bundle in K408. Am 23.03.2017 21:20 schrieb "Leschke, Scott" : > *Sent this about 1.5 weeks ago. Thought I’d resend one more time just in > case there’s somebody out there using this.* > > > >

Re: Karaf running on ARM - RaspberryPi

Hello, the first problem you reported is known and has been already solved for K408. So, if you ewant to use Karaf on ARM, don't use K406 or K407 -- use K408 (or K410). Am 18.03.2017 15:57 schrieb "JT" : Hi all, I've got a couple of issues running Karaf on a

Re: Karaf Container 4.0.x / minimum configuration

Hi, do you use the OpenJDK or Oracle Java? On ARM the Oracle JVM works much better (performace) then the OpenJDK -- at the time I tested it. Best regards, Markus 2017-06-22 13:57 GMT+02:00 jljordan : > Hi JB, > > Thanks for your answer. > We use Debian 8 (Jessie) with

Re: wrap:mvn in offline mode

Hi, if I understand your use case correctly, you want to add "wrap" to "installedFeature". https://karaf.apache.org/manual/latest/#_plugin_configuration 2017-10-24 11:03 GMT+02:00 DERIES Sebastien : > Hey Everyone, > > > > I currently work on a custom karaf

Re: Event admin blacklisting?

AFAIK there is also "org.apache.felix.eventadmin.Timeout=0" to disable the timeout handling at all. Another approach would be that your event handlers only take the event and add it to a blocking queue (e.g. LinkedBlockingDeque). You could use another thread that handles the elements added to

Re: How do i change a single line in a custom distro file?

Have you already tried "assembly-property-edits.xml" in the "src/main/karaf" folder of your custom distribution? I don't find the official documentation, but you can found examples using a search engine of your choose ;)

Re: Aries JPA: The persistence unit has incomplete configuration and cannot be created.

Hi, > I'm suggesting to create a Jira at Aries, we will tackle that. > Has a Jira at Aries been created? Can you point me to?

Re: Feature verify error with Karaf 4.2.2

Can you try to remove "effective:=active" from the capabilitiy?

resolving org.apache.qpid.proton-j

Hi, I would like to use the bundle "org.apache.qpid.proton-j". I started a clean standard Karaf 4.2.1 distribution and installed the bundle: bundle:install mvn:org.apache.qpid/proton-j/0.31.0 The bundle has unsatisfied requirements: karaf@root()> bundle:diag 45 Proton-J (45) -

Re: Aries JAX-RS Whiteboard

Hi JB, can you please point me to the correct repositories? I cannot find your commits. Best regards, Markus

Re: Aries JAX-RS Whiteboard

Hi JB, as I'm creating the Aries JAXRS feature for Karaf, I'm currently using > the one from Aries. > could you share your feature? Best regards, Markus

Re: use JAXP compliant XML parser by OSGi service

Hi Tim, hi JB, sorry for not being clear enough... As written in my initial post / mail the call to "SAXParserFactory.newInstance();" works for me as expected. After reading https://osgi.org/javadoc/r4v41/org/osgi/util/xml/XMLParserActivator.html I just want to know * if anyone knows about a

Re: use JAXP compliant XML parser by OSGi service

I have found also this one: http://apache-sling.73963.n3.nabble.com/jaxb-OSGI-amp-com-sun-xml-bind-Cannot-be-resolved-and-overwritten-by-Boot-Delegation-td4046690.html As I am using a SAX parser I don't think I will run into some "OSGi-compatible concerning class loading" problems.. But WDYT,

use JAXP compliant XML parser by OSGi service

Hello, I (assume I) have some problems using a SAXParser "the OSGi way". Code like this is currently (Karaf 4.2.0 and Java 8) working: === final SAXParserFactory factory = SAXParserFactory.newInstance(); final SAXParser saxParser; try { saxParser = factory.newSAXParser(); } catch

Re: use JAXP compliant XML parser by OSGi service

Hi Tim, isn't the information of your link about the R7 spec similar to that one I posted in the first mail for R4.1? It does not work for me (see output of first mail). Or didn't I get your point? Best regards, Markus

Re: Bndtools & Karaf : the right way

> It think bndtools at least builds the jar on each save. (This should also be > true if you use the maven setup for your project instead of the workspace > one). I am not sure if it also deploys to the local repo but maybe it does as > it is a cheap operation if the jar is already built. You

Re: Karaf, Pax Web, Jetty, GzipHandler (compression)

:33 Uhr schrieb Jean-Baptiste Onofré : > > Hi Markus, > > Are you using jetty.xml in config property from org.ops4j.pax.web.cfg ? > Else your configuration won't be loaded in the Karaf Jetty connector. > > Regards > JB > > On 18/04/2019 11:36, Markus Rathgeb wrote

Karaf, Pax Web, Jetty, GzipHandler (compression)

Hi, I would like to use gzip compression for * my servlets registered using the "registerServlet" method of "HttpService" * for a handler that provides static content of a directory added by jetty.xml The programmatic registered servlets are the most important ones. Would be nice if there is one

Re: Karaf, Pax Web, Jetty, GzipHandler (compression)

d you try to add the GzipFilter ? > > You can register the GzipFilter as a Filter service (using the http > whiteboard pattern), providing mimeTypes and url-patterns as service > properties. > > Regards > JB > > On 18/04/2019 13:17, Markus Rathgeb wrote: > > To be clea

Re: Karaf, Pax Web, Jetty, GzipHandler (compression)

ect, you want to add the handler programmatically ? > not via the jetty.xml right ? > > Regards > JB > > On 18/04/2019 13:38, Markus Rathgeb wrote: > > The GzipFilter is deprecated for Jetty >8 and does not contain any > > logic anymore: > > https://github.com/

Re: Service Sisibility

Hi Tim, can you point me to the part of the spec that states that service configuration properties can be used to set such fields (e.g. target filter)? I just know that it works ;) Best regards, Markus Tim Ward schrieb am Mi., 15. Mai 2019, 15:45: > Declarative Services is amazing, so this is

Re: Karaf, Pax Web, Jetty: "some" client authentication

I assume I need to use a "Web Application" and cannot rely on servlets etc. https://osgi.org/specification/osgi.cmpn/7.0.0/service.war.html Any change to get this mixed with Declarative Service? Am Do., 16. Mai 2019 um 20:32 Uhr schrieb Markus Rathgeb : > > If this al

Karaf, Pax Web, Jetty: "some" client authentication

Hi, I assume there are different parties involved, so if this question should be raised on another mailing list, please can you point me to? I am using Karaf + Pax Web + Jetty. Currently I build a custom distribution that Pax Web configuration (org.ops4j.pax.web.cfg) contains also this lines:

Re: feature for jetty proxy

y-proxy should be part of the http/jetty feature. > > Regards > JB > > On 10/06/2019 10:04, Markus Rathgeb wrote: > > Hello, > > > > the Karaf distributions contains features for jetty. > > Mainly there are the jetty one in the standard feature repo and >

Re: feature for jetty proxy

Added a link below Am Mo., 10. Juni 2019 um 13:51 Uhr schrieb Markus Rathgeb : > > Hi JB, > > I will have a look at the Karaf ProxyService if it fits the need. > What I need to do is to create proxies dynamic and programmatic on > runtime on special user behaviour. > Some

feature for jetty proxy

Hello, the Karaf distributions contains features for jetty. Mainly there are the jetty one in the standard feature repo and pax-jetty in the pax web feature repo. Both feature repos does not contain a feature that provides the jetty-proxy bundle. With every Karaf bump I need to modify a feature

Re: feature for jetty proxy

Hi JB, > First, you can use the ProxyService directly to programmatically create > the proxies you need. I read the proxy service of the Karaf project but this does not fit to my use-case. I use a subclass of Jetty's proxy servlet because the "proxyTo" is not fixed. It depends on the caller of

Re: feature for jetty proxy

Thanks a lot (for both)! Am Mo., 10. Juni 2019 um 18:36 Uhr schrieb Jean-Baptiste Onofré : > > Hi Markus, > > I'm already added jetty-proxy in the Pax Web and Karaf features. > > I just mentioned a workaround waiting for new Pax Web/Karaf releases. > > Regards > JB >

Re: Karaf bump, Spring Framework CNF exception

I realized that there are two versions of the Spring Framework installed now. This has not been the case on Karaf 4.2.1. Is there some relationship to "Two versions of jetty"? Have there been some changes to the feature resolver? Am Mo., 20. Mai 2019 um 09:04 Uhr schrieb Markus Rathge

Karaf bump, Spring Framework CNF exception

Hi, I had to update a custom distribution that contains a bundle that is using the Spring Framework. Currently the distribution is using Karaf 4.2.1, so Spring Framework 5.0.8.RELEASE_1. After the bump Karaf 4.2.5 will be used and so Spring Framework 5.0.12.RELEASE_1. While doing the migration I

Re: Karaf bump, Spring Framework CNF exception

It seems to work after I used a version range that allows exactly one spring verion only. spring spring-web spring-tx spring-websocket mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.spring-messaging/${spring.version}

Re: Karaf bump, Spring Framework CNF exception

> > By the way, you don't need to install the spring-messaging bundle, you > > can use the spring-messaging feature directly. > > Thanks! The feature has not been as the "my-spring" (not the real > name) has been created initially. JBO, can you please point me to the definition of the

Re: Karaf bump, Spring Framework CNF exception

> By the way, you don't need to install the spring-messaging bundle, you > can use the spring-messaging feature directly. Thanks! The feature has not been as the "my-spring" (not the real name) has been created initially. > OK good, but I would like to understand who's bringing the different >

Re: Karaf, Pax Web, Jetty: "some" client authentication

a jetty.xml (in addition of the default one created > by Pax Web), then, you can use "VirtualHost" to deploy a servlet on a > specific connector. > > I blogged about this while ago (http://blog.nanthrax.net/?p=352). > > Regards > JB > > On 16/05/2019 08:12, Markus Rath

Re: Karaf, Pax Web, Jetty: "some" client authentication

If this already known (WRT to the following comment)? https://nierbeck.de/2013/01/bind-certain-web-applications-to-specific-httpconnectors/#comment-62 Am Do., 16. Mai 2019 um 20:26 Uhr schrieb Markus Rathgeb : > > Hi Łukasz, hi JB, > > thank you for that information. > &g

Re: Karaf Decanter log => mail

: > > Sure ! and thanks for your feedback ! > > Do you mind to create a corresponding Jira and assign to me ? Else I > will later today. > > Regards > JB > > On 08/07/2019 16:20, Markus Rathgeb wrote: > > Hi JB, > > > > sounds good. > > Thank you. &g

Re: Karaf Decanter log => mail

the > checker, adding an option to "always" send the alert, ignoring previous > ones. > > I imagine something like: > > log.level.warn.always= > > I do the change for Decanter 2.3.0 and I will cut the release asap. > > OK for you ? > > Regards

Re: Karaf, Pax Web, Jetty, GzipHandler (compression)

Solved for me! See:https://groups.google.com/d/topic/ops4j/U-uglsVkaMU/discussion I edited the jetty.xml and it seems the gzip handler is used for every servlet.

Johnzon JSON-B on OSGi

Hi, I posted my problem already to the Johnzon mailing list and have been told to ask the Karaf team. So please let me ask you (this should be no cross posting). See: https://lists.apache.org/thread.html/b2134d2002738d33a57a329966ef38563372613502947158358092fa@%3Cdev.johnzon.apache.org%3E I am

Re: Johnzon JSON-B on OSGi

u can add in a > feature for instance. > > What I propose to you is to create a features for that. > > Regards > JB > > On 15/09/2019 12:20, Markus Rathgeb wrote: > > Hi, > > > > I posted my problem already to the Johnzon mailing list and have been > > told

Re: Johnzon JSON-B on OSGi

m back on my working machine). Best regards, Markus > > We already did some "wrapped" bundles (for instance Aries JAXRS API) in > such case. > More than a bundle, it's maybe better to evaluate to provide such > capability at feature level. > > Regards > JB > >

Re: Johnzon JSON-B on OSGi

n at all, how can "Apache Geronimo JCDI Spec 2.0" be satisfied at all? Best regards, Markus Am Mo., 16. Sept. 2019 um 07:54 Uhr schrieb Jean-Baptiste Onofré : > > That's exactly my point: johnzon-jsonb should not expose johnzon > packages at all. > > Back on cap, for service loade

Re: Johnzon JSON-B on OSGi

nd its requirement for the Registrar) by resolving utils? Best regards, Markus Am Mo., 16. Sept. 2019 um 11:14 Uhr schrieb Markus Rathgeb : > > Hi again, > be back with all the information (hopefully) > > For JSON-P provided by Johnzon: > === > > bundle:install

Re: Karaf and Transaction Control Service Specification

I got it working while creating the features myself.

Re: Karaf and Transaction Control Service Specification

Hi, did you see my message? Is the feature still in progress or is it just me that did not find it? Am Mo., 22. Juli 2019 um 13:03 Uhr schrieb Markus Rathgeb : > > Hi JB, > > can you point me to the feature repositories I need to add to Karaf > 4.2.6 to use OSGi R7 transaction

  1   2   >