Hi Brad,
This looks good. I did the
same exercise and came up with the same results (that’s always good).
I also included the package descriptor and there is only one usage of QName but
for completeness I thought I would add it to the thread.
PackageIdentityType.@contentType
– package content (e.g. BIOS)
I have some changes I’m
working on for the profile schema as well as an instance doc for the COSMOS
example. I’m hoping to have that done prior to the 3:30 call today
but it will be cutting it close.
Regards,
-Jason
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On
Behalf Of Beck, Bradley C
Sent: Wednesday, January 28, 2009 2:53 PM
To: cosmos-dev@xxxxxxxxxxx
Subject: [cosmos-dev] SDD Profile QNames...
This is an attempt to solidify my understanding of where, in
the deployment descriptor, profile QNames are intended to be used. Also,
I’m trying to draw out any behavior implied through the location and
usage of profile QNames.
To that end, I’ve compiled a list of attributes and
elements that are specified to have a value of QName. Beside each I’ve
given a short indication of what I think the intended behavior/action .
{of general type ArtifactType.@type} – action handler
(e.g. configure, install, undo, update, use, uninstall)
InstallArtifact.@type
UpdateArtifact.@type
UndoArtifact.@type
UninstallArtifact.@type
ConfigArtifact.@type
AdditionalContent.@type
{of general type ResourceType.@type} – resource
modeling/mapping, topology verification
Resource.@type
HostedResource.@type
ResourcePropertyType.@propertyName – query resource
for property value
PropertyType.PropertyName – resource modeling/mapping,
configuration
CapacityConstraintType.PropertyName – validation
ConsumptionConstraintType.PropertyName – validation
PropertyConstraintType.PropertyName – validation
ConditionalPropertyConstraintType.PropertyName –
validation
It seems that any “profile handler”
implementation would need to support all of the above behaviors.
Bradley Beck
CA, Inc.
Sr Software Architect
Tel: +1-952-232-1720
Bradley.Beck@xxxxxx