From issues at jboss.org Thu Apr 2 18:44:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 2 Apr 2015 18:44:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-770) Capability org.jboss.as.osgi.http fails to start In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-770: ---------------------------------- Priority: Blocker (was: Major) > Capability org.jboss.as.osgi.http fails to start > ------------------------------------------------ > > Key: JBOSGI-770 > URL: https://issues.jboss.org/browse/JBOSGI-770 > Project: JBoss OSGi > Issue Type: Bug > Environment: WildFly 8.2.0.Final > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Blocker > > {noformat} > 2015-04-01 11:38:59,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "osgi")]) - failure description: > {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.common.server.httpservice.factory is missing [jboss.serverManagement.controller.management.http]"]} > 2015-04-01 11:38:59,472 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.serverManagement.controller.management.http (missing) dependents: [service jboss.web.common.server.httpservice.factory] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 2 18:44:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 2 Apr 2015 18:44:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-770) Capability org.jboss.as.osgi.http fails to start In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-770: ------------------------------------- Summary: Capability org.jboss.as.osgi.http fails to start Key: JBOSGI-770 URL: https://issues.jboss.org/browse/JBOSGI-770 Project: JBoss OSGi Issue Type: Bug Environment: WildFly 8.2.0.Final Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov {noformat} 2015-04-01 11:38:59,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "osgi")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.common.server.httpservice.factory is missing [jboss.serverManagement.controller.management.http]"]} 2015-04-01 11:38:59,472 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.serverManagement.controller.management.http (missing) dependents: [service jboss.web.common.server.httpservice.factory] {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 2 18:45:19 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 2 Apr 2015 18:45:19 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-770) Capability org.jboss.as.osgi.http fails to start In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-770 started by Arcadiy Ivanov. --------------------------------------------- > Capability org.jboss.as.osgi.http fails to start > ------------------------------------------------ > > Key: JBOSGI-770 > URL: https://issues.jboss.org/browse/JBOSGI-770 > Project: JBoss OSGi > Issue Type: Bug > Environment: WildFly 8.2.0.Final > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Blocker > > {noformat} > 2015-04-01 11:38:59,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "osgi")]) - failure description: > {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.common.server.httpservice.factory is missing [jboss.serverManagement.controller.management.http]"]} > 2015-04-01 11:38:59,472 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.serverManagement.controller.management.http (missing) dependents: [service jboss.web.common.server.httpservice.factory] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 5 21:52:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 5 Apr 2015 21:52:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-566) Add support for entry/resource related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov reassigned JBOSGI-566: ------------------------------------- Assignee: Arcadiy Ivanov > Add support for entry/resource related APIs on Module adaptors > -------------------------------------------------------------- > > Key: JBOSGI-566 > URL: https://issues.jboss.org/browse/JBOSGI-566 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 5 21:52:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 5 Apr 2015 21:52:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-566) Add support for entry/resource related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov reopened JBOSGI-566: ----------------------------------- Will implement > Add support for entry/resource related APIs on Module adaptors > -------------------------------------------------------------- > > Key: JBOSGI-566 > URL: https://issues.jboss.org/browse/JBOSGI-566 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Apr 6 06:58:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 6 Apr 2015 06:58:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-566) Add support for entry/resource related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-566 started by Arcadiy Ivanov. --------------------------------------------- > Add support for entry/resource related APIs on Module adaptors > -------------------------------------------------------------- > > Key: JBOSGI-566 > URL: https://issues.jboss.org/browse/JBOSGI-566 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Apr 6 07:07:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 6 Apr 2015 07:07:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-566) Add support for entry/resource related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-566: ---------------------------------- Fix Version/s: JBossOSGI 2.3.1 Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/16 > Add support for entry/resource related APIs on Module adaptors > -------------------------------------------------------------- > > Key: JBOSGI-566 > URL: https://issues.jboss.org/browse/JBOSGI-566 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Apr 6 07:08:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 6 Apr 2015 07:08:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-566) Add support for entry/resource related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-566. ----------------------------------- Resolution: Done > Add support for entry/resource related APIs on Module adaptors > -------------------------------------------------------------- > > Key: JBOSGI-566 > URL: https://issues.jboss.org/browse/JBOSGI-566 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Apr 6 08:18:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 6 Apr 2015 08:18:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-770) Capability org.jboss.as.osgi.http fails to start In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-770: ---------------------------------- Fix Version/s: JBossOSGI 2.3.1 Git Pull Request: https://github.com/jbosgi/jbosgi/pull/8 > Capability org.jboss.as.osgi.http fails to start > ------------------------------------------------ > > Key: JBOSGI-770 > URL: https://issues.jboss.org/browse/JBOSGI-770 > Project: JBoss OSGi > Issue Type: Bug > Environment: WildFly 8.2.0.Final > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Blocker > Fix For: JBossOSGI 2.3.1 > > > {noformat} > 2015-04-01 11:38:59,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "osgi")]) - failure description: > {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.common.server.httpservice.factory is missing [jboss.serverManagement.controller.management.http]"]} > 2015-04-01 11:38:59,472 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.serverManagement.controller.management.http (missing) dependents: [service jboss.web.common.server.httpservice.factory] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Apr 6 09:25:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 6 Apr 2015 09:25:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-770) Capability org.jboss.as.osgi.http fails to start in domain In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-770: ---------------------------------- Summary: Capability org.jboss.as.osgi.http fails to start in domain (was: Capability org.jboss.as.osgi.http fails to start) > Capability org.jboss.as.osgi.http fails to start in domain > ---------------------------------------------------------- > > Key: JBOSGI-770 > URL: https://issues.jboss.org/browse/JBOSGI-770 > Project: JBoss OSGi > Issue Type: Bug > Environment: WildFly 8.2.0.Final > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Blocker > Fix For: JBossOSGI 2.3.1 > > > {noformat} > 2015-04-01 11:38:59,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "osgi")]) - failure description: > {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.common.server.httpservice.factory is missing [jboss.serverManagement.controller.management.http]"]} > 2015-04-01 11:38:59,472 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.serverManagement.controller.management.http (missing) dependents: [service jboss.web.common.server.httpservice.factory] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Apr 6 09:26:19 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 6 Apr 2015 09:26:19 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-770) Capability org.jboss.as.osgi.http fails to start in domain In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-770. ----------------------------------- Resolution: Done > Capability org.jboss.as.osgi.http fails to start in domain > ---------------------------------------------------------- > > Key: JBOSGI-770 > URL: https://issues.jboss.org/browse/JBOSGI-770 > Project: JBoss OSGi > Issue Type: Bug > Environment: WildFly 8.2.0.Final > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Blocker > Fix For: JBossOSGI 2.3.1 > > > {noformat} > 2015-04-01 11:38:59,428 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "osgi")]) - failure description: > {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.common.server.httpservice.factory is missing [jboss.serverManagement.controller.management.http]"]} > 2015-04-01 11:38:59,472 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.serverManagement.controller.management.http (missing) dependents: [service jboss.web.common.server.httpservice.factory] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Apr 6 21:56:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 6 Apr 2015 21:56:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-765) HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-765: ---------------------------------- Fix Version/s: JBossOSGI 2.3.1 > HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported > ------------------------------------------------------------------------------------------ > > Key: JBOSGI-765 > URL: https://issues.jboss.org/browse/JBOSGI-765 > Project: JBoss OSGi > Issue Type: Bug > Components: framework > Affects Versions: JBossOSGi 2.2.0 > Environment: WildFly 8.1.0.Final > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Minor > Fix For: JBossOSGI 2.3.1 > > > Whenever an OSGI bundle contains JAXB-annotated classes, and Manifest of that bundle does not contain "Import-Package: javax.xml.bind.annotation" such bundle will be: > 1) Successfully installed > 2) Successfully activated > 3) All classes within said bundle will be properly loaded > 4) X.class.getDeclaredAnnotations() will return empty array if the only annotations on the class X are the annotations that reside in javax.xml.bind.annotation. > No "NoClassDefFoundError" or "ClassNotFoundException" are ever thrown, no errors are logged. However, due to declared annotations not being present during class introspection, if such class X is used in with RESTEasy the following exception is thrown by the rest service: > org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: java.util.ArrayList of media type: application/xml > if the return type of REST API call is List. > While workaround is quite simple (below), the concern is that such hidden behavior may result in other spurious failures of unknown origin in JAXB and elsewhere, since no indication that bundle resolution and linkage has failed is given anywhere. > Marked Minor since workaround exists but I would recommend escalation. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Apr 7 11:42:20 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 7 Apr 2015 11:42:20 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-765) HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-765. ----------------------------------- Resolution: Won't Fix > HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported > ------------------------------------------------------------------------------------------ > > Key: JBOSGI-765 > URL: https://issues.jboss.org/browse/JBOSGI-765 > Project: JBoss OSGi > Issue Type: Bug > Components: framework > Affects Versions: JBossOSGi 2.2.0 > Environment: WildFly 8.1.0.Final > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Minor > Fix For: JBossOSGI 2.3.1 > > > Whenever an OSGI bundle contains JAXB-annotated classes, and Manifest of that bundle does not contain "Import-Package: javax.xml.bind.annotation" such bundle will be: > 1) Successfully installed > 2) Successfully activated > 3) All classes within said bundle will be properly loaded > 4) X.class.getDeclaredAnnotations() will return empty array if the only annotations on the class X are the annotations that reside in javax.xml.bind.annotation. > No "NoClassDefFoundError" or "ClassNotFoundException" are ever thrown, no errors are logged. However, due to declared annotations not being present during class introspection, if such class X is used in with RESTEasy the following exception is thrown by the rest service: > org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: java.util.ArrayList of media type: application/xml > if the return type of REST API call is List. > While workaround is quite simple (below), the concern is that such hidden behavior may result in other spurious failures of unknown origin in JAXB and elsewhere, since no indication that bundle resolution and linkage has failed is given anywhere. > Marked Minor since workaround exists but I would recommend escalation. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Tue Apr 7 11:42:22 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Tue, 7 Apr 2015 11:42:22 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-765) HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056593#comment-13056593 ] Arcadiy Ivanov commented on JBOSGI-765: --------------------------------------- This seems to be a correct behavior under JLS - https://bugs.openjdk.java.net/browse/JDK-6322301 Class.getAnnotations() never throws ClassNotFoundException or TypeNotPresentException but silently strips the annotations altogether. > HostBundleClassLoader silently deletes JAXB annotations from Class if package not imported > ------------------------------------------------------------------------------------------ > > Key: JBOSGI-765 > URL: https://issues.jboss.org/browse/JBOSGI-765 > Project: JBoss OSGi > Issue Type: Bug > Components: framework > Affects Versions: JBossOSGi 2.2.0 > Environment: WildFly 8.1.0.Final > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Minor > Fix For: JBossOSGI 2.3.1 > > > Whenever an OSGI bundle contains JAXB-annotated classes, and Manifest of that bundle does not contain "Import-Package: javax.xml.bind.annotation" such bundle will be: > 1) Successfully installed > 2) Successfully activated > 3) All classes within said bundle will be properly loaded > 4) X.class.getDeclaredAnnotations() will return empty array if the only annotations on the class X are the annotations that reside in javax.xml.bind.annotation. > No "NoClassDefFoundError" or "ClassNotFoundException" are ever thrown, no errors are logged. However, due to declared annotations not being present during class introspection, if such class X is used in with RESTEasy the following exception is thrown by the rest service: > org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: java.util.ArrayList of media type: application/xml > if the return type of REST API call is List. > While workaround is quite simple (below), the concern is that such hidden behavior may result in other spurious failures of unknown origin in JAXB and elsewhere, since no indication that bundle resolution and linkage has failed is given anywhere. > Marked Minor since workaround exists but I would recommend escalation. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Apr 8 17:31:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Wed, 8 Apr 2015 17:31:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-771) NPE in FallbackLoader In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-771: ------------------------------------- Summary: NPE in FallbackLoader Key: JBOSGI-771 URL: https://issues.jboss.org/browse/JBOSGI-771 Project: JBoss OSGi Issue Type: Bug Components: framework Affects Versions: JBossOSGi 2.2.0 Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov Priority: Blocker Fix For: JBossOSGI 2.3.1 {noformat} Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: org.apache.servicemix.specs.activation-api-1.1:2.2.0 at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:624) at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:524) at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:576) at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:129) ... 5 more Caused by: java.lang.NullPointerException at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:155) at org.jboss.modules.Module.loadModuleClass(Module.java:576) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:146) [jboss-modules.jar:1.3.3.Final] at org.jboss.osgi.framework.internal.HostBundleRevision.loadClassInternal(HostBundleRevision.java:135) at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:119) at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:513) at org.apache.servicemix.specs.activation.Activator.register(Activator.java:60) at org.apache.servicemix.specs.locator.Activator.start(Activator.java:70) at org.apache.servicemix.specs.activation.Activator.start(Activator.java:43) at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:598) ... 8 more {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Apr 8 21:16:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Wed, 8 Apr 2015 21:16:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-771) NPE in FallbackLoader due to absent BundleWiring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-771: ---------------------------------- Summary: NPE in FallbackLoader due to absent BundleWiring (was: NPE in FallbackLoader) > NPE in FallbackLoader due to absent BundleWiring > ------------------------------------------------ > > Key: JBOSGI-771 > URL: https://issues.jboss.org/browse/JBOSGI-771 > Project: JBoss OSGi > Issue Type: Bug > Components: framework > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Blocker > Fix For: JBossOSGI 2.3.1 > > > {noformat} > Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: org.apache.servicemix.specs.activation-api-1.1:2.2.0 > at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:624) > at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:524) > at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:576) > at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:129) > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:155) > at org.jboss.modules.Module.loadModuleClass(Module.java:576) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:146) [jboss-modules.jar:1.3.3.Final] > at org.jboss.osgi.framework.internal.HostBundleRevision.loadClassInternal(HostBundleRevision.java:135) > at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:119) > at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:513) > at org.apache.servicemix.specs.activation.Activator.register(Activator.java:60) > at org.apache.servicemix.specs.locator.Activator.start(Activator.java:70) > at org.apache.servicemix.specs.activation.Activator.start(Activator.java:43) > at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:598) > ... 8 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 9 02:55:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 9 Apr 2015 02:55:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-771) NPE in FallbackLoader due to absent BundleWiring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-771: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/19 > NPE in FallbackLoader due to absent BundleWiring > ------------------------------------------------ > > Key: JBOSGI-771 > URL: https://issues.jboss.org/browse/JBOSGI-771 > Project: JBoss OSGi > Issue Type: Bug > Components: framework > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Blocker > Fix For: JBossOSGI 2.3.1 > > > {noformat} > Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: org.apache.servicemix.specs.activation-api-1.1:2.2.0 > at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:624) > at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:524) > at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:576) > at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:129) > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:155) > at org.jboss.modules.Module.loadModuleClass(Module.java:576) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:146) [jboss-modules.jar:1.3.3.Final] > at org.jboss.osgi.framework.internal.HostBundleRevision.loadClassInternal(HostBundleRevision.java:135) > at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:119) > at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:513) > at org.apache.servicemix.specs.activation.Activator.register(Activator.java:60) > at org.apache.servicemix.specs.locator.Activator.start(Activator.java:70) > at org.apache.servicemix.specs.activation.Activator.start(Activator.java:43) > at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:598) > ... 8 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 9 02:55:19 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 9 Apr 2015 02:55:19 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-771) NPE in FallbackLoader due to absent BundleWiring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-771. ----------------------------------- Resolution: Done > NPE in FallbackLoader due to absent BundleWiring > ------------------------------------------------ > > Key: JBOSGI-771 > URL: https://issues.jboss.org/browse/JBOSGI-771 > Project: JBoss OSGi > Issue Type: Bug > Components: framework > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Blocker > Fix For: JBossOSGI 2.3.1 > > > {noformat} > Caused by: org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: org.apache.servicemix.specs.activation-api-1.1:2.2.0 > at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:624) > at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:524) > at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:576) > at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:129) > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.osgi.framework.internal.FallbackLoader.loadClassLocal(FallbackLoader.java:155) > at org.jboss.modules.Module.loadModuleClass(Module.java:576) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:146) [jboss-modules.jar:1.3.3.Final] > at org.jboss.osgi.framework.internal.HostBundleRevision.loadClassInternal(HostBundleRevision.java:135) > at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:119) > at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:513) > at org.apache.servicemix.specs.activation.Activator.register(Activator.java:60) > at org.apache.servicemix.specs.locator.Activator.start(Activator.java:70) > at org.apache.servicemix.specs.activation.Activator.start(Activator.java:43) > at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:598) > ... 8 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Mon Apr 13 12:25:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Mon, 13 Apr 2015 12:25:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-772) Remove OSGi Enterprise classes from JBOSGi projects In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-772: ------------------------------------- Summary: Remove OSGi Enterprise classes from JBOSGi projects Key: JBOSGI-772 URL: https://issues.jboss.org/browse/JBOSGI-772 Project: JBoss OSGi Issue Type: Task Affects Versions: JBossOSGi 2.2.0 Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov Fix For: JBossOSGI 2.3.1 Should reference OSGi classes directly -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Apr 15 03:22:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Wed, 15 Apr 2015 03:22:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-772) Remove OSGi Enterprise classes from JBOSGi projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-772. ----------------------------------- Resolution: Rejected Apparently even Felix and Aries carry parts of OSGi Specification directly so it's the norm. > Remove OSGi Enterprise classes from JBOSGi projects > --------------------------------------------------- > > Key: JBOSGI-772 > URL: https://issues.jboss.org/browse/JBOSGI-772 > Project: JBoss OSGi > Issue Type: Task > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > Should reference OSGi classes directly -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Wed Apr 15 03:22:19 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Wed, 15 Apr 2015 03:22:19 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-772) Remove OSGi Enterprise classes from JBOSGi projects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov closed JBOSGI-772. --------------------------------- > Remove OSGi Enterprise classes from JBOSGi projects > --------------------------------------------------- > > Key: JBOSGI-772 > URL: https://issues.jboss.org/browse/JBOSGI-772 > Project: JBoss OSGi > Issue Type: Task > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > Should reference OSGi classes directly -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 16 01:29:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 16 Apr 2015 01:29:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-773) Rewrite OSGi Subsystem for domain support In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-773: ------------------------------------- Summary: Rewrite OSGi Subsystem for domain support Key: JBOSGI-773 URL: https://issues.jboss.org/browse/JBOSGI-773 Project: JBoss OSGi Issue Type: Feature Request Affects Versions: JBossOSGi 2.2.0 Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov Fix For: JBossOSGI 2.3.1 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 16 01:29:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 16 Apr 2015 01:29:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-773) Rewrite OSGi Subsystem for domain support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-773 started by Arcadiy Ivanov. --------------------------------------------- > Rewrite OSGi Subsystem for domain support > ----------------------------------------- > > Key: JBOSGI-773 > URL: https://issues.jboss.org/browse/JBOSGI-773 > Project: JBoss OSGi > Issue Type: Feature Request > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 16 14:57:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 16 Apr 2015 14:57:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-567) Add support for manifest header related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov reopened JBOSGI-567: ----------------------------------- Assignee: Arcadiy Ivanov > Add support for manifest header related APIs on Module adaptors > --------------------------------------------------------------- > > Key: JBOSGI-567 > URL: https://issues.jboss.org/browse/JBOSGI-567 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 16 14:58:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 16 Apr 2015 14:58:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-567) Add support for manifest header related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-567 started by Arcadiy Ivanov. --------------------------------------------- > Add support for manifest header related APIs on Module adaptors > --------------------------------------------------------------- > > Key: JBOSGI-567 > URL: https://issues.jboss.org/browse/JBOSGI-567 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 16 22:32:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 16 Apr 2015 22:32:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-567) Add support for manifest header related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-567: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/20 > Add support for manifest header related APIs on Module adaptors > --------------------------------------------------------------- > > Key: JBOSGI-567 > URL: https://issues.jboss.org/browse/JBOSGI-567 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 16 22:38:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 16 Apr 2015 22:38:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-567) Add support for manifest header related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-567. ----------------------------------- Resolution: Done > Add support for manifest header related APIs on Module adaptors > --------------------------------------------------------------- > > Key: JBOSGI-567 > URL: https://issues.jboss.org/browse/JBOSGI-567 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Thu Apr 16 22:38:19 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Thu, 16 Apr 2015 22:38:19 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-567) Add support for manifest header related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-567: ---------------------------------- Fix Version/s: JBossOSGI 2.3.1 > Add support for manifest header related APIs on Module adaptors > --------------------------------------------------------------- > > Key: JBOSGI-567 > URL: https://issues.jboss.org/browse/JBOSGI-567 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Apr 17 01:13:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Fri, 17 Apr 2015 01:13:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-567) Add support for manifest header related APIs on Module adaptors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059940#comment-13059940 ] Arcadiy Ivanov commented on JBOSGI-567: --------------------------------------- Implemented > Add support for manifest header related APIs on Module adaptors > --------------------------------------------------------------- > > Key: JBOSGI-567 > URL: https://issues.jboss.org/browse/JBOSGI-567 > Project: JBoss OSGi > Issue Type: Task > Components: framework > Reporter: Thomas Diesler > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Fri Apr 17 01:27:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Fri, 17 Apr 2015 01:27:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-773) Rewrite OSGi Subsystem for domain support In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-773: ---------------------------------- Component/s: wildfly > Rewrite OSGi Subsystem for domain support > ----------------------------------------- > > Key: JBOSGI-773 > URL: https://issues.jboss.org/browse/JBOSGI-773 > Project: JBoss OSGi > Issue Type: Feature Request > Components: wildfly > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 08:08:19 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 08:08:19 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-774) Cleanup solution for JBOSGI-567 In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-774: ------------------------------------- Summary: Cleanup solution for JBOSGI-567 Key: JBOSGI-774 URL: https://issues.jboss.org/browse/JBOSGI-774 Project: JBoss OSGi Issue Type: Task Components: framework, wildfly Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov Fix For: JBossOSGI 2.3.1 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 08:08:19 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 08:08:19 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-774) Cleanup solution for JBOSGI-567 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-774 started by Arcadiy Ivanov. --------------------------------------------- > Cleanup solution for JBOSGI-567 > ------------------------------- > > Key: JBOSGI-774 > URL: https://issues.jboss.org/browse/JBOSGI-774 > Project: JBoss OSGi > Issue Type: Task > Components: framework, wildfly > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 08:12:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 08:12:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-774) Cleanup solution for JBOSGI-567 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-774: ---------------------------------- Description: JBOSGI-567 solution introduced AbstractBundleRevisionAdaptor detecting if OSGiMetaData was present in the attachment and creating one if it wasn't. This solution, however usurps the responsibility from ModuleIdentityRepositoryIntegration and copies code from ModuleIdentityRepository. > Cleanup solution for JBOSGI-567 > ------------------------------- > > Key: JBOSGI-774 > URL: https://issues.jboss.org/browse/JBOSGI-774 > Project: JBoss OSGi > Issue Type: Task > Components: framework, wildfly > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > JBOSGI-567 solution introduced AbstractBundleRevisionAdaptor detecting if OSGiMetaData was present in the attachment and creating one if it wasn't. > This solution, however usurps the responsibility from ModuleIdentityRepositoryIntegration and copies code from ModuleIdentityRepository. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 08:16:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 08:16:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-775) ServiceLoader should work with module-based dependencies or capabilities In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-775: ------------------------------------- Summary: ServiceLoader should work with module-based dependencies or capabilities Key: JBOSGI-775 URL: https://issues.jboss.org/browse/JBOSGI-775 Project: JBoss OSGi Issue Type: Enhancement Components: framework, resolver Affects Versions: JBossOSGi 2.2.0 Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov Fix For: JBossOSGI 2.3.1 A bundle should be able to load Java SPI services from modules turned into OSGi Framework capabilities or from modules on which OSGi Bundle declares explicit MSC dependency with services and/or meta-inf option. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 08:17:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 08:17:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-775) ServiceLoader should work with module dependencies and capabilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-775: ---------------------------------- Summary: ServiceLoader should work with module dependencies and capabilities (was: ServiceLoader should work with module-based dependencies or capabilities) > ServiceLoader should work with module dependencies and capabilities > ------------------------------------------------------------------- > > Key: JBOSGI-775 > URL: https://issues.jboss.org/browse/JBOSGI-775 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > A bundle should be able to load Java SPI services from modules turned into OSGi Framework capabilities or from modules on which OSGi Bundle declares explicit MSC dependency with services and/or meta-inf option. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 08:17:19 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 08:17:19 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-775) ServiceLoader should work with module dependencies and capabilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-775 started by Arcadiy Ivanov. --------------------------------------------- > ServiceLoader should work with module dependencies and capabilities > ------------------------------------------------------------------- > > Key: JBOSGI-775 > URL: https://issues.jboss.org/browse/JBOSGI-775 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > A bundle should be able to load Java SPI services from modules turned into OSGi Framework capabilities or from modules on which OSGi Bundle declares explicit MSC dependency with services and/or meta-inf option. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 08:28:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 08:28:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-775) ServiceLoader should work with module dependencies and capabilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-775: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/21, https://github.com/jbosgi/jbosgi-resolver/pull/7 > ServiceLoader should work with module dependencies and capabilities > ------------------------------------------------------------------- > > Key: JBOSGI-775 > URL: https://issues.jboss.org/browse/JBOSGI-775 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > A bundle should be able to load Java SPI services from modules turned into OSGi Framework capabilities or from modules on which OSGi Bundle declares explicit MSC dependency with services and/or meta-inf option. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 08:38:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 08:38:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-775) ServiceLoader should work with module dependencies and capabilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060388#comment-13060388 ] Arcadiy Ivanov commented on JBOSGI-775: --------------------------------------- The following statements taken from the test case allow to load Java services: {noformat} DynamicImport-Package: META-INF.services, org.jboss.test.osgi.framework.serviceloader.* Dependencies: moduleA meta-inf {noformat} * {{meta-inf}} can be replaces with {{services}} per [WildFly 8 Classloading|https://docs.jboss.org/author/display/WFLY8/Class+Loading+in+WildFly] * {{Dependencies}} are unnecessary if the capabilities are specified in the JBOSGI WildFly Subsystem configuration. * {{DynamicImport-Package}} may be {{*}}, but that will increase the classloading overhead. It's better to increase dynamic package import specificity to speed up classloading. > ServiceLoader should work with module dependencies and capabilities > ------------------------------------------------------------------- > > Key: JBOSGI-775 > URL: https://issues.jboss.org/browse/JBOSGI-775 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > A bundle should be able to load Java SPI services from modules turned into OSGi Framework capabilities or from modules on which OSGi Bundle declares explicit MSC dependency with services and/or meta-inf option. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 08:47:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 08:47:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-775) ServiceLoader should work with module dependencies and capabilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-775 stopped by Arcadiy Ivanov. --------------------------------------------- > ServiceLoader should work with module dependencies and capabilities > ------------------------------------------------------------------- > > Key: JBOSGI-775 > URL: https://issues.jboss.org/browse/JBOSGI-775 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > A bundle should be able to load Java SPI services from modules turned into OSGi Framework capabilities or from modules on which OSGi Bundle declares explicit MSC dependency with services and/or meta-inf option. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 08:48:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 08:48:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-775) ServiceLoader should work with module dependencies and capabilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-775. ----------------------------------- Resolution: Done > ServiceLoader should work with module dependencies and capabilities > ------------------------------------------------------------------- > > Key: JBOSGI-775 > URL: https://issues.jboss.org/browse/JBOSGI-775 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > A bundle should be able to load Java SPI services from modules turned into OSGi Framework capabilities or from modules on which OSGi Bundle declares explicit MSC dependency with services and/or meta-inf option. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 17:01:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 17:01:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-775) ServiceLoader should work with module dependencies and capabilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-775: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/21, https://github.com/jbosgi/jbosgi-resolver/pull/7, https://github.com/jbosgi/jbosgi/pull/10 (was: https://github.com/jbosgi/jbosgi-framework/pull/21, https://github.com/jbosgi/jbosgi-resolver/pull/7) > ServiceLoader should work with module dependencies and capabilities > ------------------------------------------------------------------- > > Key: JBOSGI-775 > URL: https://issues.jboss.org/browse/JBOSGI-775 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > A bundle should be able to load Java SPI services from modules turned into OSGi Framework capabilities or from modules on which OSGi Bundle declares explicit MSC dependency with services and/or meta-inf option. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 17:04:19 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 17:04:19 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-776) Improve FallbackLoader logging to aid DynamicImport-Package troubleshooting In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-776: ------------------------------------- Summary: Improve FallbackLoader logging to aid DynamicImport-Package troubleshooting Key: JBOSGI-776 URL: https://issues.jboss.org/browse/JBOSGI-776 Project: JBoss OSGi Issue Type: Enhancement Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov Priority: Minor Fix For: JBossOSGI 2.3.1 -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 22:25:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 22:25:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-775) ServiceLoader should work with module dependencies and capabilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-775: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-framework/pull/21, https://github.com/jbosgi/jbosgi-resolver/pull/7, https://github.com/jbosgi/jbosgi/pull/10, https://github.com/jbosgi/jbosgi-repository/pull/14 (was: https://github.com/jbosgi/jbosgi-framework/pull/21, https://github.com/jbosgi/jbosgi-resolver/pull/7, https://github.com/jbosgi/jbosgi/pull/10) > ServiceLoader should work with module dependencies and capabilities > ------------------------------------------------------------------- > > Key: JBOSGI-775 > URL: https://issues.jboss.org/browse/JBOSGI-775 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver > Affects Versions: JBossOSGi 2.2.0 > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > A bundle should be able to load Java SPI services from modules turned into OSGi Framework capabilities or from modules on which OSGi Bundle declares explicit MSC dependency with services and/or meta-inf option. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 22:28:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 22:28:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-777) Filter-out zero-length path from module-exported paths In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-777: ------------------------------------- Summary: Filter-out zero-length path from module-exported paths Key: JBOSGI-777 URL: https://issues.jboss.org/browse/JBOSGI-777 Project: JBoss OSGi Issue Type: Bug Reporter: Arcadiy Ivanov Assignee: Arcadiy Ivanov Fix For: JBossOSGI 2.3.1 {noformat} 22:15:15,816 ERROR [org.jboss.osgi.repository] (MSC service thread 1-8) JBOSGI020401: Cannot create resource for: javax.jws.api: org.jboss.osgi.resolver.ResourceBuilderException: JBOSGI010908: Cannot initialize resource from: [javax.jws.api:0.0.0] at org.jboss.osgi.resolver.spi.AbstractResourceBuilder.loadFrom(AbstractResourceBuilder.java:316) [jbosgi-resolver-api-4.0.4.Final-SNAPSHOT.jar:4.0.4.Final-SNAPSHOT] at org.jboss.osgi.repository.spi.AbstractRepository.getTargetResource(AbstractRepository.java:249) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] at org.jboss.osgi.repository.spi.ModuleIdentityRepository.getTargetResource(ModuleIdentityRepository.java:120) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] at org.jboss.osgi.repository.spi.ModuleIdentityRepository.findProviders(ModuleIdentityRepository.java:108) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] at org.jboss.as.osgi.service.ModuleIdentityRepositoryIntegration.findProviders(ModuleIdentityRepositoryIntegration.java:108) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] at org.jboss.as.osgi.service.BootstrapBundlesIntegration.installInitialModuleCapability(BootstrapBundlesIntegration.java:181) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] at org.jboss.as.osgi.service.BootstrapBundlesIntegration.start(BootstrapBundlesIntegration.java:135) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] Caused by: java.lang.IllegalArgumentException: No paths for clause: at org.jboss.osgi.metadata.internal.ManifestParser.parse(ManifestParser.java:102) at org.jboss.osgi.metadata.internal.ManifestParser.parsePackages(ManifestParser.java:47) at org.jboss.osgi.metadata.internal.PackageAttributeListValueCreator.useString(PackageAttributeListValueCreator.java:35) at org.jboss.osgi.metadata.internal.PackageAttributeListValueCreator.useString(PackageAttributeListValueCreator.java:32) at org.jboss.osgi.metadata.internal.AbstractValueCreator.createValue(AbstractValueCreator.java:45) at org.jboss.osgi.metadata.internal.ListValueCreator.createValue(ListValueCreator.java:43) at org.jboss.osgi.metadata.internal.ListValueCreator.createValue(ListValueCreator.java:31) at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.get(AbstractOSGiMetaData.java:266) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.get(AbstractOSGiMetaData.java:257) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.getExportPackages(AbstractOSGiMetaData.java:198) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] at org.jboss.osgi.resolver.spi.AbstractResourceBuilder.loadFrom(AbstractResourceBuilder.java:236) [jbosgi-resolver-api-4.0.4.Final-SNAPSHOT.jar:4.0.4.Final-SNAPSHOT] ... 11 more {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 22:28:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 22:28:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-777) Filter-out zero-length path from module-exported paths In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-777 started by Arcadiy Ivanov. --------------------------------------------- > Filter-out zero-length path from module-exported paths > ------------------------------------------------------ > > Key: JBOSGI-777 > URL: https://issues.jboss.org/browse/JBOSGI-777 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > {noformat} > 22:15:15,816 ERROR [org.jboss.osgi.repository] (MSC service thread 1-8) JBOSGI020401: Cannot create resource for: javax.jws.api: org.jboss.osgi.resolver.ResourceBuilderException: JBOSGI010908: Cannot initialize resource from: [javax.jws.api:0.0.0] > at org.jboss.osgi.resolver.spi.AbstractResourceBuilder.loadFrom(AbstractResourceBuilder.java:316) [jbosgi-resolver-api-4.0.4.Final-SNAPSHOT.jar:4.0.4.Final-SNAPSHOT] > at org.jboss.osgi.repository.spi.AbstractRepository.getTargetResource(AbstractRepository.java:249) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] > at org.jboss.osgi.repository.spi.ModuleIdentityRepository.getTargetResource(ModuleIdentityRepository.java:120) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] > at org.jboss.osgi.repository.spi.ModuleIdentityRepository.findProviders(ModuleIdentityRepository.java:108) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] > at org.jboss.as.osgi.service.ModuleIdentityRepositoryIntegration.findProviders(ModuleIdentityRepositoryIntegration.java:108) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] > at org.jboss.as.osgi.service.BootstrapBundlesIntegration.installInitialModuleCapability(BootstrapBundlesIntegration.java:181) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] > at org.jboss.as.osgi.service.BootstrapBundlesIntegration.start(BootstrapBundlesIntegration.java:135) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] > Caused by: java.lang.IllegalArgumentException: No paths for clause: > at org.jboss.osgi.metadata.internal.ManifestParser.parse(ManifestParser.java:102) > at org.jboss.osgi.metadata.internal.ManifestParser.parsePackages(ManifestParser.java:47) > at org.jboss.osgi.metadata.internal.PackageAttributeListValueCreator.useString(PackageAttributeListValueCreator.java:35) > at org.jboss.osgi.metadata.internal.PackageAttributeListValueCreator.useString(PackageAttributeListValueCreator.java:32) > at org.jboss.osgi.metadata.internal.AbstractValueCreator.createValue(AbstractValueCreator.java:45) > at org.jboss.osgi.metadata.internal.ListValueCreator.createValue(ListValueCreator.java:43) > at org.jboss.osgi.metadata.internal.ListValueCreator.createValue(ListValueCreator.java:31) > at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.get(AbstractOSGiMetaData.java:266) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] > at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.get(AbstractOSGiMetaData.java:257) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] > at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.getExportPackages(AbstractOSGiMetaData.java:198) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] > at org.jboss.osgi.resolver.spi.AbstractResourceBuilder.loadFrom(AbstractResourceBuilder.java:236) [jbosgi-resolver-api-4.0.4.Final-SNAPSHOT.jar:4.0.4.Final-SNAPSHOT] > ... 11 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sat Apr 18 22:36:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sat, 18 Apr 2015 22:36:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-777) Filter-out zero-length path from module-exported paths In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-777: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-repository/pull/14, https://github.com/jbosgi/jbosgi-resolver/pull/8 (was: https://github.com/jbosgi/jbosgi-repository/pull/14) > Filter-out zero-length path from module-exported paths > ------------------------------------------------------ > > Key: JBOSGI-777 > URL: https://issues.jboss.org/browse/JBOSGI-777 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > {noformat} > 22:15:15,816 ERROR [org.jboss.osgi.repository] (MSC service thread 1-8) JBOSGI020401: Cannot create resource for: javax.jws.api: org.jboss.osgi.resolver.ResourceBuilderException: JBOSGI010908: Cannot initialize resource from: [javax.jws.api:0.0.0] > at org.jboss.osgi.resolver.spi.AbstractResourceBuilder.loadFrom(AbstractResourceBuilder.java:316) [jbosgi-resolver-api-4.0.4.Final-SNAPSHOT.jar:4.0.4.Final-SNAPSHOT] > at org.jboss.osgi.repository.spi.AbstractRepository.getTargetResource(AbstractRepository.java:249) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] > at org.jboss.osgi.repository.spi.ModuleIdentityRepository.getTargetResource(ModuleIdentityRepository.java:120) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] > at org.jboss.osgi.repository.spi.ModuleIdentityRepository.findProviders(ModuleIdentityRepository.java:108) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] > at org.jboss.as.osgi.service.ModuleIdentityRepositoryIntegration.findProviders(ModuleIdentityRepositoryIntegration.java:108) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] > at org.jboss.as.osgi.service.BootstrapBundlesIntegration.installInitialModuleCapability(BootstrapBundlesIntegration.java:181) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] > at org.jboss.as.osgi.service.BootstrapBundlesIntegration.start(BootstrapBundlesIntegration.java:135) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] > Caused by: java.lang.IllegalArgumentException: No paths for clause: > at org.jboss.osgi.metadata.internal.ManifestParser.parse(ManifestParser.java:102) > at org.jboss.osgi.metadata.internal.ManifestParser.parsePackages(ManifestParser.java:47) > at org.jboss.osgi.metadata.internal.PackageAttributeListValueCreator.useString(PackageAttributeListValueCreator.java:35) > at org.jboss.osgi.metadata.internal.PackageAttributeListValueCreator.useString(PackageAttributeListValueCreator.java:32) > at org.jboss.osgi.metadata.internal.AbstractValueCreator.createValue(AbstractValueCreator.java:45) > at org.jboss.osgi.metadata.internal.ListValueCreator.createValue(ListValueCreator.java:43) > at org.jboss.osgi.metadata.internal.ListValueCreator.createValue(ListValueCreator.java:31) > at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.get(AbstractOSGiMetaData.java:266) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] > at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.get(AbstractOSGiMetaData.java:257) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] > at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.getExportPackages(AbstractOSGiMetaData.java:198) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] > at org.jboss.osgi.resolver.spi.AbstractResourceBuilder.loadFrom(AbstractResourceBuilder.java:236) [jbosgi-resolver-api-4.0.4.Final-SNAPSHOT.jar:4.0.4.Final-SNAPSHOT] > ... 11 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 04:25:19 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 04:25:19 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-774) Cleanup solution for JBOSGI-567 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-774. ----------------------------------- Resolution: Done > Cleanup solution for JBOSGI-567 > ------------------------------- > > Key: JBOSGI-774 > URL: https://issues.jboss.org/browse/JBOSGI-774 > Project: JBoss OSGi > Issue Type: Task > Components: framework, wildfly > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > JBOSGI-567 solution introduced AbstractBundleRevisionAdaptor detecting if OSGiMetaData was present in the attachment and creating one if it wasn't. > This solution, however usurps the responsibility from ModuleIdentityRepositoryIntegration and copies code from ModuleIdentityRepository. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 04:26:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 04:26:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-777) Filter-out zero-length path from module-exported paths In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-777. ----------------------------------- Resolution: Done > Filter-out zero-length path from module-exported paths > ------------------------------------------------------ > > Key: JBOSGI-777 > URL: https://issues.jboss.org/browse/JBOSGI-777 > Project: JBoss OSGi > Issue Type: Bug > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > {noformat} > 22:15:15,816 ERROR [org.jboss.osgi.repository] (MSC service thread 1-8) JBOSGI020401: Cannot create resource for: javax.jws.api: org.jboss.osgi.resolver.ResourceBuilderException: JBOSGI010908: Cannot initialize resource from: [javax.jws.api:0.0.0] > at org.jboss.osgi.resolver.spi.AbstractResourceBuilder.loadFrom(AbstractResourceBuilder.java:316) [jbosgi-resolver-api-4.0.4.Final-SNAPSHOT.jar:4.0.4.Final-SNAPSHOT] > at org.jboss.osgi.repository.spi.AbstractRepository.getTargetResource(AbstractRepository.java:249) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] > at org.jboss.osgi.repository.spi.ModuleIdentityRepository.getTargetResource(ModuleIdentityRepository.java:120) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] > at org.jboss.osgi.repository.spi.ModuleIdentityRepository.findProviders(ModuleIdentityRepository.java:108) [jbosgi-repository-core-4.0.2.Final-SNAPSHOT.jar:4.0.2.Final-SNAPSHOT] > at org.jboss.as.osgi.service.ModuleIdentityRepositoryIntegration.findProviders(ModuleIdentityRepositoryIntegration.java:108) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] > at org.jboss.as.osgi.service.BootstrapBundlesIntegration.installInitialModuleCapability(BootstrapBundlesIntegration.java:181) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] > at org.jboss.as.osgi.service.BootstrapBundlesIntegration.start(BootstrapBundlesIntegration.java:135) [jbosgi-wildfly-service-2.3.1.Final-SNAPSHOT.jar:2.3.1.Final-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45] > Caused by: java.lang.IllegalArgumentException: No paths for clause: > at org.jboss.osgi.metadata.internal.ManifestParser.parse(ManifestParser.java:102) > at org.jboss.osgi.metadata.internal.ManifestParser.parsePackages(ManifestParser.java:47) > at org.jboss.osgi.metadata.internal.PackageAttributeListValueCreator.useString(PackageAttributeListValueCreator.java:35) > at org.jboss.osgi.metadata.internal.PackageAttributeListValueCreator.useString(PackageAttributeListValueCreator.java:32) > at org.jboss.osgi.metadata.internal.AbstractValueCreator.createValue(AbstractValueCreator.java:45) > at org.jboss.osgi.metadata.internal.ListValueCreator.createValue(ListValueCreator.java:43) > at org.jboss.osgi.metadata.internal.ListValueCreator.createValue(ListValueCreator.java:31) > at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.get(AbstractOSGiMetaData.java:266) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] > at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.get(AbstractOSGiMetaData.java:257) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] > at org.jboss.osgi.metadata.spi.AbstractOSGiMetaData.getExportPackages(AbstractOSGiMetaData.java:198) [jbosgi-metadata-4.0.0.Final.jar:4.0.0.Final] > at org.jboss.osgi.resolver.spi.AbstractResourceBuilder.loadFrom(AbstractResourceBuilder.java:236) [jbosgi-resolver-api-4.0.4.Final-SNAPSHOT.jar:4.0.4.Final-SNAPSHOT] > ... 11 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 04:26:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 04:26:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-776) Improve FallbackLoader logging to aid DynamicImport-Package troubleshooting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-776. ----------------------------------- Resolution: Done > Improve FallbackLoader logging to aid DynamicImport-Package troubleshooting > --------------------------------------------------------------------------- > > Key: JBOSGI-776 > URL: https://issues.jboss.org/browse/JBOSGI-776 > Project: JBoss OSGi > Issue Type: Enhancement > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Priority: Minor > Fix For: JBossOSGI 2.3.1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 04:37:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 04:37:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-774) Cleanup solution for JBOSGI-567 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov reopened JBOSGI-774: ----------------------------------- > Cleanup solution for JBOSGI-567 > ------------------------------- > > Key: JBOSGI-774 > URL: https://issues.jboss.org/browse/JBOSGI-774 > Project: JBoss OSGi > Issue Type: Task > Components: framework, wildfly > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > JBOSGI-567 solution introduced AbstractBundleRevisionAdaptor detecting if OSGiMetaData was present in the attachment and creating one if it wasn't. > This solution, however usurps the responsibility from ModuleIdentityRepositoryIntegration and copies code from ModuleIdentityRepository. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 04:37:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 04:37:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-774) Cleanup solution for JBOSGI-567 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov resolved JBOSGI-774. ----------------------------------- Resolution: Done > Cleanup solution for JBOSGI-567 > ------------------------------- > > Key: JBOSGI-774 > URL: https://issues.jboss.org/browse/JBOSGI-774 > Project: JBoss OSGi > Issue Type: Task > Components: framework, wildfly > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > JBOSGI-567 solution introduced AbstractBundleRevisionAdaptor detecting if OSGiMetaData was present in the attachment and creating one if it wasn't. > This solution, however usurps the responsibility from ModuleIdentityRepositoryIntegration and copies code from ModuleIdentityRepository. -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 04:39:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 04:39:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-778) Centralize module OsgiMetadata logic In-Reply-To: References: Message-ID: Arcadiy Ivanov created JBOSGI-778: ------------------------------------- Summary: Centralize module OsgiMetadata logic Key: JBOSGI-778 URL: https://issues.jboss.org/browse/JBOSGI-778 Project: JBoss OSGi Issue Type: Enhancement Components: framework, resolver, wildfly Reporter: Arcadiy Ivanov Fix For: JBossOSGI 2.3.1 * Module OSGiMetaData processing is all over the place and needs to be centralized * OSGiMetaData attachment to XBundleRevision needs to be reviewed -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 04:53:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 04:53:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-778) Centralize module OsgiMetaData reading logic In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-778: ---------------------------------- Summary: Centralize module OsgiMetaData reading logic (was: Centralize module OsgiMetadata logic) > Centralize module OsgiMetaData reading logic > -------------------------------------------- > > Key: JBOSGI-778 > URL: https://issues.jboss.org/browse/JBOSGI-778 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver, wildfly > Reporter: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > * Module OSGiMetaData processing is all over the place and needs to be centralized > * OSGiMetaData attachment to XBundleRevision needs to be reviewed -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 04:55:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 04:55:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-778) Centralize module OsgiMetaData reading logic In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov reassigned JBOSGI-778: ------------------------------------- Assignee: Arcadiy Ivanov > Centralize module OsgiMetaData reading logic > -------------------------------------------- > > Key: JBOSGI-778 > URL: https://issues.jboss.org/browse/JBOSGI-778 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver, wildfly > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > * Module OSGiMetaData processing is all over the place and needs to be centralized > * OSGiMetaData attachment to XBundleRevision needs to be reviewed -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 04:55:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 04:55:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-778) Centralize module OsgiMetaData reading logic In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBOSGI-778 started by Arcadiy Ivanov. --------------------------------------------- > Centralize module OsgiMetaData reading logic > -------------------------------------------- > > Key: JBOSGI-778 > URL: https://issues.jboss.org/browse/JBOSGI-778 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver, wildfly > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > * Module OSGiMetaData processing is all over the place and needs to be centralized > * OSGiMetaData attachment to XBundleRevision needs to be reviewed -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 05:45:20 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 05:45:20 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-778) Centralize module OsgiMetaData reading logic In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-778: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-resolver/pull/9 > Centralize module OsgiMetaData reading logic > -------------------------------------------- > > Key: JBOSGI-778 > URL: https://issues.jboss.org/browse/JBOSGI-778 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver, wildfly > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > * Module OSGiMetaData processing is all over the place and needs to be centralized > * OSGiMetaData attachment to XBundleRevision needs to be reviewed -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 05:51:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 05:51:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-778) Centralize module OsgiMetaData reading logic In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-778: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-resolver/pull/9, https://github.com/jbosgi/jbosgi-framework/pull/24 (was: https://github.com/jbosgi/jbosgi-resolver/pull/9) > Centralize module OsgiMetaData reading logic > -------------------------------------------- > > Key: JBOSGI-778 > URL: https://issues.jboss.org/browse/JBOSGI-778 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver, wildfly > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > * Module OSGiMetaData processing is all over the place and needs to be centralized > * OSGiMetaData attachment to XBundleRevision needs to be reviewed -- This message was sent by Atlassian JIRA (v6.3.11#6341) From issues at jboss.org Sun Apr 19 05:52:18 2015 From: issues at jboss.org (Arcadiy Ivanov (JIRA)) Date: Sun, 19 Apr 2015 05:52:18 -0400 (EDT) Subject: [jboss-osgi-issues] [JBoss JIRA] (JBOSGI-778) Centralize module OsgiMetaData reading logic In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBOSGI-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arcadiy Ivanov updated JBOSGI-778: ---------------------------------- Git Pull Request: https://github.com/jbosgi/jbosgi-resolver/pull/9, https://github.com/jbosgi/jbosgi-framework/pull/24, https://github.com/jbosgi/jbosgi-repository/pull/15, https://github.com/jbosgi/jbosgi/pull/11 (was: https://github.com/jbosgi/jbosgi-resolver/pull/9, https://github.com/jbosgi/jbosgi-framework/pull/24) > Centralize module OsgiMetaData reading logic > -------------------------------------------- > > Key: JBOSGI-778 > URL: https://issues.jboss.org/browse/JBOSGI-778 > Project: JBoss OSGi > Issue Type: Enhancement > Components: framework, resolver, wildfly > Reporter: Arcadiy Ivanov > Assignee: Arcadiy Ivanov > Fix For: JBossOSGI 2.3.1 > > > * Module OSGiMetaData processing is all over the place and needs to be centralized > * OSGiMetaData attachment to XBundleRevision needs to be reviewed -- This message was sent by Atlassian JIRA (v6.3.11#6341)