dm Server
  1. dm Server
  2. DMS-73

Developer uses OSGi standard API for registering servlets

    Details

    • Type: Story Story
    • Status: Done Done
    • Priority: Major Major
    • Resolution: Won't Fix
    • Fix Version/s: 2.0.0.RELEASE
    • Component/s: Servlet, Web
    • Labels:
      None

      Description

      Currently it seems the only way to specify that a bundle contains a Servlet is via S2AP's specialised manifest header "Web-Servlets". However OSGI also provides a standardised API for the registration of Servlets via the "org.osgi.service.http". Within the current beta of S2AP, this API doesn't seem to be available. If it is available within the platform, I can only assume its not being exported for use by other bundles.

      Consequently any pre-existing OSGI bundles that use this API to register any Servlets they may contain, are forced to make changes, most likely both within code and the manifest to enable them to be compatible with S2AP. As such, it would be very useful to have the org.osgi.service.http API available for Servlet registration.

        Activity

        Hide
        Neale Upstone added a comment -

        Shame to see the OSGi service not supported in version 1.0.

        If SS want high adoption, then allowing people to move seamlessly from Equinox to SSAP seems a sensible move.

        Does anyone have a workaround?

        Show
        Neale Upstone added a comment - Shame to see the OSGi service not supported in version 1.0. If SS want high adoption, then allowing people to move seamlessly from Equinox to SSAP seems a sensible move. Does anyone have a workaround?
        Hide
        Immanuel Scheerer added a comment -

        Remove existing web application with context path "/". Then just deploy the attached httpservice.war, and you will have a working HttpService.

        The web application depends on org.eclipse.equinox.http.servlet .

        Show
        Immanuel Scheerer added a comment - Remove existing web application with context path "/". Then just deploy the attached httpservice.war, and you will have a working HttpService. The web application depends on org.eclipse.equinox.http.servlet .
        Hide
        Rob Harrop added a comment -

        This is superceded by our support for RFC66 which is a superset of the HttpService spec.

        We're not fully complete on our implementation yet, but we will be and HttpService will be part of that final implementation.

        Thanks for taking the time to report and comment.

        Regards,

        Rob

        Show
        Rob Harrop added a comment - This is superceded by our support for RFC66 which is a superset of the HttpService spec. We're not fully complete on our implementation yet, but we will be and HttpService will be part of that final implementation. Thanks for taking the time to report and comment. Regards, Rob

          People

          • Assignee:
            Unassigned
            Reporter:
            Daniel Murley
          • Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              First Response Date: