<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Folks, <br>
<br>
now that we deploy through the GWT console it's a real usability
issue that we don't have a way to determine whether an OSGi bundle
should be automatically started when deployed through the
management API.<br>
<br>
Here the related issues<br>
<br>
[<a href="https://issues.jboss.org/browse/AS7-3693">AS7-3693</a>]
Console does not support install/start semantic for bundles<br>
[<a href="https://issues.jboss.org/browse/AS7-3694">AS7-3694</a>]
Allow management client to associate metadata with DeploymentUnit<br>
[<a href="https://issues.jboss.org/browse/AS7-2777">AS7-2777</a>]
Add notion of start/stop for deployments<br>
[<a href="https://issues.jboss.org/browse/AS7-378">AS7-378</a>]
Support notion of deployment set<br>
<br>
I could have a go at this set of problems because it directly
relates to OSGi bundle deployment. Please note, that JSR-88 also
has the notion of start/stop for JavaEE deployments. You can for
example stop a webapp to temporarily make the http endpoint
unavailable. Currently this is faked/hacked in the jsr88 impl.<br>
<br>
I would post proposals for the individual subproblems.<br>
<br>
#1 client metadata associated with the DU<br>
#2 start/stop semantic for arbitrary deployments<br>
#3 notion of deployment set and DUPs that can operate on the set
rather than individual DU only<br>
<br>
cheers<br>
-thomas <br>
<br>
</tt>
<pre class="moz-signature" cols="72">--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
</pre>
</body>
</html>