[jira] [Created] (KARAF-4696) Upgrade to Pax-Web 4.3.0

2016-09-02 Thread Achim Nierbeck (JIRA) 
Achim Nierbeck created KARAF-4696:
-

 Summary: Upgrade to Pax-Web 4.3.0
 Key: KARAF-4696
 URL: https://issues.apache.org/jira/browse/KARAF-4696
 Project: Karaf
  Issue Type: Bug
  Components: karaf-webcontainer
Reporter: Achim Nierbeck
 Fix For: 4.0.7


API Changes in Pax-Web require a Minor version bump to 4.3.0 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (KARAF-4178) Cellar webconsole doesn't appear in a browser

2016-09-02 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4178.
-
Resolution: Cannot Reproduce

> Cellar webconsole doesn't appear in a browser
> -
>
> Key: KARAF-4178
> URL: https://issues.apache.org/jira/browse/KARAF-4178
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-webconsole
>Affects Versions: cellar-4.0.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Attachments: webconsole-cellar.png
>
>
> Even installing the cellar-webconsole feature, the cellar plugin doesn't 
> appear in the Karaf webconsole.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4178) Cellar webconsole doesn't appear in a browser

2016-09-02 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4178:

Fix Version/s: (was: cellar-4.0.2)

> Cellar webconsole doesn't appear in a browser
> -
>
> Key: KARAF-4178
> URL: https://issues.apache.org/jira/browse/KARAF-4178
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-webconsole
>Affects Versions: cellar-4.0.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Attachments: webconsole-cellar.png
>
>
> Even installing the cellar-webconsole feature, the cellar plugin doesn't 
> appear in the Karaf webconsole.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4178) Cellar webconsole doesn't appear in a browser

2016-09-02 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/KARAF-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458873#comment-15458873
 ] 

Jean-Baptiste Onofré commented on KARAF-4178:
-

Hmmm, my bad, it works fine with the different scenario.

> Cellar webconsole doesn't appear in a browser
> -
>
> Key: KARAF-4178
> URL: https://issues.apache.org/jira/browse/KARAF-4178
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-webconsole
>Affects Versions: cellar-4.0.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Attachments: webconsole-cellar.png
>
>
> Even installing the cellar-webconsole feature, the cellar plugin doesn't 
> appear in the Karaf webconsole.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4695) Unable to use http://karaf.apache.org/xmlns/shell/v1.0.0

2016-09-02 Thread Kevin O'Toole (JIRA) 
Kevin O'Toole created KARAF-4695:


 Summary: Unable to use http://karaf.apache.org/xmlns/shell/v1.0.0
 Key: KARAF-4695
 URL: https://issues.apache.org/jira/browse/KARAF-4695
 Project: Karaf
  Issue Type: Bug
  Components: karaf-shell
Affects Versions: 4.0.6, 4.0.5
Reporter: Kevin O'Toole


Within my Blueprint file, if I use the 
http://karaf.apache.org/xmlns/shell/v1.0.0 namespace, I get the following 
exception (notice it refers to 1.1.0 even though I am using 1.0.0)
{noformat}org.xml.sax.SAXParseException: src-import.3.1: The namespace 
attribute, 'http://schemas.xmlsoap.org/wsdl/', of an  element information item 
must be identical to the targetNamespace attribute, 
'http://karaf.apache.org/xmlns/shell/v1.1.0', of the imported document.
at 
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown 
Source)[:]
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)[:]
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown 
Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaError(Unknown 
Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
at 
org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown 
Source)[:]
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown 
Source)[:]
at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(Unknown 
Source)[:]
at 
org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.createSchema(NamespaceHandlerRegistryImpl.java:641)[48:org.apache.aries.blueprint.core:1.6.2]
at 
org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.doGetSchema(NamespaceHandlerRegistryImpl.java:458)[48:org.apache.aries.blueprint.core:1.6.2]
at 
org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.getSchema(NamespaceHandlerRegistryImpl.java:443)[48:org.apache.aries.blueprint.core:1.6.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:343)[48:org.apache.aries.blueprint.core:1.6.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:276)[48:org.apache.aries.blueprint.core:1.6.2]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:300)[48:org.apache.aries.blueprint.core:1.6.2]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:269)[48:org.apache.aries.blueprint.core:1.6.2]
at 
org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:265)[48:org.apache.aries.blueprint.core:1.6.2]
at 
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:255)[48:org.apache.aries.blueprint.core:1.6.2]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)[66:org.apache.aries.util:1.1.1]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)[66:org.apache.aries.util:1.1.1]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)[66:org.apache.aries.util:1.1.1]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)[66:org.apache.aries.util:1.1.1]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)[66:org.apache.aries.util:1.1.1]
at 
org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:731)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:486)[org.apache.felix.framework-5.4.0.jar:]
at 
org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4541)[org.apache.felix.framework-5.4.0.jar:]
at

[jira] [Commented] (KARAF-4257) Use req/cap in Cellar to be able to switch different implementation

2016-09-02 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/KARAF-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458510#comment-15458510
 ] 

Jean-Baptiste Onofré commented on KARAF-4257:
-

Cellar bundles already provide some capabilities. The idea of this Jira is to 
use kind of extender of Cellar cluster where Hazelcast would be the default 
implementation.

> Use req/cap in Cellar to be able to switch different implementation
> ---
>
> Key: KARAF-4257
> URL: https://issues.apache.org/jira/browse/KARAF-4257
> Project: Karaf
>  Issue Type: Improvement
>  Components: cellar-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4669) Start level is ignored for bundles installed in cluster

2016-09-02 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/KARAF-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458506#comment-15458506
 ] 

Jean-Baptiste Onofré commented on KARAF-4669:
-

I would recommend to use feature sync instead of bundle for that. Anyway, I 
plan to store the start-level on the cluster map to be able to deal with it.

> Start level is ignored for bundles installed in cluster
> ---
>
> Key: KARAF-4669
> URL: https://issues.apache.org/jira/browse/KARAF-4669
> Project: Karaf
>  Issue Type: Improvement
>  Components: cellar-bundle
>Affects Versions: cellar-4.0.1
>Reporter: Sergiy Shyrkov
>Priority: Minor
>
> Right now the start-level is not supported for bundles in cluster, i.e. it is 
> not possible to provide a particular start level when using 
> "cluster:bundle-install" command or directly the CellarBundleMBeanImpl.
> We could workaround this by first installing the bundle (without start), 
> changing the start-level and then starting it.
> But even in this case the bundle start level on other cluster nodes is the 
> default one (80) and not the one, we are specifying on the source node.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4694) Downgrade to Hazelcast 3.6.2

2016-09-02 Thread JIRA 
Jean-Baptiste Onofré created KARAF-4694:
---

 Summary: Downgrade to Hazelcast 3.6.2
 Key: KARAF-4694
 URL: https://issues.apache.org/jira/browse/KARAF-4694
 Project: Karaf
  Issue Type: Bug
  Components: cellar-core
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré


To avoid issue with {{camel-hazelcast}} component, I downgrade Cellar to 
Hazelcast 3.6.2 in order to have aligned version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4670) Race condition in the Activator.updated() of the org.apache.karaf.cellar.hazelcast

2016-09-02 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458498#comment-15458498
 ] 

ASF GitHub Bot commented on KARAF-4670:
---

Github user asfgit closed the pull request at:

https://github.com/apache/karaf-cellar/pull/31


> Race condition in the Activator.updated() of the 
> org.apache.karaf.cellar.hazelcast
> --
>
> Key: KARAF-4670
> URL: https://issues.apache.org/jira/browse/KARAF-4670
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-hazelcast
>Affects Versions: cellar-4.0.1
>Reporter: Sergiy Shyrkov
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.2
>
>
> Sometimes on the startup I get an NPE in the 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator.updated() because 
> the doStart() method execution has not been finished yet and the 
> hazelcastServiceFactory is still null.
> My log is as follows, where the log message about the initialization of the 
> hazelcastServiceFactory ("init Hazelcast service factory") comes after the 
> call to Activator.updated() (causes an NPE).
> Thank you!
> {code}
> 2016-08-26 14:35:01,780: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.bundle: BundleEvent STARTING - 
> org.apache.karaf.cellar.bundle
> 2016-08-26 14:35:01,793: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.bundle/4.0.1. Missing 
> dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,794: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.bundle: BundleEvent STARTED - 
> org.apache.karaf.cellar.bundle
> 2016-08-26 14:35:01,795: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: BundleEvent STARTING - 
> org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,801: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: ServiceEvent REGISTERED - 
> [org.osgi.service.cm.ManagedService] - org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,810: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.config/4.0.1. Missing 
> dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,810: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: BundleEvent STARTED - 
> org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,811: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.features: BundleEvent STARTING - 
> org.apache.karaf.cellar.features
> 2016-08-26 14:35:01,831: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.features/4.0.1. 
> Missing dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,831: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.features: BundleEvent STARTED - 
> org.apache.karaf.cellar.features
> 2016-08-26 14:35:01,832: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.hazelcast: BundleEvent STARTING - 
> org.apache.karaf.cellar.hazelcast
> 2016-08-26 14:35:01,839: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.hazelcast: ServiceEvent REGISTERED - 
> [org.osgi.service.cm.ManagedService] - org.apache.karaf.cellar.hazelcast
> 2016-08-26 14:35:01,841: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Registering 
> commands for bundle org.apache.karaf.cellar.hazelcast/4.0.1
> 2016-08-26 14:35:01,841: DEBUG [pool-153-thread-1] 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator: CELLAR HAZELCAST: 
> init combined class loader
> 2016-08-26 14:35:01,844: ERROR [CM Configuration Updater (ManagedService 
> Update: pid=[org.apache.karaf.cellar.discovery])] 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator: Can't update 
> Hazelcast service factory
> java.lang.NullPointerException
>   at 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator.updated(Activator.java:392)
>   at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)
>   at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)
>   at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)
>   at 
>

[jira] [Resolved] (KARAF-4670) Race condition in the Activator.updated() of the org.apache.karaf.cellar.hazelcast

2016-09-02 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-4670.
-
Resolution: Fixed

> Race condition in the Activator.updated() of the 
> org.apache.karaf.cellar.hazelcast
> --
>
> Key: KARAF-4670
> URL: https://issues.apache.org/jira/browse/KARAF-4670
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-hazelcast
>Affects Versions: cellar-4.0.1
>Reporter: Sergiy Shyrkov
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.2
>
>
> Sometimes on the startup I get an NPE in the 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator.updated() because 
> the doStart() method execution has not been finished yet and the 
> hazelcastServiceFactory is still null.
> My log is as follows, where the log message about the initialization of the 
> hazelcastServiceFactory ("init Hazelcast service factory") comes after the 
> call to Activator.updated() (causes an NPE).
> Thank you!
> {code}
> 2016-08-26 14:35:01,780: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.bundle: BundleEvent STARTING - 
> org.apache.karaf.cellar.bundle
> 2016-08-26 14:35:01,793: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.bundle/4.0.1. Missing 
> dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,794: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.bundle: BundleEvent STARTED - 
> org.apache.karaf.cellar.bundle
> 2016-08-26 14:35:01,795: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: BundleEvent STARTING - 
> org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,801: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: ServiceEvent REGISTERED - 
> [org.osgi.service.cm.ManagedService] - org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,810: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.config/4.0.1. Missing 
> dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,810: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: BundleEvent STARTED - 
> org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,811: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.features: BundleEvent STARTING - 
> org.apache.karaf.cellar.features
> 2016-08-26 14:35:01,831: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.features/4.0.1. 
> Missing dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,831: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.features: BundleEvent STARTED - 
> org.apache.karaf.cellar.features
> 2016-08-26 14:35:01,832: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.hazelcast: BundleEvent STARTING - 
> org.apache.karaf.cellar.hazelcast
> 2016-08-26 14:35:01,839: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.hazelcast: ServiceEvent REGISTERED - 
> [org.osgi.service.cm.ManagedService] - org.apache.karaf.cellar.hazelcast
> 2016-08-26 14:35:01,841: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Registering 
> commands for bundle org.apache.karaf.cellar.hazelcast/4.0.1
> 2016-08-26 14:35:01,841: DEBUG [pool-153-thread-1] 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator: CELLAR HAZELCAST: 
> init combined class loader
> 2016-08-26 14:35:01,844: ERROR [CM Configuration Updater (ManagedService 
> Update: pid=[org.apache.karaf.cellar.discovery])] 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator: Can't update 
> Hazelcast service factory
> java.lang.NullPointerException
>   at 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator.updated(Activator.java:392)
>   at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)
>   at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)
>   at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)
>   at 
> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1444)
>   at 
>

[jira] [Commented] (KARAF-4670) Race condition in the Activator.updated() of the org.apache.karaf.cellar.hazelcast

2016-09-02 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458497#comment-15458497
 ] 

ASF subversion and git services commented on KARAF-4670:


Commit 8b78846cbdf61adeae38228c8bbe3ad377e9983c in karaf-cellar's branch 
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-cellar.git;h=8b78846 ]

[KARAF-4670] This closes #31


> Race condition in the Activator.updated() of the 
> org.apache.karaf.cellar.hazelcast
> --
>
> Key: KARAF-4670
> URL: https://issues.apache.org/jira/browse/KARAF-4670
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-hazelcast
>Affects Versions: cellar-4.0.1
>Reporter: Sergiy Shyrkov
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.2
>
>
> Sometimes on the startup I get an NPE in the 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator.updated() because 
> the doStart() method execution has not been finished yet and the 
> hazelcastServiceFactory is still null.
> My log is as follows, where the log message about the initialization of the 
> hazelcastServiceFactory ("init Hazelcast service factory") comes after the 
> call to Activator.updated() (causes an NPE).
> Thank you!
> {code}
> 2016-08-26 14:35:01,780: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.bundle: BundleEvent STARTING - 
> org.apache.karaf.cellar.bundle
> 2016-08-26 14:35:01,793: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.bundle/4.0.1. Missing 
> dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,794: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.bundle: BundleEvent STARTED - 
> org.apache.karaf.cellar.bundle
> 2016-08-26 14:35:01,795: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: BundleEvent STARTING - 
> org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,801: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: ServiceEvent REGISTERED - 
> [org.osgi.service.cm.ManagedService] - org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,810: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.config/4.0.1. Missing 
> dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,810: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: BundleEvent STARTED - 
> org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,811: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.features: BundleEvent STARTING - 
> org.apache.karaf.cellar.features
> 2016-08-26 14:35:01,831: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.features/4.0.1. 
> Missing dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,831: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.features: BundleEvent STARTED - 
> org.apache.karaf.cellar.features
> 2016-08-26 14:35:01,832: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.hazelcast: BundleEvent STARTING - 
> org.apache.karaf.cellar.hazelcast
> 2016-08-26 14:35:01,839: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.hazelcast: ServiceEvent REGISTERED - 
> [org.osgi.service.cm.ManagedService] - org.apache.karaf.cellar.hazelcast
> 2016-08-26 14:35:01,841: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Registering 
> commands for bundle org.apache.karaf.cellar.hazelcast/4.0.1
> 2016-08-26 14:35:01,841: DEBUG [pool-153-thread-1] 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator: CELLAR HAZELCAST: 
> init combined class loader
> 2016-08-26 14:35:01,844: ERROR [CM Configuration Updater (ManagedService 
> Update: pid=[org.apache.karaf.cellar.discovery])] 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator: Can't update 
> Hazelcast service factory
> java.lang.NullPointerException
>   at 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator.updated(Activator.java:392)
>   at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)
>   at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)
>   at 
>

[jira] [Commented] (KARAF-4670) Race condition in the Activator.updated() of the org.apache.karaf.cellar.hazelcast

2016-09-02 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458496#comment-15458496
 ] 

ASF subversion and git services commented on KARAF-4670:


Commit 9f9601126d685c76f49d3519bed5da5215771163 in karaf-cellar's branch 
refs/heads/master from [~shyrkov]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-cellar.git;h=9f96011 ]

[KARAF-4670] Postpone configuration update if the hazelcastServiceFactory 
instance if not initialized yet


> Race condition in the Activator.updated() of the 
> org.apache.karaf.cellar.hazelcast
> --
>
> Key: KARAF-4670
> URL: https://issues.apache.org/jira/browse/KARAF-4670
> Project: Karaf
>  Issue Type: Bug
>  Components: cellar-hazelcast
>Affects Versions: cellar-4.0.1
>Reporter: Sergiy Shyrkov
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.2
>
>
> Sometimes on the startup I get an NPE in the 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator.updated() because 
> the doStart() method execution has not been finished yet and the 
> hazelcastServiceFactory is still null.
> My log is as follows, where the log message about the initialization of the 
> hazelcastServiceFactory ("init Hazelcast service factory") comes after the 
> call to Activator.updated() (causes an NPE).
> Thank you!
> {code}
> 2016-08-26 14:35:01,780: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.bundle: BundleEvent STARTING - 
> org.apache.karaf.cellar.bundle
> 2016-08-26 14:35:01,793: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.bundle/4.0.1. Missing 
> dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,794: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.bundle: BundleEvent STARTED - 
> org.apache.karaf.cellar.bundle
> 2016-08-26 14:35:01,795: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: BundleEvent STARTING - 
> org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,801: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: ServiceEvent REGISTERED - 
> [org.osgi.service.cm.ManagedService] - org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,810: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.config/4.0.1. Missing 
> dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,810: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.config: BundleEvent STARTED - 
> org.apache.karaf.cellar.config
> 2016-08-26 14:35:01,811: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.features: BundleEvent STARTING - 
> org.apache.karaf.cellar.features
> 2016-08-26 14:35:01,831: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Command 
> registration delayed for bundle org.apache.karaf.cellar.features/4.0.1. 
> Missing dependencies: [org.apache.karaf.cellar.core.ClusterManager, 
> org.apache.karaf.cellar.core.GroupManager, 
> org.apache.karaf.cellar.core.event.EventProducer]
> 2016-08-26 14:35:01,831: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.features: BundleEvent STARTED - 
> org.apache.karaf.cellar.features
> 2016-08-26 14:35:01,832: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.hazelcast: BundleEvent STARTING - 
> org.apache.karaf.cellar.hazelcast
> 2016-08-26 14:35:01,839: DEBUG [FelixStartLevel] 
> org.apache.karaf.cellar.hazelcast: ServiceEvent REGISTERED - 
> [org.osgi.service.cm.ManagedService] - org.apache.karaf.cellar.hazelcast
> 2016-08-26 14:35:01,841: INFO  [FelixStartLevel] 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension: Registering 
> commands for bundle org.apache.karaf.cellar.hazelcast/4.0.1
> 2016-08-26 14:35:01,841: DEBUG [pool-153-thread-1] 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator: CELLAR HAZELCAST: 
> init combined class loader
> 2016-08-26 14:35:01,844: ERROR [CM Configuration Updater (ManagedService 
> Update: pid=[org.apache.karaf.cellar.discovery])] 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator: Can't update 
> Hazelcast service factory
> java.lang.NullPointerException
>   at 
> org.apache.karaf.cellar.hazelcast.internal.osgi.Activator.updated(Activator.java:392)
>   at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)
>   at 
>

[jira] [Commented] (KARAF-4693) shell:new issue with class wildcards

2016-09-02 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458098#comment-15458098
 ] 

ASF GitHub Bot commented on KARAF-4693:
---

GitHub user paoloantinori opened a pull request:

https://github.com/apache/karaf/pull/236

KARAF-4693 - shell:new, support for wildcards in generics



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/paoloantinori/karaf KARAF-4693

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf/pull/236.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #236


commit ea0149950fb405bf7f518f4638b4708ec35f6dd6
Author: Paolo Antinori 
Date:   2016-09-02T09:56:18Z

KARAF-4693 - shell:new, support for wildcards in generics




> shell:new issue with class wildcards
> 
>
> Key: KARAF-4693
> URL: https://issues.apache.org/jira/browse/KARAF-4693
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.0.6
>Reporter: Paolo Antinori
>
> Karaf shell fails if you run this command:
> {code:none}a=shell:new java.util.ArrayList 2
> 2016-09-02 11:15:51,525 | ERROR | nsole user karaf | ShellUtil
> | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
> executing command
> java.lang.IllegalStateException
>   at 
> org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:161)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:154)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.karaf.shell.commands.impl.NewAction.findMatchingConstructors(NewAction.java:167)[41:org.apache.karaf.shell.commands:4.0.6]
>   at 
> org.apache.karaf.shell.commands.impl.NewAction.execute(NewAction.java:89)[41:org.apache.karaf.shell.commands:4.0.6]
>   at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[43:org.apache.karaf.shell.core:4.0.6]
>   at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:274)[43:org.apache.karaf.shell.core:4.0.6]
>   at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
> {code}
> The reason for that is not really that it can't handle generics but it the 
> logic that probe for the best matching constructor, that at some point, in 
> this class:
> https://github.com/apache/karaf/blob/68bef0ced72a3fe192cfe496b3fff654b49b2377/shell/core/src/main/java/org/apache/karaf/shell/support/converter/GenericType.java#L161-L161
> sees {{type}} set to {{"? extends E"}} that is not able to handle, thus 
> throwing the blocking exception.
> It's enough to replace that exception with an empty return, to bypass the 
> failing iteration and have the command to succeed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4693) shell:new issue with class wildcards

2016-09-02 Thread Paolo Antinori (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KARAF-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paolo Antinori updated KARAF-4693:
--
Description: 
Karaf shell fails if you run this command:

{code:none}a=shell:new java.util.ArrayList 2

2016-09-02 11:15:51,525 | ERROR | nsole user karaf | ShellUtil  
  | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
executing command
java.lang.IllegalStateException
at 
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:161)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:154)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.commands.impl.NewAction.findMatchingConstructors(NewAction.java:167)[41:org.apache.karaf.shell.commands:4.0.6]
at 
org.apache.karaf.shell.commands.impl.NewAction.execute(NewAction.java:89)[41:org.apache.karaf.shell.commands:4.0.6]
at 
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:274)[43:org.apache.karaf.shell.core:4.0.6]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]

{code}

The reason for that is not really that it can't handle generics but it the 
logic that probe for the best matching constructor, that at some point, in this 
class:

https://github.com/apache/karaf/blob/68bef0ced72a3fe192cfe496b3fff654b49b2377/shell/core/src/main/java/org/apache/karaf/shell/support/converter/GenericType.java#L161-L161

sees {{type}} set to {{"? extends E"}} that is not able to handle, thus 
throwing the blocking exception.

It's enough to replace that exception with an empty return, to bypass the 
failing iteration and have the command to succeed.

  was:
Karaf shell fails if you run this command:

{code:a}=shell:new java.util.ArrayList 2

2016-09-02 11:15:51,525 | ERROR | nsole user karaf | ShellUtil  
  | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
executing command
java.lang.IllegalStateException
at 
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:161)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:154)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.commands.impl.NewAction.findMatchingConstructors(NewAction.java:167)[41:org.apache.karaf.shell.commands:4.0.6]
at 
org.apache.karaf.shell.commands.impl.NewAction.execute(NewAction.java:89)[41:org.apache.karaf.shell.commands:4.0.6]
at 
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.6]
at

[jira] [Created] (KARAF-4693) shell:new issue with class wildcards

2016-09-02 Thread Paolo Antinori (JIRA) 
Paolo Antinori created KARAF-4693:
-

 Summary: shell:new issue with class wildcards
 Key: KARAF-4693
 URL: https://issues.apache.org/jira/browse/KARAF-4693
 Project: Karaf
  Issue Type: Bug
  Components: karaf-shell
Affects Versions: 4.0.6
Reporter: Paolo Antinori


Karaf shell fails if you run this command:

{code:a}=shell:new java.util.ArrayList 2

2016-09-02 11:15:51,525 | ERROR | nsole user karaf | ShellUtil  
  | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
executing command
java.lang.IllegalStateException
at 
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:161)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.support.converter.GenericType.parametersOf(GenericType.java:154)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.support.converter.GenericType.[init](GenericType.java:53)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.commands.impl.NewAction.findMatchingConstructors(NewAction.java:167)[41:org.apache.karaf.shell.commands:4.0.6]
at 
org.apache.karaf.shell.commands.impl.NewAction.execute(NewAction.java:89)[41:org.apache.karaf.shell.commands:4.0.6]
at 
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:83)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:67)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:87)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:480)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:406)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:182)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:119)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:94)[43:org.apache.karaf.shell.core:4.0.6]
at 
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:274)[43:org.apache.karaf.shell.core:4.0.6]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]

{code}

The reason for that is not really that it can't handle generics but it the 
logic that probe for the best matching constructor, that at some point, in this 
class:

https://github.com/apache/karaf/blob/68bef0ced72a3fe192cfe496b3fff654b49b2377/shell/core/src/main/java/org/apache/karaf/shell/support/converter/GenericType.java#L161-L161

sees {{type}} set to {{"? extends E"}} that is not able to handle, thus 
throwing the blocking exception.

It's enough to replace that exception with an empty return, to bypass the 
failing iteration and have the command to succeed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4692) Inconsistent behavior towards Bundle-ManifestVersion

2016-09-02 Thread Paolo Antinori (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KARAF-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paolo Antinori updated KARAF-4692:
--
Description: 
In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the 
clause completely), {{bundle:install}} command **succeeds**, while 
{{feature:install}}, while installing a feature containing a bundle with 
manifest version set to 1, **fails**.

{code}
karaf@root()> feature:install ibm 
Error executing command: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1


2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil  
  | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
executing command
org.osgi.framework.BundleException: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported 
'Bundle-ManifestVersion' value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6]
... 9 more
{code}

  was:
In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the 
clause completely), {{bundle:install}} command succeeds, while 
{{feature:install}}, while installing a feature containing a bundle with 
manifest version set to 1, fails.

{code}
karaf@root()> feature:install ibm 
Error executing command: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1


2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil  
  | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
executing command
org.osgi.framework.BundleException: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported 
'Bundle-ManifestVersion' value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at

[jira] [Updated] (KARAF-4692) Inconsistent behavior towards Bundle-ManifestVersion

2016-09-02 Thread Paolo Antinori (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KARAF-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paolo Antinori updated KARAF-4692:
--
Description: 
In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the 
clause completely), {{bundle:install}} command *succeeds*, while 
{{feature:install}}, while installing a feature containing a bundle with 
manifest version set to 1, *fails*.

{code}
karaf@root()> feature:install ibm 
Error executing command: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1


2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil  
  | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
executing command
org.osgi.framework.BundleException: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported 
'Bundle-ManifestVersion' value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6]
... 9 more
{code}

  was:
In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the 
clause completely), {{bundle:install}} command **succeeds**, while 
{{feature:install}}, while installing a feature containing a bundle with 
manifest version set to 1, **fails**.

{code}
karaf@root()> feature:install ibm 
Error executing command: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1


2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil  
  | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
executing command
org.osgi.framework.BundleException: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported 
'Bundle-ManifestVersion' value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at

[jira] [Created] (KARAF-4692) Inconsistent behavior towards Bundle-ManifestVersion

2016-09-02 Thread Paolo Antinori (JIRA) 
Paolo Antinori created KARAF-4692:
-

 Summary: Inconsistent behavior towards Bundle-ManifestVersion
 Key: KARAF-4692
 URL: https://issues.apache.org/jira/browse/KARAF-4692
 Project: Karaf
  Issue Type: Bug
  Components: karaf-core
Affects Versions: 4.0.6
Reporter: Paolo Antinori


In case of a bundle with `Bundle-ManifestVersion` set to 1 (or without the 
clause completely), `bundle:install` command succeeds, while `feature:install`, 
while installing a feature containing a bundle with manifest version set to 1, 
fails.

```
karaf@root()> feature:install ibm 
Error executing command: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1


2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil  
  | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
executing command
org.osgi.framework.BundleException: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported 
'Bundle-ManifestVersion' value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6]
... 9 more
```



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (KARAF-4692) Inconsistent behavior towards Bundle-ManifestVersion

2016-09-02 Thread Paolo Antinori (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KARAF-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paolo Antinori updated KARAF-4692:
--
Description: 
In case of a bundle with {{Bundle-ManifestVersion}} set to 1 (or without the 
clause completely), {{bundle:install}} command succeeds, while 
{{feature:install}}, while installing a feature containing a bundle with 
manifest version set to 1, fails.

{code}
karaf@root()> feature:install ibm 
Error executing command: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1


2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil  
  | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
executing command
org.osgi.framework.BundleException: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported 
'Bundle-ManifestVersion' value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6]
... 9 more
{code}

  was:
In case of a bundle with `Bundle-ManifestVersion` set to 1 (or without the 
clause completely), `bundle:install` command succeeds, while `feature:install`, 
while installing a feature containing a bundle with manifest version set to 1, 
fails.

```
karaf@root()> feature:install ibm 
Error executing command: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1


2016-09-02 10:43:57,069 | ERROR | nsole user karaf | ShellUtil  
  | 43 - org.apache.karaf.shell.core - 4.0.6 | Exception caught while 
executing command
org.osgi.framework.BundleException: Unable to build resource for 
mvn:com.ibm.mqjms/com.ibm.mqjms/7.5.0.6: Unsupported 'Bundle-ManifestVersion' 
value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:80)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:65)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:143)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:218)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_102]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_102]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_102]
Caused by: org.osgi.framework.BundleException: Unsupported 
'Bundle-ManifestVersion' value: 1
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.doBuild(ResourceBuilder.java:88)[8:org.apache.karaf.features.core:4.0.6]
at 
org.apache.karaf.features.internal.resolver.ResourceBuilder.build(ResourceBuilder.java:78)[8:org.apache.karaf.features.core:4.0.6]
... 9

[jira] [Commented] (KARAF-4685) Support session replication through OSGi 6 http whiteboard

2016-09-02 Thread Roland Hauser (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457899#comment-15457899
 ] 

Roland Hauser commented on KARAF-4685:
--

I'm already working on an implementation. It would be great, if I could use 
that new Cellar branch ;-)

> Support session replication through OSGi 6 http whiteboard
> --
>
> Key: KARAF-4685
> URL: https://issues.apache.org/jira/browse/KARAF-4685
> Project: Karaf
>  Issue Type: Improvement
>  Components: cellar-http
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
>
> Currently, session replication can only be done through specifying the 
> Hazelcast filter/listener in the web.xml file of a web-application. This can 
> be a serious disadvantage if you also want to install a web-application to 
> another web-container which does not need clustering, and, consequently, does 
> not contain the Hazelcast libs. In this case, the application won't start.
> I suggest an additional way how session replication could be realized without 
> the need of modifying the web-app: it could be done through a Cellar 
> component which implements a http whiteboard. I would realize this as follows:
> - Register a Filter/Session listener to the OSGi service registry. Per 
> default, every web-application installed is considered for session 
> replication.
> - It should be possible to configure Hazelcast filter properties either 
> through a config file inside the OSGI-INF folder of the web-app, or, through 
> the ConfigAdmin service.
> - If the sessions of a specific web-application should not be replicated, 
> then this could be flagged either through a config file inside the OSGI-INF 
> folder of the web-app, or, through the ConfigAdmin service.
> - The new Cellar component should be installable as additional feature 
> "http-failover"
> What's your opinion?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4685) Support session replication through OSGi 6 http whiteboard

2016-09-02 Thread Achim Nierbeck (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457897#comment-15457897
 ] 

Achim Nierbeck commented on KARAF-4685:
---

Well the proposed flags are only available from that feature on ... (or better 
understood with that version)
BUT ... we have a similar thing already available with the current version of 
Pax-Web :-) 

> Support session replication through OSGi 6 http whiteboard
> --
>
> Key: KARAF-4685
> URL: https://issues.apache.org/jira/browse/KARAF-4685
> Project: Karaf
>  Issue Type: Improvement
>  Components: cellar-http
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
>
> Currently, session replication can only be done through specifying the 
> Hazelcast filter/listener in the web.xml file of a web-application. This can 
> be a serious disadvantage if you also want to install a web-application to 
> another web-container which does not need clustering, and, consequently, does 
> not contain the Hazelcast libs. In this case, the application won't start.
> I suggest an additional way how session replication could be realized without 
> the need of modifying the web-app: it could be done through a Cellar 
> component which implements a http whiteboard. I would realize this as follows:
> - Register a Filter/Session listener to the OSGi service registry. Per 
> default, every web-application installed is considered for session 
> replication.
> - It should be possible to configure Hazelcast filter properties either 
> through a config file inside the OSGI-INF folder of the web-app, or, through 
> the ConfigAdmin service.
> - If the sessions of a specific web-application should not be replicated, 
> then this could be flagged either through a config file inside the OSGI-INF 
> folder of the web-app, or, through the ConfigAdmin service.
> - The new Cellar component should be installable as additional feature 
> "http-failover"
> What's your opinion?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4685) Support session replication through OSGi 6 http whiteboard

2016-09-02 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/KARAF-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457888#comment-15457888
 ] 

Jean-Baptiste Onofré commented on KARAF-4685:
-

It's hard to relay on OSGi Enterpsie Spec 6.0.0 in Cellar 4.0.x, or it means 
such feature will work only with only specific Karaf version.

What I can do is to prepare Cellar 4.1.0 (working with Karaf 4.1.x), and 
implement such feature for this version serie.

> Support session replication through OSGi 6 http whiteboard
> --
>
> Key: KARAF-4685
> URL: https://issues.apache.org/jira/browse/KARAF-4685
> Project: Karaf
>  Issue Type: Improvement
>  Components: cellar-http
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
>
> Currently, session replication can only be done through specifying the 
> Hazelcast filter/listener in the web.xml file of a web-application. This can 
> be a serious disadvantage if you also want to install a web-application to 
> another web-container which does not need clustering, and, consequently, does 
> not contain the Hazelcast libs. In this case, the application won't start.
> I suggest an additional way how session replication could be realized without 
> the need of modifying the web-app: it could be done through a Cellar 
> component which implements a http whiteboard. I would realize this as follows:
> - Register a Filter/Session listener to the OSGi service registry. Per 
> default, every web-application installed is considered for session 
> replication.
> - It should be possible to configure Hazelcast filter properties either 
> through a config file inside the OSGI-INF folder of the web-app, or, through 
> the ConfigAdmin service.
> - If the sessions of a specific web-application should not be replicated, 
> then this could be flagged either through a config file inside the OSGI-INF 
> folder of the web-app, or, through the ConfigAdmin service.
> - The new Cellar component should be installable as additional feature 
> "http-failover"
> What's your opinion?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (KARAF-4685) Support session replication through OSGi 6 http whiteboard

2016-09-02 Thread Achim Nierbeck (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457864#comment-15457864
 ] 

Achim Nierbeck edited comment on KARAF-4685 at 9/2/16 8:01 AM:
---

This will require Pax-Web 6.0 as it's the version handling OSGi R6 
Http-Whiteboard service. 
So this will only be possible on a Karaf 4.1 not lower. 


was (Author: achim_nierbeck):
This will require Pax-Web 6.0 as it's the version handling OSGi R6 
Http-Whiteboard service. 

> Support session replication through OSGi 6 http whiteboard
> --
>
> Key: KARAF-4685
> URL: https://issues.apache.org/jira/browse/KARAF-4685
> Project: Karaf
>  Issue Type: Improvement
>  Components: cellar-http
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
>
> Currently, session replication can only be done through specifying the 
> Hazelcast filter/listener in the web.xml file of a web-application. This can 
> be a serious disadvantage if you also want to install a web-application to 
> another web-container which does not need clustering, and, consequently, does 
> not contain the Hazelcast libs. In this case, the application won't start.
> I suggest an additional way how session replication could be realized without 
> the need of modifying the web-app: it could be done through a Cellar 
> component which implements a http whiteboard. I would realize this as follows:
> - Register a Filter/Session listener to the OSGi service registry. Per 
> default, every web-application installed is considered for session 
> replication.
> - It should be possible to configure Hazelcast filter properties either 
> through a config file inside the OSGI-INF folder of the web-app, or, through 
> the ConfigAdmin service.
> - If the sessions of a specific web-application should not be replicated, 
> then this could be flagged either through a config file inside the OSGI-INF 
> folder of the web-app, or, through the ConfigAdmin service.
> - The new Cellar component should be installable as additional feature 
> "http-failover"
> What's your opinion?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4685) Support session replication through OSGi 6 http whiteboard

2016-09-02 Thread Achim Nierbeck (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457864#comment-15457864
 ] 

Achim Nierbeck commented on KARAF-4685:
---

This will require Pax-Web 6.0 as it's the version handling OSGi R6 
Http-Whiteboard service. 

> Support session replication through OSGi 6 http whiteboard
> --
>
> Key: KARAF-4685
> URL: https://issues.apache.org/jira/browse/KARAF-4685
> Project: Karaf
>  Issue Type: Improvement
>  Components: cellar-http
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
>
> Currently, session replication can only be done through specifying the 
> Hazelcast filter/listener in the web.xml file of a web-application. This can 
> be a serious disadvantage if you also want to install a web-application to 
> another web-container which does not need clustering, and, consequently, does 
> not contain the Hazelcast libs. In this case, the application won't start.
> I suggest an additional way how session replication could be realized without 
> the need of modifying the web-app: it could be done through a Cellar 
> component which implements a http whiteboard. I would realize this as follows:
> - Register a Filter/Session listener to the OSGi service registry. Per 
> default, every web-application installed is considered for session 
> replication.
> - It should be possible to configure Hazelcast filter properties either 
> through a config file inside the OSGI-INF folder of the web-app, or, through 
> the ConfigAdmin service.
> - If the sessions of a specific web-application should not be replicated, 
> then this could be flagged either through a config file inside the OSGI-INF 
> folder of the web-app, or, through the ConfigAdmin service.
> - The new Cellar component should be installable as additional feature 
> "http-failover"
> What's your opinion?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4685) Support session replication through OSGi 6 http whiteboard

2016-09-02 Thread Roland Hauser (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457856#comment-15457856
 ] 

Roland Hauser commented on KARAF-4685:
--

This should work exactly that way, see OSGi enterprise spec 6.0.0, 140.5 
Registering service filters and 140.7 Registering Listeners. The only thing is 
that a listener must be registered with property 
osgi.http.whiteboard.listener=true otherwise it will be ignored by the http 
whiteboard.

> Support session replication through OSGi 6 http whiteboard
> --
>
> Key: KARAF-4685
> URL: https://issues.apache.org/jira/browse/KARAF-4685
> Project: Karaf
>  Issue Type: Improvement
>  Components: cellar-http
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
>
> Currently, session replication can only be done through specifying the 
> Hazelcast filter/listener in the web.xml file of a web-application. This can 
> be a serious disadvantage if you also want to install a web-application to 
> another web-container which does not need clustering, and, consequently, does 
> not contain the Hazelcast libs. In this case, the application won't start.
> I suggest an additional way how session replication could be realized without 
> the need of modifying the web-app: it could be done through a Cellar 
> component which implements a http whiteboard. I would realize this as follows:
> - Register a Filter/Session listener to the OSGi service registry. Per 
> default, every web-application installed is considered for session 
> replication.
> - It should be possible to configure Hazelcast filter properties either 
> through a config file inside the OSGI-INF folder of the web-app, or, through 
> the ConfigAdmin service.
> - If the sessions of a specific web-application should not be replicated, 
> then this could be flagged either through a config file inside the OSGI-INF 
> folder of the web-app, or, through the ConfigAdmin service.
> - The new Cellar component should be installable as additional feature 
> "http-failover"
> What's your opinion?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (KARAF-4691) Mouse scroll does not work anymore in less

2016-09-02 Thread Guillaume Nodet (JIRA) 
Guillaume Nodet created KARAF-4691:
--

 Summary: Mouse scroll does not work anymore in less
 Key: KARAF-4691
 URL: https://issues.apache.org/jira/browse/KARAF-4691
 Project: Karaf
  Issue Type: Bug
  Components: karaf-shell
Affects Versions: 4.1.0
Reporter: Guillaume Nodet






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)