Printable View
In the DM server developer guide, it says the deployment steps is copying all bundles into usr directory, and restart dm server, and then put the plan file to pickup directory or deploy the plan file from dm admin web.
Does it mean we have restart dm server once I want upgrade a bundle belonging to the plan? It is too bad.
The usr directory is actively monitored for changes while dm Server is running, so it is not necessary to restart dm Server to pick up those changes.
However, to update a plan to use an updated bundle from the usr directory, it is necessary to undeploy and redeploy the plan (since dm Server does not currently support whole plan refresh).
What actually happens, then bundle file change detected? Which events are fired or occured? This is not quite clear topic and not covered in documentation too.Quote:
Originally Posted by Glyn Normington
Did you mean "dm Server does not currently support PARTIAL plan refresh"?Quote:
Originally Posted by Glyn Normington
The repository index for the bundle is updated to reflect the updated bundle. This is a "passive" operation with no notifications or "external" events. The file system listener events are provided only for the repository to use internally and are not available as external events.Quote:
Originally Posted by Kirill Uvaev
The updated bundle is then available for referencing out of the repository.
If the updated repository is being used as a remote repository, then the change of the secure hash of the bundle will result in a cache miss when the bundle is referenced remotely.
Yes, I did mean that. Thanks.Quote:
Did you mean "dm Server does not currently support PARTIAL plan refresh"?
Are there any technical difficulties to implement partial updates? How soon can it be expected?
PARs currently support update of individual bundles contained in the PAR, so this level of partial refresh would not be too difficult to add to the plan support. Testing is a little involved as the test needs to handle before after versions and check that the update has happened correctly.
However, since partial refresh of plans would really require exposing in the tooling to be useful, this isn't likely to happen soon. Also we have plenty of more urgent tasks to attend to.
If there's enough demand, then perhaps someone will contribute this to the Virgo project.
Users have their own tools, based on JMX calls to Deployer :) And really miss partial refresh, cause they are ready to go and use it :)Quote:
Originally Posted by Glyn Normington
Ok, then it would be really helpful if you could raise a bugzilla against Virgo to record this user story. Others can then vote up the requirement or even consider supplying a patch.
See www.eclipse.org/virgo for a link.