Sling
  1. Sling
  2. SLING-28

Simplify the Sling (aka Component) API

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3
    • Component/s: API
    • Labels:
      None

      Description

      JIRA issue to track simplification of the Sling (aka Component) API.

      See http://www.mail-archive.com/sling-dev@incubator.apache.org/msg00177.html for the discussion on the mailing list.

        Issue Links

          Activity

          Hide
          Felix Meschberger added a comment - - edited

          Commited first proposal in Rev. 581158 as project sling-api in trunk.

          The new API can be summarized as follows:

          • The API is renamed to Sling API and all prefixes changed to Sling...
          • Moved the API to the root Sling package org.apache.sling
          • The Component interfaces has been dropped and replaced by just using the Servlet interface
          • An abstract SlingServlet is added, which has a method taking SlingRequest and SlingResponse
          • No special Context and Session implementation any more (just use the ServletContext and HttpSession)
          • SlingResponse is empty: getNamespace is dropped, the other methods are Servlet API 2.4 replicas
          • Require Servlet API 2.4
          • Use servlet name (Servlet.getServletName) as identifier of servlets for Sling
          • Rename Content.getComponentId() to Content.getServletName() method referring to handling servlet

          Up for discussion ....

          Show
          Felix Meschberger added a comment - - edited Commited first proposal in Rev. 581158 as project sling-api in trunk. The new API can be summarized as follows: The API is renamed to Sling API and all prefixes changed to Sling... Moved the API to the root Sling package org.apache.sling The Component interfaces has been dropped and replaced by just using the Servlet interface An abstract SlingServlet is added, which has a method taking SlingRequest and SlingResponse No special Context and Session implementation any more (just use the ServletContext and HttpSession) SlingResponse is empty: getNamespace is dropped, the other methods are Servlet API 2.4 replicas Require Servlet API 2.4 Use servlet name (Servlet.getServletName) as identifier of servlets for Sling Rename Content.getComponentId() to Content.getServletName() method referring to handling servlet Up for discussion ....
          Hide
          Felix Meschberger added a comment -

          Updated the sling-api project with the latest findings of working on microsling in Rev. 588574

          Refer to the sling-dev list for discussion on this issue.

          Show
          Felix Meschberger added a comment - Updated the sling-api project with the latest findings of working on microsling in Rev. 588574 Refer to the sling-dev list for discussion on this issue.
          Hide
          Felix Meschberger added a comment -

          After many iterations and additions, the Sling API has now been submitted to a vote [1]. So I close this issue.

          If anything new surfaces regarding the Sling API, new issues should be created.

          [1] http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200711.mbox/%3c1193992693.12650.28.camel@bslm-046.corp.day.com%3e

          Show
          Felix Meschberger added a comment - After many iterations and additions, the Sling API has now been submitted to a vote [1] . So I close this issue. If anything new surfaces regarding the Sling API, new issues should be created. [1] http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200711.mbox/%3c1193992693.12650.28.camel@bslm-046.corp.day.com%3e

            People

            • Assignee:
              Felix Meschberger
              Reporter:
              Felix Meschberger
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development