Re: [camp] [OASIS Issue Tracker] Updated: (CAMP-150) mechanism for creating an Assembly (or Plan) by value (i.e. POSTing the contents of a PDP or Plan file) is difficult to use

[Gilbert Pilz <gilbert.pilz@oracle.com>]

Please review the latest proposal before tomorrow's call.

~ gp

On Jan 7, 2014, at 6:35 PM, OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> wrote:

> 
>     [ http://tools.oasis-open.org/issues/browse/CAMP-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> 
> Gilbert Pilz updated CAMP-150:
> ------------------------------
> 
>    Proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/51874/camp-spec-v1.1-wd32-150-v5.doc  (was: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/51798/camp-spec-v1.1-wd32-150-v4.doc)
> 
> Updated proposal to require Providers to support both MIME and non-MIME variants when deploying an application by value or registering a plan by value.
> 
>> mechanism for creating an Assembly (or Plan) by value (i.e. POSTing the contents of a PDP or Plan file) is difficult to use
>> ---------------------------------------------------------------------------------------------------------------------------
>> 
>>                Key: CAMP-150
>>                URL: http://tools.oasis-open.org/issues/browse/CAMP-150
>>            Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>>         Issue Type: Bug
>>         Components: Spec
>>           Reporter: Gilbert Pilz
>>           Assignee: Gilbert Pilz
>>           Priority: Critical
>> 
>> We've been back and forth on this a couple of times but, be that as it may, the current version of the spec (WD 29) defines a mechanism for creating either Assemblies or Plans by value that makes it difficult to write simple clients for CAMP. Specifically, Sections 6.11 and 6.12 WD 29 says that the contents of either the PDP or the Plan file should be placed in the body of the POST request message; no multipart/form-data etc.
>> This mechanism make it difficult to write a simple client that can upload applications to an CAMP cloud. HTML forms will not work, there are no Javascript libraries (that I can find) that work this way, even soapUI can't be made to do this (nCAMP implements an extension that accepts multipart/form-data requests). It might not seem like a big deal, but I believe that the inability to support simple clients will have a large negative impact on CAMP's adoption. For someone not sure of the benefits of CAMP, making them jump major technical hurdles to implement their first use case is likely to cause them to give up and write CAMP off as "too complicated".
> 
> -- 
> 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
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>