[OASIS Issue Tracker] Commented: (CAMP-66) Creating instance of a Platform Component

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CAMP-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35932#action_35932 ] 

Gilbert Pilz commented on CAMP-66:
----------------------------------

Someone needs to jog my memory on the use case around creating a stand-alone Component (i.e. a Component that is not part of a tree of Components rooted in an Assembly) from a Service. Even if we stipulate that there will be long-lived Components (e.g. Heroku's free database servers) that exist independently of any one Assembly, surely creating such things is the job of the Platform Admin and therefore out of scope for CAMP?

> Creating instance of a Platform Component
> -----------------------------------------
>
>                 Key: CAMP-66
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-66
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Anish Karmarkar
>
> Issue 30 (Parameters) resolution talks about parameters on a PlatformComponentTemplate and the fact that the platform MUST accept POST on PlatformComponentTempaltes that specify parameters. This is a new feature that we have introduced. Given this resolution, we might want to specific exactly how those POSTs work by adding another subsection in the protocol section.

-- 
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