June 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-556) Complete support for Bundle uninstall

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-556?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved WFLY-556. --------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Complete support for Bundle uninstall > ------------------------------------- > > Key: WFLY-556 > URL: https://issues.jboss.org/browse/WFLY-556 > Project: WildFly > Issue Type: Sub-task > Components: OSGi, Server > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 9.0.0.CR1 > > > Bundle uninstall only removes the BundleRevision from the runtime if it is no longer in use. The classloader associated with an uninstalled bundle that is still in use remains active. > Approach #1 - "in use" semantic specific to Bundle deployments > An undeploy management operation undeploys the bundle revision but holds in the MODULE phase when the revision is still in use > This is similar to deferred MODULE phase for deploy operation > in use is not respected for non-osgi deployments and hence breaks bundle deployments that depend on them > Approach #2 - "in use" semantic applies to all deployment types > Undeploy will only destroy the Module service if the Module is not in use by another deployment > When Module usage drops to zero, undeploy continues and removes the deployment from management > This approach would map cleanly - there is no cascading destroy effect. i.e. when you undeploy a jar that a webapp depends on > Services provided by the undeployed deployment would always go down, only classloader destruction is deferred -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-540) OSGi requirements for AS9

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-540?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved WFLY-540. --------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > OSGi requirements for AS9 > ------------------------- > > Key: WFLY-540 > URL: https://issues.jboss.org/browse/WFLY-540 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 9.0.0.CR1 > > > [jboss-as7-dev] [Resolving AS8/OSGi deployment disconnects|http://lists.jboss.org/pipermail/jboss-as7-dev/2013-April/007...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1153) Initial OSGi / CDI Integration

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1153?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1153. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Initial OSGi / CDI Integration > ------------------------------- > > Key: WFLY-1153 > URL: https://issues.jboss.org/browse/WFLY-1153 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld, OSGi > Reporter: Thomas Diesler > Labels: roadmap > > Provide an example test that shows CDI integration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1133) Integration of EventAdmin with AS7 components

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1133?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1133. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Integration of EventAdmin with AS7 components > --------------------------------------------- > > Key: WFLY-1133 > URL: https://issues.jboss.org/browse/WFLY-1133 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > > Non-OSGi components should be able to publish/receive events through EventAdmin > and vice versa of course -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1104) Provide access to OSGiMetaData for server, web, etc

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1104?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1104. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Provide access to OSGiMetaData for server, web, etc > --------------------------------------------------- > > Key: WFLY-1104 > URL: https://issues.jboss.org/browse/WFLY-1104 > Project: WildFly > Issue Type: Feature Request > Components: OSGi, Server > Reporter: Thomas Diesler > > Currently we have a policy that server does not have a dependency on OSGi API and as a result to OSGiMetaData. > In several places we do a check like this > {code} > if (depUnit.hasAttachment(Attachments.OSGI_MANIFEST)) { > ... > } > {code} > This however implies that the Manifest is the only possible source of valid OSGi metadata. The OSGi webapp spec allows for metadata to be specified as part of a "webbundle://" URI (see AS7-6006) > To make this work, the integration code currently generates a Manifest and later OSGiMetaData from it. The above code still works even if the deployment content does not have a Manifest. > I propose to move the OSGiMetaData one level down so that > {code} > if (depUnit.hasAttachment(Attachments.OSGI_METADATA)) { > ... > } > {code} > is the deciding criteria. As a additional benefit web would no longer need to produce/consume the raw Manifest headers and OSGi metadata would be treated like all other metadata structures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-116) Cannot replace jar that bundle depends on

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-116?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved WFLY-116. --------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Cannot replace jar that bundle depends on > ----------------------------------------- > > Key: WFLY-116 > URL: https://issues.jboss.org/browse/WFLY-116 > Project: WildFly > Issue Type: Bug > Components: OSGi > Reporter: Thomas Diesler > > With an OSGi webapp that depends on a jar the jar cannot be replaced. > See BundleReplaceTestCase.testDependentJarReplace() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1246) Provide management view for the OSGi Repository

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1246?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1246. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Provide management view for the OSGi Repository > ----------------------------------------------- > > Key: WFLY-1246 > URL: https://issues.jboss.org/browse/WFLY-1246 > Project: WildFly > Issue Type: Task > Components: OSGi > Reporter: Thomas Diesler > Labels: roadmap > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1243) Complete support for HttpService on JBossWeb

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1243?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1243. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Complete support for HttpService on JBossWeb > -------------------------------------------- > > Key: WFLY-1243 > URL: https://issues.jboss.org/browse/WFLY-1243 > Project: WildFly > Issue Type: Task > Components: OSGi > Reporter: Thomas Diesler > Labels: roadmap > > #1 Add support for MimeType, Content-Lenght, etc > #2 Delegate authentication/authorisation to HttpContext > #3 Add support for "/" root context > #4 Make HttpService an optional capability > #5 Make virtual host/port configurable > This issue is complete when the TCK passes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1096) Complete support for OSGi Blueprint

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1096?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1096. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Complete support for OSGi Blueprint > ----------------------------------- > > Key: WFLY-1096 > URL: https://issues.jboss.org/browse/WFLY-1096 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > Labels: roadmap > > R5 TCK compliance for Blueprint -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1225) Add support for Framework restart

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1225?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1225. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Add support for Framework restart > --------------------------------- > > Key: WFLY-1225 > URL: https://issues.jboss.org/browse/WFLY-1225 > Project: WildFly > Issue Type: Task > Components: OSGi > Reporter: Thomas Diesler > > It should be possible to modify the framework configuration and restart the framework in AS7. This is especially important for a Framework instance running in OpenShift. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2013