On Fri, Jan 05, 2007 at 11:31:38AM -0800, lianep at eng.sun.com wrote: > A better solution is desired. Templates and using templates for some > sort of 'instance cloning' may be part of the answer (or may not), but > mean that I'd like to make it through the templates implementation > first before completely discarding the notion that we could address > situations 2 and 3 above elegantly.
Add to this a well-known property to indicate implementation origin and I think you have the right solution. Packages would then deliver template manifests and the system will do the right thing. On install one template per-service will result in :default instance. On updagre all instances with the same implementation label will be upgraded with the upgrade template manifest for instances of that same implementation. Then the only issue left is: how to select an implementation for the :default instance on install if there's more than one to choose from. Nico --
