[
https://issues.apache.org/jira/browse/STANBOL-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14193937#comment-14193937
]
Cristian Petroaca commented on STANBOL-1335:
--------------------------------------------
Checked the library you pointed out and I seems it does the job.
Attached are the changes done. I added the 3rd party lib as an embedded
dependency in the cors filter bundle. I assumed there is no value in exposing
the library as a bundle since it is very specific in nature and my CorsFilter
bundle is the only one which uses it.
I tested the changes on Chrome, Firefox and IE. I used the following code in
cors.html which was fetched from another server I ran on another computer in
order to contact the Stanbol server on my PC:
<!DOCTYPE html>
<html>
<head>
<script src="https://code.jquery.com/jquery-2.1.1.min.js";></script>
</head>
<body>
<button id="button">Try it</button>
<p id="demo"></p>
<script>
$("button").click(function(){
$.ajax({url:"http://cpetroaca-pc:8080/enhancer";,
success:function(result){
$("#resultDiv").html(result);
}});
});
</script>
<div id="resultDiv"></div>
</body>
</html>
> 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
>
> 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)
