OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Created: (CAMP-21) Clarify that App Developers/Admins cannot assume what the Assembly Template tree looks like until post-deploy


Clarify that App Developers/Admins cannot 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


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]