Re: Package versioning (was Re: [VOTE] Release webconsole 3.1.0 bundlerepository 1.6.4, karaf 1.6.2 (2nd try))
On Wed, Jun 16, 2010 at 23:47, Justin Edelson justinedel...@gmail.com wrote: On 6/16/10 5:36 PM, Guillaume Nodet wrote: On Wed, Jun 16, 2010 at 23:30, Justin Edelson justinedel...@gmail.com wrote: How could the use clause be used for JavaScript code? It is only relevant when there is more than one exporter of a package. A use clause from the javascript package on to the main webconsole package would ensure that importer of the javascript package can't be wired on to an imcompatible webconsole package. If you don't add this clause and have a webconsole 3.x and 3.y, you might end up being wired on to both versions. Except that the wiring between the JavaScript bundles actually happens at the client-side. If you had webconsole 3.x and 3.y bundles installed, which version would be served is determined by which bundle's activator got to HttpService first. If each HttpService exports its own javax.servlet package and check for compatibility, each servlet can only be wired to a single HttpService instance. There's work going on about extenders in the OSGi Alliance, hopefully we'll have a nice way to handle those problems. This looks like the type of semantic confusion which arises from repurposing manifest headers to represent something they were not meant to represent. Exporting a package with nothing, for the purpose of specifiying a provided environment (in this case javascript) sounds like a repurpose to me... It is a repurpose. But didn't this start with you wanting to repurpose the version of the Java package to specify the version of the front-end environment? In this case, the plugin is asked by the webconsole to compute something that the webconsole will use. If the way the computation needs to be done needs to change because the webconsole handle the result in a different way, then surely there is an incompatible change. As I said, I consider that this is part of the semantic implied when writing a plugin, so I still think it should be associated to the main package. So it's not about trying to version JQuery per se, it's about the semantics of the renderContent() method, nothing more than that. To be clear, my desire would be to have the OSGi Alliance define the right headers and have HttpService enhanced to take advantage of them. Barring that, an empty marker package is just the least worst choice IMHO. Justin Justin On 6/16/10 3:57 AM, Guillaume Nodet wrote: We'd have to add a use clause to make sure the plugin is wired to two compatible packages. Apart from that, I think it should work, but i'm still not convinced about that. It add more maintenance on both sides without much added value. On Wed, Jun 16, 2010 at 09:33, Felix Meschberger fmesc...@gmail.com wrote: Hi, On 15.06.2010 23:22, Justin Edelson wrote: On Tue, Jun 15, 2010 at 4:59 PM, Guillaume Nodet gno...@gmail.com wrote: On Tue, Jun 15, 2010 at 15:05, Felix Meschberger fmesc...@gmail.com wrote: Hi, On 15.06.2010 14:49, Guillaume Nodet wrote: What if you change the semantic of a function call without changing the signature ? I guess that's an incompatible change in theory, though still binary compatible. So we can't limit to binary compatibility for versioning imho, which mean there is some semantic involved. Yes, agreed, this is in fact an API change - and therefore requires an update in the exported package version. Nevertheless: I would say, that changing the semantics of a method is dangerous, just because it involves no change on the invocation level. So I would think, that changing the semantics of a method is even more dangerous than an incompatible API change. If you expect the user to take an action when upgrading, it means there is a (somewhat) incompatible change imho. Really depends on the kind of upgrade. Consider for example the Web Console upgrading to the next JQuery release. This would require a new Web Console release with an increased bundle version number. But since nothing in the API changes as a consequence of this JQuery upgrade, we must not increase the exported package version number ! BTW: [1] is highly recommended reading ! The document actually clearly talks about semantic compatibility. The question then comes down to: is the environment provided by the webconsole to the plugin part of the semantic of the package exported. I would think so. Why? The Java package org.apache.felix.webconsole should be able to be versioned independently of any front-end code. Just because there isn't a great way to expose/consume the version of the JavaScript libraries doesn't mean you should overload the meaning of the package version. Which leads me to have to bump the major version of the package if the html output of the plugin won't work anymore. One thing that might work is to define a synthetic package representing the front-end environment. But this would be versioned independently from the
[jira] Created: (FELIX-2417) NPE in Filter
NPE in Filter -- Key: FELIX-2417 URL: https://issues.apache.org/jira/browse/FELIX-2417 Project: Felix Issue Type: Bug Affects Versions: framework-3.0.0 Environment: java version 1.6.0_20 Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing) Reporter: Martin Zdila After upgrading framework from 2.0.5 to 3.0.0 I am getting many NPE exceptions Cannot register Component. I can't identify the core of the problem, but from what I see: in the org.apache.felix.framework.FilterImpl on line 145 the name = service.factoryPid but m_map doesn't contain such entry and so the key is set to null. The next call on the line 147 fails because key cannot be null in Hashtable.get(key). ERROR: my-cool-bundle (110): [my.cool.ServiceImpl] Cannot register Component java.lang.NullPointerException at java.util.Hashtable.get(Hashtable.java:334) at org.apache.felix.framework.FilterImpl$DictionaryCapability.getAttribute(FilterImpl.java:147) at org.apache.felix.framework.capabilityset.CapabilitySet.matchesInternal(CapabilitySet.java:269) at org.apache.felix.framework.capabilityset.CapabilitySet.matches(CapabilitySet.java:226) at org.apache.felix.framework.FilterImpl.match(FilterImpl.java:59) at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:538) at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:124) at org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.findConfigurations(ConfigurationComponentRegistry.java:267) at org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.findFactoryConfigurations(ConfigurationComponentRegistry.java:259) at org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.createComponentHolder(ConfigurationComponentRegistry.java:107) at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:244) at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:147) at org.apache.felix.scr.impl.BundleComponentActivator.init(BundleComponentActivator.java:111) at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:255) at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:173) at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:800) at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:728) at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:610) at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3734) at org.apache.felix.framework.Felix.startBundle(Felix.java:1807) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1188) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2418) add/remove/update/stop bundle using their bundle symbolic name
add/remove/update/stop bundle using their bundle symbolic name -- Key: FELIX-2418 URL: https://issues.apache.org/jira/browse/FELIX-2418 Project: Felix Issue Type: New Feature Components: Karaf Reporter: Charles Moulliard http://old.nabble.com/Suggestion-%3A-osgi%3Aupdate-stop-start-ts28828649.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2419) UnsupportedOperationException while installing features
UnsupportedOperationException while installing features
---
Key: FELIX-2419
URL: https://issues.apache.org/jira/browse/FELIX-2419
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.6.2
Reporter: Gert Vanthienen
Fix For: karaf 1.8.0
I was trying to install a few features on the Karaf 1.6.2 release candidate
build and encountered UnsupportedOperationException
Here are the commands I used
{noformat}
features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.2.0/xml/features
features:install camel-scala
features:install camel
{noformat}
This is the resulting exception's stack trace
{noformat}
10:46:07,342 | INFO | l Console Thread | Console |
araf.shell.console.jline.Console 198 | Exception caught while executing command
java.lang.UnsupportedOperationException
at java.util.AbstractList.remove(AbstractList.java:144)[:1.6.0_20]
at java.util.AbstractList$Itr.remove(AbstractList.java:360)[:1.6.0_20]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesWithOptionalPackagesToRefresh(FeaturesServiceImpl.java:445)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesToRefresh(FeaturesServiceImpl.java:389)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:252)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:222)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:218)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:51)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:41)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.runtime.shell.CommandProxy.execute(CommandProxy.java:50)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:229)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.karaf.shell.console.jline.Console.run(Console.java:180)[22:org.apache.felix.karaf.shell.console:1.6.2]
at java.lang.Thread.run(Thread.java:637)[:1.6.0_20]
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2419) UnsupportedOperationException while installing features
[
https://issues.apache.org/jira/browse/FELIX-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated FELIX-2419:
---
Assignee: Guillaume Nodet
Fix Version/s: karaf-1.6.2
(was: karaf 1.8.0)
UnsupportedOperationException while installing features
---
Key: FELIX-2419
URL: https://issues.apache.org/jira/browse/FELIX-2419
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.6.2
Reporter: Gert Vanthienen
Assignee: Guillaume Nodet
Fix For: karaf-1.6.2
I was trying to install a few features on the Karaf 1.6.2 release candidate
build and encountered UnsupportedOperationException
Here are the commands I used
{noformat}
features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.2.0/xml/features
features:install camel-scala
features:install camel
{noformat}
This is the resulting exception's stack trace
{noformat}
10:46:07,342 | INFO | l Console Thread | Console |
araf.shell.console.jline.Console 198 | Exception caught while executing
command
java.lang.UnsupportedOperationException
at java.util.AbstractList.remove(AbstractList.java:144)[:1.6.0_20]
at java.util.AbstractList$Itr.remove(AbstractList.java:360)[:1.6.0_20]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesWithOptionalPackagesToRefresh(FeaturesServiceImpl.java:445)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesToRefresh(FeaturesServiceImpl.java:389)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:252)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:222)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:218)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:51)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:41)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.runtime.shell.CommandProxy.execute(CommandProxy.java:50)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:229)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.karaf.shell.console.jline.Console.run(Console.java:180)[22:org.apache.felix.karaf.shell.console:1.6.2]
at java.lang.Thread.run(Thread.java:637)[:1.6.0_20]
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2419) UnsupportedOperationException while installing features
[
https://issues.apache.org/jira/browse/FELIX-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated FELIX-2419:
---
Attachment: FELIX-2419.diff
UnsupportedOperationException while installing features
---
Key: FELIX-2419
URL: https://issues.apache.org/jira/browse/FELIX-2419
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.6.2
Reporter: Gert Vanthienen
Assignee: Guillaume Nodet
Fix For: karaf-1.6.2
Attachments: FELIX-2419.diff
I was trying to install a few features on the Karaf 1.6.2 release candidate
build and encountered UnsupportedOperationException
Here are the commands I used
{noformat}
features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.2.0/xml/features
features:install camel-scala
features:install camel
{noformat}
This is the resulting exception's stack trace
{noformat}
10:46:07,342 | INFO | l Console Thread | Console |
araf.shell.console.jline.Console 198 | Exception caught while executing
command
java.lang.UnsupportedOperationException
at java.util.AbstractList.remove(AbstractList.java:144)[:1.6.0_20]
at java.util.AbstractList$Itr.remove(AbstractList.java:360)[:1.6.0_20]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesWithOptionalPackagesToRefresh(FeaturesServiceImpl.java:445)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesToRefresh(FeaturesServiceImpl.java:389)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:252)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:222)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:218)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:51)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:41)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.runtime.shell.CommandProxy.execute(CommandProxy.java:50)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:229)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.karaf.shell.console.jline.Console.run(Console.java:180)[22:org.apache.felix.karaf.shell.console:1.6.2]
at java.lang.Thread.run(Thread.java:637)[:1.6.0_20]
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ANNOUNCE] Karaf is moving to top level
The Apache Software Foundation has approved yesterday the move of Karaf as a top level project. The whole community is thrilled and will strive to make the project even better and more successful. It will take some time to move all the infrastructure, so we'll keep everyone posted. -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
Re: [ANNOUNCE] Karaf is moving to top level
Thanks Guillaume, If you need any help (for example to move Jira tasks to the new location, etc), don't hesitate to ping me. Regards JB On 06/17/2010 07:48 PM, Guillaume Nodet wrote: The Apache Software Foundation has approved yesterday the move of Karaf as a top level project. The whole community is thrilled and will strive to make the project even better and more successful. It will take some time to move all the infrastructure, so we'll keep everyone posted.
[jira] Created: (FELIX-2420) Enum support for @Property annotation
Enum support for @Property annotation - Key: FELIX-2420 URL: https://issues.apache.org/jira/browse/FELIX-2420 Project: Felix Issue Type: Improvement Components: iPOJO Reporter: Joel Schuster Priority: Minor It would be nice if the @Property annotation would support Enum types as well as the String and numeric types. Ideally the value would be taken as a String or numeric and the appropriate Enum would be chosen based on the valueOf method or the ordinal. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2419) UnsupportedOperationException while installing features
[
https://issues.apache.org/jira/browse/FELIX-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved FELIX-2419.
Resolution: Fixed
Fixed in http://svn.apache.org/viewvc?view=revisionrevision=955727
UnsupportedOperationException while installing features
---
Key: FELIX-2419
URL: https://issues.apache.org/jira/browse/FELIX-2419
Project: Felix
Issue Type: Bug
Components: Karaf
Affects Versions: karaf-1.6.2
Reporter: Gert Vanthienen
Assignee: Guillaume Nodet
Fix For: karaf-1.6.2
Attachments: FELIX-2419.diff
I was trying to install a few features on the Karaf 1.6.2 release candidate
build and encountered UnsupportedOperationException
Here are the commands I used
{noformat}
features:addUrl mvn:org.apache.camel.karaf/apache-camel/2.2.0/xml/features
features:install camel-scala
features:install camel
{noformat}
This is the resulting exception's stack trace
{noformat}
10:46:07,342 | INFO | l Console Thread | Console |
araf.shell.console.jline.Console 198 | Exception caught while executing
command
java.lang.UnsupportedOperationException
at java.util.AbstractList.remove(AbstractList.java:144)[:1.6.0_20]
at java.util.AbstractList$Itr.remove(AbstractList.java:360)[:1.6.0_20]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesWithOptionalPackagesToRefresh(FeaturesServiceImpl.java:445)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.findBundlesToRefresh(FeaturesServiceImpl.java:389)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:252)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:222)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:218)[20:org.apache.felix.karaf.features.core:1.6.2]
at
org.apache.felix.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:51)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:39)[27:org.apache.felix.karaf.features.command:1.6.2]
at
org.apache.felix.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:41)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:35)[22:org.apache.felix.karaf.shell.console:1.6.2]
at
org.apache.felix.gogo.runtime.shell.CommandProxy.execute(CommandProxy.java:50)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:229)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[17:org.apache.felix.gogo.runtime:0.4.0]
at
org.apache.felix.karaf.shell.console.jline.Console.run(Console.java:180)[22:org.apache.felix.karaf.shell.console:1.6.2]
at java.lang.Thread.run(Thread.java:637)[:1.6.0_20]
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2421) Implicit bootdelegation doesn't ignore classloaders if they are inner classes
Implicit bootdelegation doesn't ignore classloaders if they are inner classes - Key: FELIX-2421 URL: https://issues.apache.org/jira/browse/FELIX-2421 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-3.0.0 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: framework-3.2.0 The implicit (a.k.a., magic) bootdelegation doesn't bootdelegate if it finds a classloader on the stack which is an inner class of a bundle-loaded class. If the classloader would be loaded from a bundle it will not prevent bootdelegation but if it happens to be an inner class it will. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2421) Implicit bootdelegation doesn't ignore classloaders if they are inner classes
[ https://issues.apache.org/jira/browse/FELIX-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved FELIX-2421. --- Resolution: Fixed Fixed in trunk. Implicit bootdelegation doesn't ignore classloaders if they are inner classes - Key: FELIX-2421 URL: https://issues.apache.org/jira/browse/FELIX-2421 Project: Felix Issue Type: Bug Components: Framework Affects Versions: framework-3.0.0 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: framework-3.2.0 The implicit (a.k.a., magic) bootdelegation doesn't bootdelegate if it finds a classloader on the stack which is an inner class of a bundle-loaded class. If the classloader would be loaded from a bundle it will not prevent bootdelegation but if it happens to be an inner class it will. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
