incubator-stanbol-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Grisel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STANBOL-120) Refactor HTTP Endpoint
Date Tue, 29 Mar 2011 10:04:05 GMT

    [ https://issues.apache.org/jira/browse/STANBOL-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012417#comment-13012417
] 

Olivier Grisel commented on STANBOL-120:
----------------------------------------

Before implementing the pluggable navigation, we need to extend the WebFragment interface
to be able register resources such as scrips and style sheets.

> 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: Fabian Christ
>              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

Mime
View raw message