camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9320) Cannot set XStream permissions on a per CamelContext basis
Date Fri, 13 Nov 2015 12:18:11 GMT

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

ASF GitHub Bot commented on CAMEL-9320:
---------------------------------------

GitHub user tdiesler opened a pull request:

    https://github.com/apache/camel/pull/678

    [CAMEL-9320] Cannot set XStream permissions on a per CamelContext basis

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tdiesler/camel CAMEL-9320m

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/678.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #678
    
----
commit c4bc88d31958118028339b5cc85b84b6f1a6ce10
Author: Thomas Diesler <thomas.diesler@jboss.com>
Date:   2015-11-13T11:53:14Z

    [CAMEL-9320] Cannot set XStream permissions on a per CamelContext basis

----


> 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)

Mime
View raw message