[
https://issues.apache.org/jira/browse/STANBOL-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186698#comment-14186698
]
Rupert Westenthaler commented on STANBOL-1335:
----------------------------------------------
ad2: The ordering of different Servlet filter depends AFAIK on the configured
"service.ranking". Meaning that you do not need to care about it as the
ordering can be enforced by the configuration. So if one wants to send CORS
headers as query parameter he needs to make sure that the QueryHeadersFilter
comes before the CORS filter by configuring a higher "service.ranking" to the
QueryHeadersFilter.
just got a tip from a Apache Marmotta developer that they are using [1] for
supporting CORS by a Servlet Filter. So maybe you should have a look at this
lib.
[1] https://bitbucket.org/thetransactioncompany/cors-filter
> 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)
