[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-21) Clarify whether App Developers/Admins can assume what the Assembly Template tree looks like until post-deploy
[ http://tools.oasis-open.org/issues/browse/CAMP-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32432#action_32432 ]
Gilbert Pilz commented on CAMP-21:
----------------------------------
This is a P1 issue, so we need to start making progress on it. Although the resolution of this issue could result in some text being added to the spec, at this point in time I think that what is important about this issue is the constraints it places on the design of the PDP.
Just to get things started, I think the answer to this question is "No, Application Developers and Application Administrators CANNOT assume they know what the AssemblyTemplate tree will look like until *after* they have registered the PDP."
As far as the design of the PDP goes, this means that it CANNOT contain representations of things like the AssemblyTemplate, Application Component Templates, etc. These resources are created when the PDP is registered and different CAMP implementations MAY create different representations of the same application.
> Clarify whether App Developers/Admins can assume what the Assembly Template tree looks like until post-deploy
> -------------------------------------------------------------------------------------------------------------
>
> Key: CAMP-21
> URL: http://tools.oasis-open.org/issues/browse/CAMP-21
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Improvement
> Components: Spec
> Reporter: Anish Karmarkar
> Assignee: Gilbert Pilz
> Priority: Critical
>
> The resources described by CAMP (e.g. Assembly Template, Application Component Template) represent (among other things) points of management control. Different providers may support different levels of management granularity. For, example, consider the Tomcat sample application. This application is made up of a single WAR file (sample.war) that contains a static HTML file (index.html), a JSP file (hello.jsp), and a servlet class (Hello.class).
> One provider could choose to model this application as an Assembly Template with a single Application Component Template consisting of the sample.war file. Another provider could choose to model the application with multiple Application Component Templates - one for the static, index.html file and one for the Servlet/JSP files (hello.jsp and Hello.class). It depends on the level of management granularity implemented by the provider.
> Unless they have out-of-band knowledge of their target platform, App Developers/Admins can't assume anything about the structure of the post-deploy Assembly Template tree other than the fact that one app => one Assembly Template. Any assumptions they do make about this structure may constrain the portability of their app to other platforms.
> [This issue was raised by Gilbert Pilz and was drupal issue # 1092
--
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]