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 Mon, 28 Mar 2011 21:31:05 GMT

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

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

Just a status update: I got the main WebFragment logics up and working for most of the enhancer
root resources. The NavigationMixin needs to be updated to be use new contributions defined
as a new method contributed throught the WebFragment as well, e.g. WebFragment#getMenuItems()
or something.

The ImplicitView system does not work anymore for some reason: I have to set explicit @GET
methods that return a viewable on index instead... Not a big deal though.

The welcome page should be externalized in another bundle, and the list of HTTP services (endpoints)
should be made dynamic too (based on the  WebFragment#getMenuItems() with additional description
/ short documentation?

The integration tests need to be moved to the toplevel too: we can probably get rid of the
enhancer specific launchers too (or move them to the top level). Maybe this should be addressed
in another issue.


Have a good night a see you tomorrow on IRC to get that issue resolved :)

> 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