[jira] [Commented] (KARAF-6001) Upgrade to Pax Web 7.2.4 / Jetty 9.4.12.v20180830
[ https://issues.apache.org/jira/browse/KARAF-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676255#comment-16676255 ] ASF GitHub Bot commented on KARAF-6001: --- jbonofre opened a new pull request #645: [KARAF-6001] Upgrade to Pax Web 7.2.4 and Jetty 9.4.12.v20180830 URL: https://github.com/apache/karaf/pull/645 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to Pax Web 7.2.4 / Jetty 9.4.12.v20180830 > - > > Key: KARAF-6001 > URL: https://issues.apache.org/jira/browse/KARAF-6001 > Project: Karaf > Issue Type: New Feature > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6001) Upgrade to Pax Web 7.2.4 / Jetty 9.4.12.v20180830
[ https://issues.apache.org/jira/browse/KARAF-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6001: Summary: Upgrade to Pax Web 7.2.4 / Jetty 9.4.12.v20180830 (was: Upgrade to Pax Web 7.2.4 / Jetty) > Upgrade to Pax Web 7.2.4 / Jetty 9.4.12.v20180830 > - > > Key: KARAF-6001 > URL: https://issues.apache.org/jira/browse/KARAF-6001 > Project: Karaf > Issue Type: New Feature > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5772) HTTP proxy should be able to support several addresses with round-robin
[
https://issues.apache.org/jira/browse/KARAF-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676248#comment-16676248
]
Jean-Baptiste Onofré commented on KARAF-5772:
-
We can start with two balancing algorithms: round-robin and random. Then, we
can define a {{BalancingPolicy}} interface that the user can implement and use.
It would allow to support weight based or any other custom policy. Round-robin
and random will be implementation of this {{BalancingPolicy}}.
> HTTP proxy should be able to support several addresses with round-robin
> ---
>
> Key: KARAF-5772
> URL: https://issues.apache.org/jira/browse/KARAF-5772
> Project: Karaf
> Issue Type: Improvement
> Components: karaf
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: http, proxy
> Fix For: 4.2.2
>
>
> The Karaf HTTP proxy servlet should be able to round-robin or random pick up
> a target destination if several are provided.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5772) HTTP proxy should be able to support several addresses with round-robin
[ https://issues.apache.org/jira/browse/KARAF-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5772: Fix Version/s: 4.2.2 > HTTP proxy should be able to support several addresses with round-robin > --- > > Key: KARAF-5772 > URL: https://issues.apache.org/jira/browse/KARAF-5772 > Project: Karaf > Issue Type: Improvement > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: http, proxy > Fix For: 4.2.2 > > > The Karaf HTTP proxy servlet should be able to round-robin or random pick up > a target destination if several are provided. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5919) Be able to store Http Proxy list in order to keep configuration after restart
[
https://issues.apache.org/jira/browse/KARAF-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676243#comment-16676243
]
ASF GitHub Bot commented on KARAF-5919:
---
jbonofre closed pull request #644: [KARAF-5919] Be able to store Http Proxy
list in order to keep configuration after restart
URL: https://github.com/apache/karaf/pull/644
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/http/src/main/java/org/apache/karaf/http/core/ProxyService.java
b/http/src/main/java/org/apache/karaf/http/core/ProxyService.java
index 63d03fe858..c168a71c47 100644
--- a/http/src/main/java/org/apache/karaf/http/core/ProxyService.java
+++ b/http/src/main/java/org/apache/karaf/http/core/ProxyService.java
@@ -26,4 +26,6 @@
void removeProxy(String url) throws Exception;
+void initProxies();
+
}
diff --git
a/http/src/main/java/org/apache/karaf/http/core/internal/ProxyServiceImpl.java
b/http/src/main/java/org/apache/karaf/http/core/internal/ProxyServiceImpl.java
index 16e481f04a..0d4f061ca9 100644
---
a/http/src/main/java/org/apache/karaf/http/core/internal/ProxyServiceImpl.java
+++
b/http/src/main/java/org/apache/karaf/http/core/internal/ProxyServiceImpl.java
@@ -17,18 +17,31 @@
package org.apache.karaf.http.core.internal;
import org.apache.karaf.http.core.ProxyService;
+import org.osgi.service.cm.Configuration;
+import org.osgi.service.cm.ConfigurationAdmin;
import org.osgi.service.http.HttpService;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import java.io.IOException;
import java.util.*;
public class ProxyServiceImpl implements ProxyService {
+private static Logger LOG =
LoggerFactory.getLogger(ProxyServiceImpl.class.getName());
+
+protected static final String CONFIGURATION_PID = "org.apache.karaf.http";
+protected static final String CONFIGURATION_KEY = "proxies";
+
+private ConfigurationAdmin configurationAdmin;
private HttpService httpService;
private Map proxies;
-public ProxyServiceImpl(HttpService httpService) {
+public ProxyServiceImpl(HttpService httpService, ConfigurationAdmin
configurationAdmin) {
this.httpService = httpService;
+this.configurationAdmin = configurationAdmin;
this.proxies = new HashMap<>();
+initProxies();
}
@Override
@@ -38,15 +51,115 @@ public ProxyServiceImpl(HttpService httpService) {
@Override
public void addProxy(String url, String proxyTo) throws Exception {
-ProxyServlet proxyServlet = new ProxyServlet();
-proxyServlet.setProxyTo(proxyTo);
-httpService.registerServlet(url, proxyServlet, new Hashtable(), null);
-proxies.put(url, proxyTo);
+addProxyInternal(url, proxyTo);
+updateConfiguration();
}
@Override
public void removeProxy(String url) throws Exception {
+LOG.debug("removing proxy alias: " + url);
httpService.unregister(url);
proxies.remove(url);
+updateConfiguration();
+}
+
+@Override
+public void initProxies() {
+LOG.debug("unregistering and registering all configured proxies");
+unregisterAllProxies();
+initProxiesInternal();
+}
+
+private void initProxiesInternal() {
+try {
+Configuration configuration = getConfiguration();
+Dictionary configurationProperties =
configuration.getProperties();
+String[] proxiesArray =
getConfiguredProxyArray(configurationProperties);
+if (proxiesArray != null) {
+for (String proxyPair : proxiesArray) {
+String[] split = proxyPair.split(" ", 2);
+if (split.length == 2) {
+String from = split[0].trim();
+String to = split[1].trim();
+if (from.length() > 0 && to.length() > 0) {
+addProxyInternal(from, to);
+}
+}
+}
+}
+} catch (Exception e) {
+LOG.error("unable to initialize proxies: " + e.getMessage());
+}
+}
+
+private void addProxyInternal(String url, String proxyTo) {
+LOG.debug("adding proxy alias: " + url + ", proxied to: " + proxyTo);
+try {
+ProxyServlet proxyServlet = new ProxyServlet();
+proxyServlet.setProxyTo(proxyTo);
+httpService.registerServlet(url, proxyServlet, new Hashtable(),
null);
+proxies.put(url, proxyTo);
+} catch (Exception e) {
+LOG.error("could not add proxy alias: " + url + ", proxied to: " +
proxyTo + ", reason: " + e.getMessage());
+
[jira] [Commented] (KARAF-5919) Be able to store Http Proxy list in order to keep configuration after restart
[ https://issues.apache.org/jira/browse/KARAF-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676245#comment-16676245 ] ASF subversion and git services commented on KARAF-5919: Commit 0290cc2d465a915c39e43516d8e8cee148d2bc3c in karaf's branch refs/heads/master from [~j...@nanthrax.net] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=0290cc2 ] Merge pull request #644 from sjhiggs/KARAF-5919 [KARAF-5919] Be able to store Http Proxy list in order to keep configuration after restart > Be able to store Http Proxy list in order to keep configuration after restart > - > > Key: KARAF-5919 > URL: https://issues.apache.org/jira/browse/KARAF-5919 > Project: Karaf > Issue Type: Improvement > Components: karaf >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: http, proxy > Fix For: 4.2.2 > > > The Http proxy feature provide a command to manage a list of proxy > configuration but this list is in memory stored. It would be nice if we could > persist this list to avoid to reconfigure it after restart the Karaf instance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-5919) Be able to store Http Proxy list in order to keep configuration after restart
[ https://issues.apache.org/jira/browse/KARAF-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-5919. - Resolution: Fixed > Be able to store Http Proxy list in order to keep configuration after restart > - > > Key: KARAF-5919 > URL: https://issues.apache.org/jira/browse/KARAF-5919 > Project: Karaf > Issue Type: Improvement > Components: karaf >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: http, proxy > Fix For: 4.2.2 > > > The Http proxy feature provide a command to manage a list of proxy > configuration but this list is in memory stored. It would be nice if we could > persist this list to avoid to reconfigure it after restart the Karaf instance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5919) Be able to store Http Proxy list in order to keep configuration after restart
[ https://issues.apache.org/jira/browse/KARAF-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676244#comment-16676244 ] ASF subversion and git services commented on KARAF-5919: Commit 0241a192f03699e93f9de39e9aaa4c50b97b71c4 in karaf's branch refs/heads/master from [~shiggs] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=0241a19 ] [KARAF-5919] Be able to store Http Proxy list in order to keep configuration after restart > Be able to store Http Proxy list in order to keep configuration after restart > - > > Key: KARAF-5919 > URL: https://issues.apache.org/jira/browse/KARAF-5919 > Project: Karaf > Issue Type: Improvement > Components: karaf >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: http, proxy > Fix For: 4.2.2 > > > The Http proxy feature provide a command to manage a list of proxy > configuration but this list is in memory stored. It would be nice if we could > persist this list to avoid to reconfigure it after restart the Karaf instance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5919) Be able to store Http Proxy list in order to keep configuration after restart
[ https://issues.apache.org/jira/browse/KARAF-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16676246#comment-16676246 ] ASF subversion and git services commented on KARAF-5919: Commit 0290cc2d465a915c39e43516d8e8cee148d2bc3c in karaf's branch refs/heads/master from [~j...@nanthrax.net] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=0290cc2 ] Merge pull request #644 from sjhiggs/KARAF-5919 [KARAF-5919] Be able to store Http Proxy list in order to keep configuration after restart > Be able to store Http Proxy list in order to keep configuration after restart > - > > Key: KARAF-5919 > URL: https://issues.apache.org/jira/browse/KARAF-5919 > Project: Karaf > Issue Type: Improvement > Components: karaf >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: http, proxy > Fix For: 4.2.2 > > > The Http proxy feature provide a command to manage a list of proxy > configuration but this list is in memory stored. It would be nice if we could > persist this list to avoid to reconfigure it after restart the Karaf instance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KARAF-4375) IllegalArgumentException: invalid topic exception
[ https://issues.apache.org/jira/browse/KARAF-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Leschke closed KARAF-4375. > IllegalArgumentException: invalid topic exception > - > > Key: KARAF-4375 > URL: https://issues.apache.org/jira/browse/KARAF-4375 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-1.0.1, decanter-1.1.0 > Environment: JVM 1.8.x Decanter 1.0.1 >Reporter: Scott Leschke >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: decanter-1.1.0 > > > Per Christian Schneider, the Decanter LogAppender bundle throws > IllegalArgumentException: invalid topic if the name of the logger is null or > empty. I've confirmed that this is in fact the case.. > java.lang.IllegalArgumentException: invalid topic: decanter/collect/log/ > at > org.osgi.service.event.Event.validateTopicName(Event.java:209)[3:org.apache.karaf.services.eventadmin:4.0.4] > at > org.osgi.service.event.Event.(Event.java:59)[3:org.apache.karaf.services.eventadmin:4.0.4] > at > org.apache.karaf.decanter.collector.log.LogAppender.appendInternal(LogAppender.java:89)[279:org.apache.karaf.decanter.collector.log:1.0.1] > ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KARAF-5078) Shell crash
[ https://issues.apache.org/jira/browse/KARAF-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Leschke closed KARAF-5078. > Shell crash > --- > > Key: KARAF-5078 > URL: https://issues.apache.org/jira/browse/KARAF-5078 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 > Environment: Windows 7 >Reporter: Scott Leschke >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 4.1.2, 4.2.0.M1 > > Attachments: testkaraf-5078.zip > > > Karaf shell behaves badly in Windows console. It appears better than 4.1.0 > but still a problem. Command string start out red and turns dark blue while > typing become virtually unreadable. > Most problematic though is that the shell crashed and brought down Karaf as a > result of entering the word "bundle" at the console prompt. After the > following tracebacks, the Felix shutdown sequence is displayed in the log. > 2017-03-31T09:56:38,363 | ERROR | Karaf local console user karaf | ShellUtil > | 42 - org.apache.karaf.shell.core - 4.1.1 | Exception > caught while executing command > java.lang.NumberFormatException: For input string: "1B" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > ~[?:?] > at java.lang.Integer.parseInt(Integer.java:580) ~[?:?] > at java.lang.Integer.parseInt(Integer.java:615) ~[?:?] > at > org.jline.terminal.impl.jna.win.WindowsAnsiOutputStream.write(WindowsAnsiOutputStream.java:189) > ~[?:?] > at java.io.FilterOutputStream.write(FilterOutputStream.java:125) ~[?:?] > at > java.nio.channels.Channels$WritableByteChannelImpl.write(Channels.java:458) > ~[?:?] > at org.apache.felix.gogo.runtime.Pipe$MultiChannel.write(Pipe.java:644) > ~[42:org.apache.karaf.shell.core:4.1.1] > at java.nio.channels.Channels.writeFullyImpl(Channels.java:78) ~[?:?] > at java.nio.channels.Channels.writeFully(Channels.java:101) ~[?:?] > at java.nio.channels.Channels.access$000(Channels.java:61) ~[?:?] > at java.nio.channels.Channels$1.write(Channels.java:174) ~[?:?] > at java.io.PrintStream.write(PrintStream.java:480) ~[?:?] > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) ~[?:?] > at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) > ~[?:?] > at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104) ~[?:?] > at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185) > ~[?:?] > at java.io.PrintStream.write(PrintStream.java:527) ~[?:?] > at java.io.PrintStream.print(PrintStream.java:669) ~[?:?] > at java.io.PrintStream.println(PrintStream.java:806) ~[?:?] > at org.apache.felix.gogo.jline.Posix._main(Posix.java:134) > ~[42:org.apache.karaf.shell.core:4.1.1] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[?:?] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[?:?] > at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?] > at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:136) > ~[42:org.apache.karaf.shell.core:4.1.1] > at > org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.lambda$wrap$0(SessionFactoryImpl.java:195) > ~[42:org.apache.karaf.shell.core:4.1.1] > at > org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.execute(SessionFactoryImpl.java:241) > [42:org.apache.karaf.shell.core:4.1.1] > at > org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68) > [42:org.apache.karaf.shell.core:4.1.1] > at > org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86) > [42:org.apache.karaf.shell.core:4.1.1] > at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:560) > [42:org.apache.karaf.shell.core:4.1.1] > at > org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:486) > [42:org.apache.karaf.shell.core:4.1.1] > at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:375) > [42:org.apache.karaf.shell.core:4.1.1] > at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) > [42:org.apache.karaf.shell.core:4.1.1] > at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) > [42:org.apache.karaf.shell.core:4.1.1] > at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) > [42:org.apache.karaf.shell.core:4.1.1] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [?:?] > at >
[jira] [Assigned] (KARAF-6003) IllegalStateException: Need active coordination - cannot use JPA and Jasypt
[
https://issues.apache.org/jira/browse/KARAF-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-6003:
---
Assignee: Jean-Baptiste Onofré
> IllegalStateException: Need active coordination - cannot use JPA and Jasypt
> ---
>
> Key: KARAF-6003
> URL: https://issues.apache.org/jira/browse/KARAF-6003
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Marek Łuniewski
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.2.2
>
>
> In version 4.2.1 one cannot use JPA because it causes
> java.lang.IllegalStateException: Need active coordination. After my
> investigation I have found that it is caused because proxy service is not
> created properly. When someone use JPA in the same bundle, as in Karaf tests,
> it works fine. But problem occurs when using osgi service and osgi reference.
> Downgrading to version 4.1.5 of Karaf results in no possibility of using
> Jasypt (to protect passwords) [using:
> org.jasypt.encryption.pbe.StandardPBEStringEncryptor]. It does not decrypt
> passwords having marks ENC(...).
> I found that upgrading Blueprint fixes problem, so that JPA and Jasypt works
> perfectly. I know that sometime ago ticket on Camel blocked Blueprint
> upgrade. It was: https://issues.apache.org/jira/browse/CAMEL-12570. Currently
> this ticket is closed.
> Patch (for current code, which is version 4.2.1) is:
> {code:java}
> diff --git a/pom.xml b/pom.xml
> index 3d314da48c..f049b7ff86 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -218,10 +218,11 @@
> 1.0.0
>
> 1.0.0
> 1.0.1
> - 1.9.0
> + 1.10.0
>
> 1.0.0
> - 1.2.0
> - 1.0.1
> + 1.3.0
> + 1.1.1
> +
> 1.0.1
>
> 0.6.0
>
> 0.4.0
> 1.1.5
> {code}
> and
> {code:java}
> diff --git a/assemblies/features/standard/src/main/feature/feature.xml
> b/assemblies/features/standard/src/main/feature/feature.xml
> index d19b87eb00..1813b2a0a5 100644
> --- a/assemblies/features/standard/src/main/feature/feature.xml
> +++ b/assemblies/features/standard/src/main/feature/feature.xml
> @@ -1429,7 +1429,7 @@ org.apache.felix.eventadmin.AddSubject=true
> blueprint inside web-bundle containers" version="${project.version}">
> war
> aries-blueprint
> -
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.web.version}
> +
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.webosgi.version}
>
>
> version="${pax.url.version}">
> {code}
> Hope it helps.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6003) IllegalStateException: Need active coordination - cannot use JPA and Jasypt
[
https://issues.apache.org/jira/browse/KARAF-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-6003:
Priority: Blocker (was: Critical)
> IllegalStateException: Need active coordination - cannot use JPA and Jasypt
> ---
>
> Key: KARAF-6003
> URL: https://issues.apache.org/jira/browse/KARAF-6003
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Marek Łuniewski
>Assignee: Jean-Baptiste Onofré
>Priority: Blocker
> Fix For: 4.2.2
>
>
> In version 4.2.1 one cannot use JPA because it causes
> java.lang.IllegalStateException: Need active coordination. After my
> investigation I have found that it is caused because proxy service is not
> created properly. When someone use JPA in the same bundle, as in Karaf tests,
> it works fine. But problem occurs when using osgi service and osgi reference.
> Downgrading to version 4.1.5 of Karaf results in no possibility of using
> Jasypt (to protect passwords) [using:
> org.jasypt.encryption.pbe.StandardPBEStringEncryptor]. It does not decrypt
> passwords having marks ENC(...).
> I found that upgrading Blueprint fixes problem, so that JPA and Jasypt works
> perfectly. I know that sometime ago ticket on Camel blocked Blueprint
> upgrade. It was: https://issues.apache.org/jira/browse/CAMEL-12570. Currently
> this ticket is closed.
> Patch (for current code, which is version 4.2.1) is:
> {code:java}
> diff --git a/pom.xml b/pom.xml
> index 3d314da48c..f049b7ff86 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -218,10 +218,11 @@
> 1.0.0
>
> 1.0.0
> 1.0.1
> - 1.9.0
> + 1.10.0
>
> 1.0.0
> - 1.2.0
> - 1.0.1
> + 1.3.0
> + 1.1.1
> +
> 1.0.1
>
> 0.6.0
>
> 0.4.0
> 1.1.5
> {code}
> and
> {code:java}
> diff --git a/assemblies/features/standard/src/main/feature/feature.xml
> b/assemblies/features/standard/src/main/feature/feature.xml
> index d19b87eb00..1813b2a0a5 100644
> --- a/assemblies/features/standard/src/main/feature/feature.xml
> +++ b/assemblies/features/standard/src/main/feature/feature.xml
> @@ -1429,7 +1429,7 @@ org.apache.felix.eventadmin.AddSubject=true
> blueprint inside web-bundle containers" version="${project.version}">
> war
> aries-blueprint
> -
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.web.version}
> +
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.webosgi.version}
>
>
> version="${pax.url.version}">
> {code}
> Hope it helps.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6003) IllegalStateException: Need active coordination - cannot use JPA and Jasypt
[
https://issues.apache.org/jira/browse/KARAF-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16675425#comment-16675425
]
Jean-Baptiste Onofré commented on KARAF-6003:
-
Let me double check the issue caused by this upgrade.
> IllegalStateException: Need active coordination - cannot use JPA and Jasypt
> ---
>
> Key: KARAF-6003
> URL: https://issues.apache.org/jira/browse/KARAF-6003
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Marek Łuniewski
>Priority: Critical
> Fix For: 4.2.2
>
>
> In version 4.2.1 one cannot use JPA because it causes
> java.lang.IllegalStateException: Need active coordination. After my
> investigation I have found that it is caused because proxy service is not
> created properly. When someone use JPA in the same bundle, as in Karaf tests,
> it works fine. But problem occurs when using osgi service and osgi reference.
> Downgrading to version 4.1.5 of Karaf results in no possibility of using
> Jasypt (to protect passwords) [using:
> org.jasypt.encryption.pbe.StandardPBEStringEncryptor]. It does not decrypt
> passwords having marks ENC(...).
> I found that upgrading Blueprint fixes problem, so that JPA and Jasypt works
> perfectly. I know that sometime ago ticket on Camel blocked Blueprint
> upgrade. It was: https://issues.apache.org/jira/browse/CAMEL-12570. Currently
> this ticket is closed.
> Patch (for current code, which is version 4.2.1) is:
> {code:java}
> diff --git a/pom.xml b/pom.xml
> index 3d314da48c..f049b7ff86 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -218,10 +218,11 @@
> 1.0.0
>
> 1.0.0
> 1.0.1
> - 1.9.0
> + 1.10.0
>
> 1.0.0
> - 1.2.0
> - 1.0.1
> + 1.3.0
> + 1.1.1
> +
> 1.0.1
>
> 0.6.0
>
> 0.4.0
> 1.1.5
> {code}
> and
> {code:java}
> diff --git a/assemblies/features/standard/src/main/feature/feature.xml
> b/assemblies/features/standard/src/main/feature/feature.xml
> index d19b87eb00..1813b2a0a5 100644
> --- a/assemblies/features/standard/src/main/feature/feature.xml
> +++ b/assemblies/features/standard/src/main/feature/feature.xml
> @@ -1429,7 +1429,7 @@ org.apache.felix.eventadmin.AddSubject=true
> blueprint inside web-bundle containers" version="${project.version}">
> war
> aries-blueprint
> -
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.web.version}
> +
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.webosgi.version}
>
>
> version="${pax.url.version}">
> {code}
> Hope it helps.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6003) IllegalStateException: Need active coordination - cannot use JPA and Jasypt
[
https://issues.apache.org/jira/browse/KARAF-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-6003:
Fix Version/s: 4.2.2
> IllegalStateException: Need active coordination - cannot use JPA and Jasypt
> ---
>
> Key: KARAF-6003
> URL: https://issues.apache.org/jira/browse/KARAF-6003
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Marek Łuniewski
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.2.2
>
>
> In version 4.2.1 one cannot use JPA because it causes
> java.lang.IllegalStateException: Need active coordination. After my
> investigation I have found that it is caused because proxy service is not
> created properly. When someone use JPA in the same bundle, as in Karaf tests,
> it works fine. But problem occurs when using osgi service and osgi reference.
> Downgrading to version 4.1.5 of Karaf results in no possibility of using
> Jasypt (to protect passwords) [using:
> org.jasypt.encryption.pbe.StandardPBEStringEncryptor]. It does not decrypt
> passwords having marks ENC(...).
> I found that upgrading Blueprint fixes problem, so that JPA and Jasypt works
> perfectly. I know that sometime ago ticket on Camel blocked Blueprint
> upgrade. It was: https://issues.apache.org/jira/browse/CAMEL-12570. Currently
> this ticket is closed.
> Patch (for current code, which is version 4.2.1) is:
> {code:java}
> diff --git a/pom.xml b/pom.xml
> index 3d314da48c..f049b7ff86 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -218,10 +218,11 @@
> 1.0.0
>
> 1.0.0
> 1.0.1
> - 1.9.0
> + 1.10.0
>
> 1.0.0
> - 1.2.0
> - 1.0.1
> + 1.3.0
> + 1.1.1
> +
> 1.0.1
>
> 0.6.0
>
> 0.4.0
> 1.1.5
> {code}
> and
> {code:java}
> diff --git a/assemblies/features/standard/src/main/feature/feature.xml
> b/assemblies/features/standard/src/main/feature/feature.xml
> index d19b87eb00..1813b2a0a5 100644
> --- a/assemblies/features/standard/src/main/feature/feature.xml
> +++ b/assemblies/features/standard/src/main/feature/feature.xml
> @@ -1429,7 +1429,7 @@ org.apache.felix.eventadmin.AddSubject=true
> blueprint inside web-bundle containers" version="${project.version}">
> war
> aries-blueprint
> -
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.web.version}
> +
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.webosgi.version}
>
>
> version="${pax.url.version}">
> {code}
> Hope it helps.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5919) Be able to store Http Proxy list in order to keep configuration after restart
[ https://issues.apache.org/jira/browse/KARAF-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16675374#comment-16675374 ] ASF GitHub Bot commented on KARAF-5919: --- sjhiggs opened a new pull request #644: [KARAF-5919] Be able to store Http Proxy list in order to keep configuration after restart URL: https://github.com/apache/karaf/pull/644 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Be able to store Http Proxy list in order to keep configuration after restart > - > > Key: KARAF-5919 > URL: https://issues.apache.org/jira/browse/KARAF-5919 > Project: Karaf > Issue Type: Improvement > Components: karaf >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Labels: http, proxy > Fix For: 4.2.2 > > > The Http proxy feature provide a command to manage a list of proxy > configuration but this list is in memory stored. It would be nice if we could > persist this list to avoid to reconfigure it after restart the Karaf instance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6003) IllegalStateException: Need active coordination - cannot use JPA and Jasypt
[
https://issues.apache.org/jira/browse/KARAF-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marek Łuniewski updated KARAF-6003:
---
Component/s: karaf
> IllegalStateException: Need active coordination - cannot use JPA and Jasypt
> ---
>
> Key: KARAF-6003
> URL: https://issues.apache.org/jira/browse/KARAF-6003
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Marek Łuniewski
>Priority: Critical
>
> In version 4.2.1 one cannot use JPA because it causes
> java.lang.IllegalStateException: Need active coordination. After my
> investigation I have found that it is caused because proxy service is not
> created properly. When someone use JPA in the same bundle, as in Karaf tests,
> it works fine. But problem occurs when using osgi service and osgi reference.
> Downgrading to version 4.1.5 of Karaf results in no possibility of using
> Jasypt (to protect passwords) [using:
> org.jasypt.encryption.pbe.StandardPBEStringEncryptor]. It does not decrypt
> passwords having marks ENC(...).
> I found that upgrading Blueprint fixes problem, so that JPA and Jasypt works
> perfectly. I know that sometime ago ticket on Camel blocked Blueprint
> upgrade. It was: https://issues.apache.org/jira/browse/CAMEL-12570. Currently
> this ticket is closed.
> Patch (for current code, which is version 4.2.1) is:
> {code:java}
> diff --git a/pom.xml b/pom.xml
> index 3d314da48c..f049b7ff86 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -218,10 +218,11 @@
> 1.0.0
>
> 1.0.0
> 1.0.1
> - 1.9.0
> + 1.10.0
>
> 1.0.0
> - 1.2.0
> - 1.0.1
> + 1.3.0
> + 1.1.1
> +
> 1.0.1
>
> 0.6.0
>
> 0.4.0
> 1.1.5
> {code}
> and
> {code:java}
> diff --git a/assemblies/features/standard/src/main/feature/feature.xml
> b/assemblies/features/standard/src/main/feature/feature.xml
> index d19b87eb00..1813b2a0a5 100644
> --- a/assemblies/features/standard/src/main/feature/feature.xml
> +++ b/assemblies/features/standard/src/main/feature/feature.xml
> @@ -1429,7 +1429,7 @@ org.apache.felix.eventadmin.AddSubject=true
> blueprint inside web-bundle containers" version="${project.version}">
> war
> aries-blueprint
> -
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.web.version}
> +
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.webosgi.version}
>
>
> version="${pax.url.version}">
> {code}
> Hope it helps.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6003) IllegalStateException: Need active coordination - cannot use JPA and Jasypt
[
https://issues.apache.org/jira/browse/KARAF-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marek Łuniewski updated KARAF-6003:
---
Description:
In version 4.2.1 one cannot use JPA because it causes
java.lang.IllegalStateException: Need active coordination. After my
investigation I have found that it is caused because proxy service is not
created properly. When someone use JPA in the same bundle, as in Karaf tests,
it works fine. But problem occurs when using osgi service and osgi reference.
Downgrading to version 4.1.5 of Karaf results in no possibility of using Jasypt
(to protect passwords) [using:
org.jasypt.encryption.pbe.StandardPBEStringEncryptor]. It does not decrypt
passwords having marks ENC(...).
I found that upgrading Blueprint fixes problem, so that JPA and Jasypt works
perfectly. I know that sometime ago ticket on Camel blocked Blueprint upgrade.
It was: https://issues.apache.org/jira/browse/CAMEL-12570. Currently this
ticket is closed.
Patch (for current code, which is version 4.2.1) is:
{code:java}
diff --git a/pom.xml b/pom.xml
index 3d314da48c..f049b7ff86 100644
--- a/pom.xml
+++ b/pom.xml
@@ -218,10 +218,11 @@
1.0.0
1.0.0
1.0.1
- 1.9.0
+ 1.10.0
1.0.0
- 1.2.0
- 1.0.1
+ 1.3.0
+ 1.1.1
+
1.0.1
0.6.0
0.4.0
1.1.5
{code}
and
{code:java}
diff --git a/assemblies/features/standard/src/main/feature/feature.xml
b/assemblies/features/standard/src/main/feature/feature.xml
index d19b87eb00..1813b2a0a5 100644
--- a/assemblies/features/standard/src/main/feature/feature.xml
+++ b/assemblies/features/standard/src/main/feature/feature.xml
@@ -1429,7 +1429,7 @@ org.apache.felix.eventadmin.AddSubject=true
blueprint inside web-bundle containers" version="${project.version}">
war
aries-blueprint
-
mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.web.version}
+
mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.webosgi.version}
{code}
Hope it helps.
was:
In version 4.2.1 one cannot use JPA because it causes
java.lang.IllegalStateException: Need active coordination. In my investigation
it is caused because proxy service is not created properly. When someone use
JPA in the same bundle, as in Karaf tests, it works fine. But problem occurs
when using osgi service and osgi reference.
Downgrading to version 4.1.5 of Karaf results in no possibility of using Jasypt
(to protect passwords) [using:
org.jasypt.encryption.pbe.StandardPBEStringEncryptor]. It does not decrypt
passwords having marks ENC(...).
I found that upgrading Blueprint fixes problem, so that JPA and Jasypt works
perfectly. I know that sometime ago ticket on Camel blocked Blueprint upgrade.
It was: https://issues.apache.org/jira/browse/CAMEL-12570. Currently this
ticket is closed.
Patch (for current code, which is version 4.2.1) is:
{code:java}
diff --git a/pom.xml b/pom.xml
index 3d314da48c..f049b7ff86 100644
--- a/pom.xml
+++ b/pom.xml
@@ -218,10 +218,11 @@
1.0.0
1.0.0
1.0.1
- 1.9.0
+ 1.10.0
1.0.0
- 1.2.0
- 1.0.1
+ 1.3.0
+ 1.1.1
+
1.0.1
0.6.0
0.4.0
1.1.5
{code}
and
{code:java}
diff --git a/assemblies/features/standard/src/main/feature/feature.xml
b/assemblies/features/standard/src/main/feature/feature.xml
index d19b87eb00..1813b2a0a5 100644
--- a/assemblies/features/standard/src/main/feature/feature.xml
+++ b/assemblies/features/standard/src/main/feature/feature.xml
@@ -1429,7 +1429,7 @@ org.apache.felix.eventadmin.AddSubject=true
blueprint inside web-bundle containers" version="${project.version}">
war
aries-blueprint
-
mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.web.version}
+
mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.webosgi.version}
{code}
Hope it helps.
> IllegalStateException: Need active coordination - cannot use JPA and Jasypt
> ---
>
> Key: KARAF-6003
> URL: https://issues.apache.org/jira/browse/KARAF-6003
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.2.1
>Reporter: Marek Łuniewski
>Priority: Critical
>
> In version 4.2.1 one cannot use JPA because it causes
> java.lang.IllegalStateException: Need active coordination. After my
> investigation I have found that it is caused because proxy service is not
> created properly. When someone use JPA in the same bundle, as in Karaf tests,
> it works fine. But problem occurs when using osgi service and osgi reference.
> Downgrading to version
[jira] [Created] (KARAF-6003) IllegalStateException: Need active coordination - cannot use JPA and Jasypt
Marek Łuniewski created KARAF-6003:
--
Summary: IllegalStateException: Need active coordination - cannot
use JPA and Jasypt
Key: KARAF-6003
URL: https://issues.apache.org/jira/browse/KARAF-6003
Project: Karaf
Issue Type: Bug
Affects Versions: 4.2.1
Reporter: Marek Łuniewski
In version 4.2.1 one cannot use JPA because it causes
java.lang.IllegalStateException: Need active coordination. In my investigation
it is caused because proxy service is not created properly. When someone use
JPA in the same bundle, as in Karaf tests, it works fine. But problem occurs
when using osgi service and osgi reference.
Downgrading to version 4.1.5 of Karaf results in no possibility of using Jasypt
(to protect passwords) [using:
org.jasypt.encryption.pbe.StandardPBEStringEncryptor]. It does not decrypt
passwords having marks ENC(...).
I found that upgrading Blueprint fixes problem, so that JPA and Jasypt works
perfectly. I know that sometime ago ticket on Camel blocked Blueprint upgrade.
It was: https://issues.apache.org/jira/browse/CAMEL-12570. Currently this
ticket is closed.
Patch (for current code, which is version 4.2.1) is:
{code:java}
diff --git a/pom.xml b/pom.xml
index 3d314da48c..f049b7ff86 100644
--- a/pom.xml
+++ b/pom.xml
@@ -218,10 +218,11 @@
1.0.0
1.0.0
1.0.1
- 1.9.0
+ 1.10.0
1.0.0
- 1.2.0
- 1.0.1
+ 1.3.0
+ 1.1.1
+
1.0.1
0.6.0
0.4.0
1.1.5
{code}
and
{code:java}
diff --git a/assemblies/features/standard/src/main/feature/feature.xml
b/assemblies/features/standard/src/main/feature/feature.xml
index d19b87eb00..1813b2a0a5 100644
--- a/assemblies/features/standard/src/main/feature/feature.xml
+++ b/assemblies/features/standard/src/main/feature/feature.xml
@@ -1429,7 +1429,7 @@ org.apache.felix.eventadmin.AddSubject=true
blueprint inside web-bundle containers" version="${project.version}">
war
aries-blueprint
-
mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.web.version}
+
mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.webosgi.version}
{code}
Hope it helps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6000) Add direct resource repositories support
[
https://issues.apache.org/jira/browse/KARAF-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16675149#comment-16675149
]
Jean-Baptiste Onofré commented on KARAF-6000:
-
The first idea is actually "dynamic" resource repositories (with dedicated
commands). Thanks for the explanation about resolving the deployment each time
we change the resource repositories set (adding/removing a repository).
About the "alternative to features", it's a rough idea, and I don't want to
fully remove feature. It's more to give some "OSGi closer" way to deal with
bundles/applications. I like the idea of command converting a features
repository as resource repository, eventually with verbose output. It would
give details about features values for users.
> Add direct resource repositories support
>
>
> Key: KARAF-6000
> URL: https://issues.apache.org/jira/browse/KARAF-6000
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> Since OSGi R6, the "new" bundle repository spec allows to directly leverage
> any requirement/capability to do the bundle resolution.
> We already support this via the features (using {{resourceRepository}} with
> json or XML in {{etc/org.apache.karaf.features.cfg}}. I think it would be
> great to have a complete alternative to features using bundle repository. We
> could introduce a minimal feature set (just for the bootstrapping) as we have
> today, but delegating to {{etc/org.apache.karaf.repository.cfg}} for resource
> repositories and using them for resolution.
> We could also provide specific commands to manipulate the bundle repositories
> (like add, remove, as we have for features repositories).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-6002) Add websocket appender
Jean-Baptiste Onofré created KARAF-6002: --- Summary: Add websocket appender Key: KARAF-6002 URL: https://issues.apache.org/jira/browse/KARAF-6002 Project: Karaf Issue Type: New Feature Components: decanter Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: decanter-2.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-6001) Upgrade to Pax Web 7.2.4 / Jetty
Jean-Baptiste Onofré created KARAF-6001: --- Summary: Upgrade to Pax Web 7.2.4 / Jetty Key: KARAF-6001 URL: https://issues.apache.org/jira/browse/KARAF-6001 Project: Karaf Issue Type: New Feature Components: karaf Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6000) Add direct resource repositories support
[
https://issues.apache.org/jira/browse/KARAF-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674803#comment-16674803
]
Guillaume Nodet commented on KARAF-6000:
Not exactly sure to understand how far you want to go.
Adding / removing resource repository is not a problem. Currently, the
"globalRepository" is considered static, i.e. it's only read when the
features-core bundle is started. If we want to make is more dynamic and have
the ability to add / remove repositories at runtime, we need to ensure we
resolve the deployment again when a repository is removed / added, or that we
force the uninstallation of the resources that come from that repository in
order to make sure we always stay consistent.
About the "complete alternative to features": at runtime, a feature is
translated into a resource, but not a bundle resource, so we could translate a
feature repository into a resource repository very easily. That said, a lot of
things that are built into features can't be modelled just using bundles as
resources. I think one good thing would be to have a command that translate a
feature or a feature repository into a resource repository so that we can have
a better idea of how things are modelled and how verbose/complex it would be to
achieve the same without features (I'm thinking about conditionals, the
dependent flag, etc...).
> Add direct resource repositories support
>
>
> Key: KARAF-6000
> URL: https://issues.apache.org/jira/browse/KARAF-6000
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.2.2
>
>
> Since OSGi R6, the "new" bundle repository spec allows to directly leverage
> any requirement/capability to do the bundle resolution.
> We already support this via the features (using {{resourceRepository}} with
> json or XML in {{etc/org.apache.karaf.features.cfg}}. I think it would be
> great to have a complete alternative to features using bundle repository. We
> could introduce a minimal feature set (just for the bootstrapping) as we have
> today, but delegating to {{etc/org.apache.karaf.repository.cfg}} for resource
> repositories and using them for resolution.
> We could also provide specific commands to manipulate the bundle repositories
> (like add, remove, as we have for features repositories).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
