Hi Andy,
Does Jena support running with active SecurityManager? If this is the
case you can wrap calls like that in a
AccessController.doPrivileged(
new PrivilegedAction<Object>(){
public Object run(){
/* the privileged code*/
return value; //or null if not needed
}
}
);
If Jena is not concerned about a SecurityManager nothing need to be
changed. In that case other calling it need to care. As Clerezza does
care about this it should be done in the JenaSparqlEngine.
For now I have fixed the issue in Stanbol by wrapping my call in an
doPrivileged block as mentioned above.
best
Rupert
On Tue, Dec 17, 2013 at 7:20 PM, Andy Seaborne <a...@apache.org> wrote:
> On 17/12/13 14:21, Sergio Fernández wrote:
>>
>> On 17/12/13 11:14, Andy Seaborne wrote:
>>>
>>> Jena version? (Just so line numbers line up - the code hasn't changed in
>>> a while around here.)
>>
>>
>> Pretty old... Jena 2.6.5 from Clerezza 0.5-incubating.
>> Andy, never mind, not a Jena issue, but a Clerezza one.
>
>
> Works for me :-)
>
> I'm still like to know what the right thing (tm) to get to XML datatype
> factory is. We'll armour the code anyway but that's merely stopping the
> exception propagating unhelpfully and attempt emergency repairs which may or
> may not work.
>
> Andy
>
--
| Rupert Westenthaler rupert.westentha...@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
