June 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-557) Complete support for Bundle update

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-557?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved WFLY-557. --------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Complete support for Bundle update > ---------------------------------- > > Key: WFLY-557 > URL: https://issues.jboss.org/browse/WFLY-557 > Project: WildFly > Issue Type: Sub-task > Components: OSGi, Server > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 9.0.0.CR1 > > > A Bundle can have multiple revisions. A call to Bundle.update(…) creates a new revision. There is only ever one current revision (the latest update) associated with a Bundle. Stale revisions continue to exist in the runtime until an explicit refresh of the transitive dependency graph. > Approach #1 - bundle revisions are represented as individual deployments > Each bundle update deploys the revision as a new deployment > The association of revisions to bundle happens in the OSGi layer only > Management sees disconnected deployments with no notion of stale/current or belonging together > Approach #2 - deployment API supports the notion of multiple revisions > deployments, their revisions and respective mapping would be modelled more closely on OSGi requirements > some deployment types might not support revisions -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1187) Allow OSGi configuration to get modified before subsystem start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1187?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1187. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Allow OSGi configuration to get modified before subsystem start > --------------------------------------------------------------- > > Key: WFLY-1187 > URL: https://issues.jboss.org/browse/WFLY-1187 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > > It should be possible to > * start the server > * modify framework properties > * start the osgi subsystem with the updated properties -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1253) HttpService MimeType, ContentLength, etc

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1253?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1253. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > HttpService MimeType, ContentLength, etc > ---------------------------------------- > > Key: WFLY-1253 > URL: https://issues.jboss.org/browse/WFLY-1253 > Project: WildFly > Issue Type: Sub-task > Components: OSGi > Reporter: Thomas Diesler > -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1076) Optimize OSGi subsystem bootstrap

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1076?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1076. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Optimize OSGi subsystem bootstrap > --------------------------------- > > Key: WFLY-1076 > URL: https://issues.jboss.org/browse/WFLY-1076 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > > The OSGi subsystem in AS7 is alrady activated lazily. However, in many cases users only want to deploy a simple artefact that "happens to be" an OSGi bundle (i.e. a JDBC driver) and do not want to deploy a large set of interconnected bundles that make up a complex modular enterprise application. For those cases the OSGi subsystem should bootstrap in a jiffy and we should not see a performance impact that is worth talking about. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1075) Enforce OSGi wiring symmetry across nodes

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1075?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1075. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Enforce OSGi wiring symmetry across nodes > ----------------------------------------- > > Key: WFLY-1075 > URL: https://issues.jboss.org/browse/WFLY-1075 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, OSGi > Reporter: Thomas Diesler > > Using a distributed cache in a multinode environment would require a mapping for the classloader. With symetric wiring only the top level cl needs to be mapped. Unsymentric wiring may lead to a number of unforeseeable issues. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-163) Some javax.* bundles show version 0.0.0 in AS7

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-163?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved WFLY-163. --------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Some javax.* bundles show version 0.0.0 in AS7 > ---------------------------------------------- > > Key: WFLY-163 > URL: https://issues.jboss.org/browse/WFLY-163 > Project: WildFly > Issue Type: Bug > Components: OSGi > Reporter: Thomas Diesler > Assignee: Cheng Fang > Fix For: 8.0.0.Alpha3 > > > Some javax bundles that we configure by default do not show valid bundle version info > javax.jws.api:0.0.0 > javax.ws.rs.api:0.0.0 > The javax.persistence.api has its metadata defined in jbosgi-xservice.properties like this > {code} > Bundle-SymbolicName: hibernate-jpa-2.0-api > Bundle-Version: 1.0.1.Final > Export-Package: javax.persistence.spi;version="2.0.0",javax.persistence.criteria;version="2.0.0",javax.persistence;version="2.0.0",javax.persistence.metamodel;version="2.0.0" > {code} > This should be replaced by metadata coming from the artefacts manifest. > Generally, all javax api artefacts should have valid OSGi metadata -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1108) Complete runtime support for Karaf based products

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1108?page=com.atlassian.jira.plugin.... ] Thomas Diesler resolved WFLY-1108. ---------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Complete runtime support for Karaf based products > ------------------------------------------------- > > Key: WFLY-1108 > URL: https://issues.jboss.org/browse/WFLY-1108 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > Labels: roadmap > > Provide complete support for Karaf based products -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-879) Attribute read for uninstalled bundle breaks console

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-879?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved WFLY-879. --------------------------------- Resolution: Won't Fix Won't Fix - OSGi is going to get removed > Attribute read for uninstalled bundle breaks console > ---------------------------------------------------- > > Key: WFLY-879 > URL: https://issues.jboss.org/browse/WFLY-879 > Project: WildFly > Issue Type: Bug > Components: OSGi > Reporter: Thomas Diesler > Labels: Console > Attachments: unread_bundle_stacktrace.txt, unread_bundle_stacktrace_cli.txt > > -- 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

10 years, 10 months

1
0
0 / 0

[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

10 years, 10 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2013