You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org> on 2012/11/29 18:38:58 UTC
[jira] [Commented] (STANBOL-352) make stanbol web services (root
resource classes) more portable
[ https://issues.apache.org/jira/browse/STANBOL-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506615#comment-13506615 ]
Reto Bachmann-Gmür commented on STANBOL-352:
--------------------------------------------
Part of it done by STANBOL-750 and by STANBOL-822. Service vs. webfragment issue not yet addressed.
> make stanbol web services (root resource classes) more portable
> ---------------------------------------------------------------
>
> Key: STANBOL-352
> URL: https://issues.apache.org/jira/browse/STANBOL-352
> Project: Stanbol
> Issue Type: Improvement
> Reporter: Reto Bachmann-Gmür
>
> Despite using the jax-rs (jsr 311) standard stanbol web components aren't very portable. The components depend on jersey mostly for producing html representation (using freemarker) furthermore they user the ServletContext to access osgi services (while this should work with other servlet based jax-rs implementation the standard osgi/osgi-ds mechanism should be used). There are also some apparent jersey dependencies that in fact aren't, for instance org.apache.stanbol.entityhub.jersey.utils.JerseyUtils doesn't depend on jersey.
> To improve portability I suggest to:
> - let all root resources be osgi-ds components and have their dependencies injected
> And either:
> - extract Viewable and the respective MessageBodyWriter from Jersey to a separate bundle so that they can be used on any compliant jax-rs implementation
> - separate rest interfaces that do not need rendering from the ui produced using freemarker. This would allow to at least run the REST-endpoint for machines on other platform.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira