Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 13 Nov 2015 14:39:11 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12912795.1447413380000.62029.1447425551051@Atlassian.JIRA>
In-Reply-To: <JIRA.12912795.1447413380000@Atlassian.JIRA>
References: <JIRA.12912795.1447413380000@Atlassian.JIRA>
 <JIRA.12912795.1447413380498@arcas>
Subject: [jira] [Commented] (CAMEL-9320) Cannot set XStream permissions on a
 per CamelContext basis
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004044#comment-15004044 ] 

Claus Ibsen commented on CAMEL-9320:
------------------------------------

The tests of camel+xstream was lacking to specify the types they are using, this has been updated and you should do like they do. 

> Cannot set XStream permissions on a per CamelContext basis
> ----------------------------------------------------------
>
>                 Key: CAMEL-9320
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9320
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: Thomas Diesler
>             Fix For: 2.16.1
>
>
> One would expect to set xstream permissions on the DataFormat associated with a given CamelContext like this
> {code}
>         XStreamDataFormat dataFormat = (XStreamDataFormat) camelctx.resolveDataFormat("xstream");
>         dataFormat.setPermissions("+" + Customer.class.getName());
> {code}  
> This approach fails however because the DefaultDataFormatResolver does not cache the DataFormat instances it creates 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)