[OASIS Issue Tracker] Commented: (CAMP-60) ApplicationComponentCapability is not linked by any resource Type

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

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

Adrian Otto commented on CAMP-60:
---------------------------------

Humble spec.

In the interest of keeping things simple, let's not solve for theoretical use cases. I have never seen anyone deploy one application to/a PaaS for the purpose of reuse by another, with one exception: when it is actually a service with a network accessible API and/or network protocol. In this case it needs an Assembly Template.

For this reason, I suggest that all PDP's produce an Assembly Template upon processing.

V.next can address more spophisticated deployment schemes based on actual end-user needs and implementations that implement extensions to service them.

> ApplicationComponentCapability is not linked by any resource Type
> -----------------------------------------------------------------
>
>                 Key: CAMP-60
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-60
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>            Reporter: Tom Rutt
>            Assignee: Gilbert Pilz
>
> The ApplicationComponentCapability resource type is not pointed at by any Resource Type.
> The PlatformComponentCapability resource type is pointed at by a link attribute of Platform.
> This seems to be a bug, as this resource, as it is currently defined, is be useless.

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