You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Alessandro Adamou (JIRA)" <ji...@apache.org> on 2011/04/05 09:18:05 UTC

[jira] [Reopened] (STANBOL-120) Refactor HTTP Endpoint

     [ https://issues.apache.org/jira/browse/STANBOL-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessandro Adamou reopened STANBOL-120:
---------------------------------------

      Assignee: Alessandro Adamou  (was: Olivier Grisel)

With the current build order in the reactor, a build with an empty local repo seems to fail upon reaching the Enhancer Sling package.

> Refactor HTTP Endpoint
> ----------------------
>
>                 Key: STANBOL-120
>                 URL: https://issues.apache.org/jira/browse/STANBOL-120
>             Project: Stanbol
>          Issue Type: Improvement
>          Components: Enhancer, Web UI
>            Reporter: Fabian Christ
>            Assignee: Alessandro Adamou
>              Labels: Endpoint, HTTP, Refactoring
>
> The Stanbol HTTP endpoint entry point is currently packaged in the enhancer/jersey bundle.
> The HTTP endpoint should be refactored into its own top level OSGi bundle called org.apache.stanbol.web. Other components, like the enhancer, can then contribute their JAXRS resources to this top level bundle.
> The top level web bundle should not have any knowledge about concrete bundles that contribute their JAXRS resources to this web bundle.
> - New bundles register their JAXRS resources at the commons web bundle.
> - The commons web bundle is responsible for making the resources available.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira