Hi all,

I have some questions about the deployment management object. They are:

1. The deployment sub-tree provides a full management of the deployment packages and restricted one for the bundles. We can’t execute operations like start, stop… over them. Are there any discussions about or any comments? A simple solution can be an additional Operations branch in the Deployment/Inventory/Deployed/<node_id>/Ext/Bundles/<bundle_id> node. I can add more details, if you think that the idea is good.

2. What is the value of the Deployment/Inventory/Deployed/<node_id>/ID node for the deployment artifacts which come from the Framework API (or Deployment Admin API)? I think that the usage of the node value can be extended a little. Some ideas are: 2.1 If the value of the ID node is default (empty string) in the Download or Delivered sub-tree and install operation is executed then the ID in Deployment sub-tree is generated from the management object. 2.2 If the value of the ID node in Download or Delivered sub-tree is already in the Deployment sub-tree then an update can be done. 2.3 The value of Deployment/Inventory/Deployed/<node_id>/ID can be specified in more details. For example, resource dependent identifier will allow mass operations like mass update, remove... A good candidate for the deployment packages is the symbolic name and for the bundles is symbolic name + ‘:’ + version. The character ‘:’ can’t be set as deployment package symbolic name and resolves the conflict when the deployment package name is same as bundle name concatenated with its version.

Any comments?

Thanks in advance, Evgeni!

--
-----------------------------------------------------------------------------------
Evgeni Grigorov . Software Engineer/Development Tools
ProSyst Software GmbH
Tel. +359 2 953 05 88 . Fax +359 2 953 26 17
Mobile +359 878 17 41 51
http://www.prosyst.com . e.grigo...@prosyst.com
-----------------------------------------------------------------------------------
stay in touch with your product.
-----------------------------------------------------------------------------------


_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to