Failure to deploy when dependencies are not resolved is not workable

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: Spec
    • None
    • Hide

      From Gil: Remove the offending sentence.
      From Tobias: Alternatively, the registration could happen with a special attribute marking it as "unresolved". Then the assembly could be inspected.

      Show
      From Gil: Remove the offending sentence. From Tobias: Alternatively, the registration could happen with a special attribute marking it as "unresolved". Then the assembly could be inspected.

      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

            Assignee:
            Gilbert Pilz (Inactive)
            Reporter:
            Anish Karmarkar (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: