[
https://issues.apache.org/jira/browse/STANBOL-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176254#comment-14176254
]
Cristian Petroaca commented on STANBOL-1335:
--------------------------------------------
Rupert suggested that I could take care if this Jira.
I searched for possble solutions to adding cors to the Jersey restful resources
in Stanbol and the library Florent found was pretty much the only one.
There is also a Jersey Jira https://java.net/jira/browse/JERSEY-1562 for adding
CORS support and this seems like the best way to enable CORS in Stanbol but
that doesn't seem likely to be solved any time soon.
Aside from third party libraries there is also the solution of adding our own
Jersey Filter in the system which would handle both preflight and actual cors
requests. This would lack the annotation system from the palominolabs jersey
library but do we really need to have cors support for specific REST endpoints?
> Re-enable CORS support
> ----------------------
>
> Key: STANBOL-1335
> URL: https://issues.apache.org/jira/browse/STANBOL-1335
> Project: Stanbol
> Issue Type: Sub-task
> Reporter: Rupert Westenthaler
> Fix For: 1.0.0
>
>
> The Stanbol trunk currently does not support CORS as the old code used in
> 0.12 is deactivated and the proposed solution - by using a Servlet Filter -
> was not yet implemented.
> Workaround: Use the 0.12.0 release or the 0.12-releasing branch version
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
