[
https://issues.apache.org/jira/browse/STANBOL-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216001#comment-14216001
]
Cristian Petroaca commented on STANBOL-1335:
--------------------------------------------
On Configurability via service properties:
On an earlier comment I asked the same question and Rupert's answer was:
"I am not aware that anyone has ever configured anything other as "Origins =
*". So I guess this feature is not really needed. Assuming that you implement
the filter as an OSGI Service it can be anyways added later on"
On Integration tests:
I'll look into that.
> 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
> Assignee: Reto Gmür
> Fix For: 1.0.0
>
> Attachments: cors_filter.patch
>
>
> 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)
