[
https://issues.apache.org/jira/browse/CAMEL-9297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998318#comment-14998318
]
Akitoshi Yoshida commented on CAMEL-9297:
-----------------------------------------
Hi Claus,
yes. After I saw your mail last night, I realized that we should make it
simpler.
One point of complexity that I want to add to your suggestion is the allows and
denies flag. Without this flag, it will become verbose to exclude or include
specific classes within a package.
For this, we could also use two attributes like Camel's removeHeaders does with
its excludes attribute. However, with that approach, we need to sort the
entries of the two attributes in the order of specific to generici/wildcards,
and invoke the corresponding Explicit or Wildcard type permission methods of
XStream. Therefore, it is more practical to introduce a suffix + and - (where +
can be optional) to indicate whether the term is allowed or denied.
How do you think?
regards, aki
> Expose more configuration options from Camel's XStream component
> ----------------------------------------------------------------
>
> Key: CAMEL-9297
> URL: https://issues.apache.org/jira/browse/CAMEL-9297
> Project: Camel
> Issue Type: Improvement
> Components: camel-xstream
> Affects Versions: 2.16.0, 2.15.4
> Reporter: Akitoshi Yoshida
> Assignee: Akitoshi Yoshida
> Attachments:
> 0001-CAMEL-9297-Expose-more-configuration-options-from-Ca.patch
>
>
> Currently, some of the configuration options of XStream are only configurable
> over the XStream API. This means, the user must instantiate an instance of
> XStream and configure that instance and assign it to Camel's XStream
> component to configure these options.
> This patch will add a more convenient way to set these additional options
> directly over Camel's XStream component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
