[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (CAMP-20) Failure to deploy when dependencies are not resolved is not workable
[ http://tools.oasis-open.org/issues/browse/CAMP-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Chapman updated CAMP-20:
--------------------------------
Assignee: Gilbert Pilz
> Failure to deploy when dependencies are not resolved is not workable
> --------------------------------------------------------------------
>
> Key: CAMP-20
> URL: http://tools.oasis-open.org/issues/browse/CAMP-20
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Bug
> Components: Spec
> Reporter: Anish Karmarkar
> Assignee: Gilbert Pilz
>
> In CAMP 1.0, section 3.2, the following sentence appears at the end of the first paragraph:
> "If the required dependencies are not resolved or if the metadata is incomplete, the register transition shall not happen."
> The problem with this is that the HTTP resources defined by CAMP aren't created until the application is registered. Application Administrators will have no way of fixing the unresolved dependencies (e.g. by wiring the Assembly Template to an Platform Component Template) because they will have no Assembly Template with which to work.
> [This issue was raised by Gilbert Pilz and was drupal issue # 1091]
--
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]