[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-44) Clarify resource type issues and API
[ http://tools.oasis-open.org/issues/browse/CAMP-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35127#action_35127 ]
Gilbert Pilz commented on CAMP-44:
----------------------------------
As I build out the components supported by nCAMP, this issue is looking more and more important. Currently nCAMP has only two ApplicationComponents and one PlatformComponent - but already there are problems. The "Tomcat WebApp" application component needs to be extended to surface the endpoint of the web app. The "MySQL Database Component" needs to be extended to surface the URI used to connect to that instance. By the decisions that we have made earlier, this requires me to create two new resource types - say "TCWebApp" and "MySQLDB". However, Section 5.16.1 says that the VitaMinder Assembly.applicationComponents array must contain links that reference ApplicationComponent resources. So TCWebApp MySQLDB resources must simultaneously be of a unique type (because they contain unique extensions) and be of type "applicationComponent".
I suggest we define a simple, single inheritance model wherein one resource type may be a sub-type of one other resource type. A sub-type must include all the attributes of its parent's type, these attributes must be of the same type, and must be at least as constrained as those of the parent. So a sub-type can say that an attribute that is optional in the parent is required in the sub-type, but it cannot say that an attribute that is required in the parent is optional in the sub-type. A sub-type can say that an attribute that can have an *arbitrary* String value in the parent must have a *specific* String value in the sub-type, etc.
> Clarify resource type issues and API
> -------------------------------------
>
> Key: CAMP-44
> URL: http://tools.oasis-open.org/issues/browse/CAMP-44
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Task
> Components: Spec
> Reporter: Alex Heneveld
> Priority: Minor
>
> There were several key questions about types that have come up in today's F2F:
> What type hierarchy will we use? Mark requests ability to define e.g. MyGreatDatabase which extends Database. (We could also have multiple inheritance / interface / etc.)
> How do we explore the type hierarchy? (The apidoc suggestion in CAMP-1 could come in here.)
> And do we permit dynamic attribute extensions -- e.g. a resource instance has values for other attributes not on its type? (Yes please!)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]