April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6952) OSGi requirements for AS9

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6952?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6952: -------------------------------- Description: [jboss-as7-dev] [Resolving AS8/OSGi deployment disconnects|http://lists.jboss.org/pipermail/jboss-as7-dev/2013-April/007...] > OSGi requirements for AS9 > ------------------------- > > Key: AS7-6952 > URL: https://issues.jboss.org/browse/AS7-6952 > Project: Application Server 7 > 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6953) Show the communication with the server (CLI commands and the responses)

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-6953?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-6953: ------------------------------ Description: It would be nice if the console allowed to show the CLI comands being sent to the server, and the outcome. Ideally, it could show it in some toolbox at the bottom, but logging it to browser's JavaScript console is good as well. Note that catching HTTP requests doesn't help since the content is encoded. was: It would be nice if the console allowed to show the CLI comands being sent to the server, and the outcome. Ideally, it could show it in some toolbox at the bottom, but logging it to browser's JavaScript console is good as well. > Show the communication with the server (CLI commands and the responses) > ----------------------------------------------------------------------- > > Key: AS7-6953 > URL: https://issues.jboss.org/browse/AS7-6953 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Affects Versions: 8.0.0.Alpha1 > Reporter: Ondrej Zizka > Assignee: Heiko Braun > Labels: cli, debugging, usability > > It would be nice if the console allowed to show the CLI comands being sent to the server, and the outcome. > Ideally, it could show it in some toolbox at the bottom, but logging it to browser's JavaScript console is good as well. > Note that catching HTTP requests doesn't help since the content is encoded. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-2777) Complete support for Bundle start/stop

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-2777?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-2777: -------------------------------- Component/s: (was: JSR88) > Complete support for Bundle start/stop > --------------------------------------- > > Key: AS7-2777 > URL: https://issues.jboss.org/browse/AS7-2777 > Project: Application Server 7 > Issue Type: Sub-task > Components: OSGi, Server > Reporter: Thomas Diesler > Labels: roadmap > > The JSR88 deployemt API allows control over the full deployment lifecycle > * deploy > * start > * stop > * undeploy > OSGi deployments (i.e. bundles) also have the notion of start/stop > This should be reflected in the management API for deployments. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6953) Show the communication with the server (CLI commands and the responses)

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-6953: --------------------------------- Summary: Show the communication with the server (CLI commands and the responses) Key: AS7-6953 URL: https://issues.jboss.org/browse/AS7-6953 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 8.0.0.Alpha1 Reporter: Ondrej Zizka Assignee: Heiko Braun It would be nice if the console allowed to show the CLI comands being sent to the server, and the outcome. Ideally, it could show it in some toolbox at the bottom, but logging it to browser's JavaScript console is good as well. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6801) Complete support for Bundle uninstall

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6801?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6801: -------------------------------- Summary: Complete support for Bundle uninstall (was: Add proper support for Bundle uninstall) > Complete support for Bundle uninstall > ------------------------------------- > > Key: AS7-6801 > URL: https://issues.jboss.org/browse/AS7-6801 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi, Server > Reporter: Thomas Diesler > > In OSGi > Stops the bundle, destroys the BundleContext, prevents further starts and marks the bundle as "removal pending". Determine the usage count of the bundle classloader (i.e. number of wires to this bundle). Only if there is no active wire left the bundle can get removed from the Framework and the bundle class loader can get garbage collected. Until then, wires to the bundle stay active and resource/class loading continues to work as before. A bundle gets removed from the Framework automatically when the last dependency gets is marked as removal pending or if there is an explicit call to refresh the the wirings of the dependency closure (i.e. removal pending bundles are thrown out new wirings get established) > In AS today > Bundle uninstall causes an 'undeploy' management operation, which rolls back the deployment through all DUPs and removes it from the Framework. AS has no notion of "removal pending" or "in use" module. Due to the way deployment phase services have dependencies on phase services from other deployments, we get an undesired side effect of bundle deployments stopping/breaking if they have a dependency on an undeployed bundle. As mentioned above, dependecies should be limited to services but not on bundle lifecycle let alone break class loader dependencies. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6801) Complete support for Bundle uninstall

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6801?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-6801: -------------------------------- Parent: AS7-6952 Issue Type: Sub-task (was: Feature Request) > Complete support for Bundle uninstall > ------------------------------------- > > Key: AS7-6801 > URL: https://issues.jboss.org/browse/AS7-6801 > Project: Application Server 7 > Issue Type: Sub-task > Components: OSGi, Server > Reporter: Thomas Diesler > > In OSGi > Stops the bundle, destroys the BundleContext, prevents further starts and marks the bundle as "removal pending". Determine the usage count of the bundle classloader (i.e. number of wires to this bundle). Only if there is no active wire left the bundle can get removed from the Framework and the bundle class loader can get garbage collected. Until then, wires to the bundle stay active and resource/class loading continues to work as before. A bundle gets removed from the Framework automatically when the last dependency gets is marked as removal pending or if there is an explicit call to refresh the the wirings of the dependency closure (i.e. removal pending bundles are thrown out new wirings get established) > In AS today > Bundle uninstall causes an 'undeploy' management operation, which rolls back the deployment through all DUPs and removes it from the Framework. AS has no notion of "removal pending" or "in use" module. Due to the way deployment phase services have dependencies on phase services from other deployments, we get an undesired side effect of bundle deployments stopping/breaking if they have a dependency on an undeployed bundle. As mentioned above, dependecies should be limited to services but not on bundle lifecycle let alone break class loader dependencies. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-3694) Allow management client to associate metadata with DeploymentUnit

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-3694?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-3694: -------------------------------- Parent: AS7-6952 Issue Type: Sub-task (was: Feature Request) > Allow management client to associate metadata with DeploymentUnit > ----------------------------------------------------------------- > > Key: AS7-3694 > URL: https://issues.jboss.org/browse/AS7-3694 > Project: Application Server 7 > Issue Type: Sub-task > Components: OSGi, Server > Reporter: Thomas Diesler > Assignee: Brian Stansberry > > Currently there is no way to pass some metadata through the deployment API such that they could show up with the DU. > As a client I'd like to say autostart=false and in my DUP I'd like to pick that up and not start a deployment (i.e. a bundle) automatically > Generally it should be possible for the client to set some properties for the deployment in a generic way such that they get associated with the DeploymentUnit > For an OSGi deployment it would be necessary to be able to define that start behaviour and the start level. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-2777) Complete support for Bundle start/stop

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-2777?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-2777: -------------------------------- Parent: AS7-6952 Issue Type: Sub-task (was: Feature Request) > Complete support for Bundle start/stop > --------------------------------------- > > Key: AS7-2777 > URL: https://issues.jboss.org/browse/AS7-2777 > Project: Application Server 7 > Issue Type: Sub-task > Components: JSR88, OSGi, Server > Reporter: Thomas Diesler > Labels: roadmap > > The JSR88 deployemt API allows control over the full deployment lifecycle > * deploy > * start > * stop > * undeploy > OSGi deployments (i.e. bundles) also have the notion of start/stop > This should be reflected in the management API for deployments. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-378) Support notion of deployment set

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-378?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler updated AS7-378: ------------------------------- Parent: AS7-6952 Issue Type: Sub-task (was: Feature Request) > Support notion of deployment set > -------------------------------- > > Key: AS7-378 > URL: https://issues.jboss.org/browse/AS7-378 > Project: Application Server 7 > Issue Type: Sub-task > Components: OSGi, Server > Reporter: Thomas Diesler > > In one deploy cycle, bundles must first get installed and then started. > It generally needs to be discussed how multiple phase deployments should be handled. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-4343) Failure detection/handling in deployment operation start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-4343?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-4343: -------------------------------- Parent: (was: AS7-2777) Issue Type: Feature Request (was: Sub-task) > Failure detection/handling in deployment operation start > -------------------------------------------------------- > > Key: AS7-4343 > URL: https://issues.jboss.org/browse/AS7-4343 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi, Server > Reporter: Thomas Diesler > Priority: Minor > -- 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

11 years, 9 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 April 2013