[jira] [Created] (CAMEL-18687) camel-salesforce: Support Client Credentials OAuth Flow
Jeremy Ross created CAMEL-18687: --- Summary: camel-salesforce: Support Client Credentials OAuth Flow Key: CAMEL-18687 URL: https://issues.apache.org/jira/browse/CAMEL-18687 Project: Camel Issue Type: New Feature Components: camel-salesforce Affects Versions: 3.19.0 Reporter: Jeremy Ross -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18646) camel-git - Provide custom configuration
[
https://issues.apache.org/jira/browse/CAMEL-18646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628449#comment-17628449
]
Gilvan Filho commented on CAMEL-18646:
--
{quote}Nice solution, in this way, if different routes use another config file,
they will not mix up. is it correct?
{quote}
Correct. You could have for examples 2 config file in your resource folder and
reference them as you want. Or to have 1 config file and use this one sometimes
and use default (.gitconfig from user folder) other times.
I'm going to do some tests providing config through query params and mix them
with loaded configs. That way I think things will work as below:
# Camel-git loads config from supplied file or default
# Loaded configs are overrided by individual query params.
> camel-git - Provide custom configuration
>
>
> Key: CAMEL-18646
> URL: https://issues.apache.org/jira/browse/CAMEL-18646
> Project: Camel
> Issue Type: Improvement
> Components: camel-git
>Affects Versions: 3.19.0
>Reporter: Federico Mariani
>Priority: Major
>
> let camel users provide a custom git configuration, for example, disable SSL
> verification.
> https://git.eclipse.org/r/plugins/gitiles/jgit/jgit/+/refs/heads/master/Documentation/config-options.md
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18686) camel-resume-api: remove configuration via registry
Otavio Rodolfo Piske created CAMEL-18686: Summary: camel-resume-api: remove configuration via registry Key: CAMEL-18686 URL: https://issues.apache.org/jira/browse/CAMEL-18686 Project: Camel Issue Type: Improvement Components: camel-resume-api Affects Versions: 3.19.0 Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Fix For: 3.20.0 Remove the configuration using keys via the registry. Default to auto-configuration on the route. This makes the implementation simpler on Camel K and Camel Quarkus. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18685) camel-file: charset conversions causing UnmappableCharacterException
Otavio Rodolfo Piske created CAMEL-18685:
Summary: camel-file: charset conversions causing
UnmappableCharacterException
Key: CAMEL-18685
URL: https://issues.apache.org/jira/browse/CAMEL-18685
Project: Camel
Issue Type: Bug
Components: camel-file
Reporter: Otavio Rodolfo Piske
In the file component, reading a file that contains an unmappable character
causes the component to throw UnmappableCharacterException.
This happens because, by default, the behavior for handling unmapped characters
in the [Charset class is to report
them|https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/nio/charset/CharsetDecoder.html#decode(java.nio.ByteBuffer)].
Ideally, we should allow configuring the behavior so that it can either be
replaced or ignored. For instance, we can try tweaking the code to use
something like (in FileOperations) to ignore errors:
{code:java}
Charset.forName(charset).newDecoder().onMalformedInput(CodingErrorAction.IGNORE).charset();
{code}
Ignore is just one of the options. We may also want to try to replace them (as
Camel did prior to 2.20).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18646) camel-git - Provide custom configuration
[ https://issues.apache.org/jira/browse/CAMEL-18646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628418#comment-17628418 ] Federico Mariani commented on CAMEL-18646: -- Nice solution, in this way, if different routes use another config file, they will not mix up. is it correct? if this is the case, I like it! [~orpiske] do you have any opinion? > camel-git - Provide custom configuration > > > Key: CAMEL-18646 > URL: https://issues.apache.org/jira/browse/CAMEL-18646 > Project: Camel > Issue Type: Improvement > Components: camel-git >Affects Versions: 3.19.0 >Reporter: Federico Mariani >Priority: Major > > let camel users provide a custom git configuration, for example, disable SSL > verification. > https://git.eclipse.org/r/plugins/gitiles/jgit/jgit/+/refs/heads/master/Documentation/config-options.md -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18684) Add Microsoft Exchange Online OAuth2 Mail Authenticator
Luigi De Masi created CAMEL-18684:
-
Summary: Add Microsoft Exchange Online OAuth2 Mail Authenticator
Key: CAMEL-18684
URL: https://issues.apache.org/jira/browse/CAMEL-18684
Project: Camel
Issue Type: Improvement
Components: camel-mail
Reporter: Luigi De Masi
Add an implementation of {{org.apache.camel.component.mail.MailAuthenticator}}
to facilitate users that want to use OAuth2 authentication using Client
Credentials Flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18684) Add Microsoft Exchange Online OAuth2 Mail Authenticator
[
https://issues.apache.org/jira/browse/CAMEL-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luigi De Masi updated CAMEL-18684:
--
Priority: Minor (was: Major)
> Add Microsoft Exchange Online OAuth2 Mail Authenticator
> ---
>
> Key: CAMEL-18684
> URL: https://issues.apache.org/jira/browse/CAMEL-18684
> Project: Camel
> Issue Type: Improvement
> Components: camel-mail
>Reporter: Luigi De Masi
>Assignee: Luigi De Masi
>Priority: Minor
>
> Add an implementation of
> {{org.apache.camel.component.mail.MailAuthenticator}} to facilitate users
> that want to use OAuth2 authentication using Client Credentials Flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-18684) Add Microsoft Exchange Online OAuth2 Mail Authenticator
[
https://issues.apache.org/jira/browse/CAMEL-18684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luigi De Masi reassigned CAMEL-18684:
-
Assignee: Luigi De Masi
> Add Microsoft Exchange Online OAuth2 Mail Authenticator
> ---
>
> Key: CAMEL-18684
> URL: https://issues.apache.org/jira/browse/CAMEL-18684
> Project: Camel
> Issue Type: Improvement
> Components: camel-mail
>Reporter: Luigi De Masi
>Assignee: Luigi De Masi
>Priority: Major
>
> Add an implementation of
> {{org.apache.camel.component.mail.MailAuthenticator}} to facilitate users
> that want to use OAuth2 authentication using Client Credentials Flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18683) Priorize RouteTemplate initialization
[
https://issues.apache.org/jira/browse/CAMEL-18683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Rambichler updated CAMEL-18683:
---
Component/s: (was: came-core)
camel-main
> Priorize RouteTemplate initialization
> -
>
> Key: CAMEL-18683
> URL: https://issues.apache.org/jira/browse/CAMEL-18683
> Project: Camel
> Issue Type: Improvement
> Components: camel-main
>Reporter: Michael Rambichler
>Priority: Minor
>
> We often struggle the issue of the correct Route naming order dependency:
>
> *Improvement:* Priorize RouteBuilder with RouteTemplates
> *Testcase:*
> Name your RouteTemplate: ZTemplate
> and another Routebuilder which will use the defined Template in ZTemplate.
> The Routebuilder will fail because the ZTemplate Route was not yet added to
> the routescollections.
> *Suggestion:* Use a dedicated class e.g. RouteTemplateBuilder to prioritize
> Routebuilder with templates
> See: RoutesConfigure.java
> private void addDiscoveredRoutes(CamelContext camelContext,
> List routes) throws Exception {
> // sort routes according to ordered
> routes.sort(OrderedComparator.get());
> // first add the routes configurations as they are globally for all routes
> for (RoutesBuilder builder : routes) {
> if (builder instanceof RouteConfigurationsBuilder) {
> RouteConfigurationsBuilder rcb = (RouteConfigurationsBuilder)
> builder;
> LOG.debug("Adding routes configurations into CamelContext from
> RouteConfigurationsBuilder: {}", rcb);
> camelContext.addRoutesConfigurations(rcb);
> }
> }
> {color:#ff} // first add the all route templates as they are globally for
> all routes
> for (RoutesBuilder builder : routes) {
> if (builder instanceof RouteTemplateBuilder) {
> LOG.debug("Adding route tempaltes into CamelContext from RoutesBuilder:
> {}", builder);
> camelContext.addRoutes(builder);
> }
> }{color}
> // then add the routes
> for (RoutesBuilder builder : routes) {
> LOG.debug("Adding routes into CamelContext from RoutesBuilder: {}",
> builder);
> camelContext.addRoutes(builder);
> }
> }
> }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18683) Priorize RouteTemplate initialization
Michael Rambichler created CAMEL-18683:
--
Summary: Priorize RouteTemplate initialization
Key: CAMEL-18683
URL: https://issues.apache.org/jira/browse/CAMEL-18683
Project: Camel
Issue Type: Improvement
Components: came-core
Reporter: Michael Rambichler
We often struggle the issue of the correct Route naming order dependency:
*Improvement:* Priorize RouteBuilder with RouteTemplates
*Testcase:*
Name your RouteTemplate: ZTemplate
and another Routebuilder which will use the defined Template in ZTemplate.
The Routebuilder will fail because the ZTemplate Route was not yet added to the
routescollections.
*Suggestion:* Use a dedicated class e.g. RouteTemplateBuilder to prioritize
Routebuilder with templates
See: RoutesConfigure.java
private void addDiscoveredRoutes(CamelContext camelContext, List
routes) throws Exception {
// sort routes according to ordered
routes.sort(OrderedComparator.get());
// first add the routes configurations as they are globally for all routes
for (RoutesBuilder builder : routes) {
if (builder instanceof RouteConfigurationsBuilder) {
RouteConfigurationsBuilder rcb = (RouteConfigurationsBuilder) builder;
LOG.debug("Adding routes configurations into CamelContext from
RouteConfigurationsBuilder: {}", rcb);
camelContext.addRoutesConfigurations(rcb);
}
}
{color:#ff} // first add the all route templates as they are globally for
all routes
for (RoutesBuilder builder : routes) {
if (builder instanceof RouteTemplateBuilder) {
LOG.debug("Adding route tempaltes into CamelContext from RoutesBuilder:
{}", builder);
camelContext.addRoutes(builder);
}
}{color}
// then add the routes
for (RoutesBuilder builder : routes) {
LOG.debug("Adding routes into CamelContext from RoutesBuilder: {}",
builder);
camelContext.addRoutes(builder);
}
}
}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18682) Camel-Plc4x: Add a Spring Boot starter
Andrea Cosentino created CAMEL-18682: Summary: Camel-Plc4x: Add a Spring Boot starter Key: CAMEL-18682 URL: https://issues.apache.org/jira/browse/CAMEL-18682 Project: Camel Issue Type: New Feature Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.20.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18646) camel-git - Provide custom configuration
[
https://issues.apache.org/jira/browse/CAMEL-18646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628310#comment-17628310
]
Gilvan Filho commented on CAMEL-18646:
--
Hi [~Federico Mariani]
I made some tests with that and I was able to pass a .gitconfig like file to be
used as custom config through custom System Reader as exposed in Stack
Overflow. That was done passing to endpoint a new query parameter (String) with
path to a .gitconfig file. That way file could be on OS dirs or on resource
folder. With that you could override all git configs as you want. But this is
not mandatory. If user doesn`t provide that file camel-git will load that from
users home folder as default behavior of JGit does.
{code:java}
from("git://repo?gitConfigFile=/tmp/gitconfig").to(...) //that way will load
from OS dirs
from("git://repo?gitConfigFile=gitconfig").to(...) //that way will load from
resources folder
from("git://repo").to(...) //that way will load from users home dir as
default{code}
Said that, is still possible allows user to provide only some desired
configurations through endpoint query params and override them in loaded
configuration no matter if that was default or from a provided through
gitConfigFile endpoint query param. But here I think we need pay attention in 2
points:
* There are a lot of options as exposed
[here|https://git.eclipse.org/r/plugins/gitiles/jgit/jgit/+/refs/heads/master/Documentation/config-options.md].
To allow the user provide all could turn things hard. Maybe defining some
settings that will be exposed this way is a simpler way to do that.
* We need to care about side effects avoiding configs made in one endpoint
affect others. I will do some tests with that.
With that two things users will have great flexibility to config as they needs.
What do you think about?
> camel-git - Provide custom configuration
>
>
> Key: CAMEL-18646
> URL: https://issues.apache.org/jira/browse/CAMEL-18646
> Project: Camel
> Issue Type: Improvement
> Components: camel-git
>Affects Versions: 3.19.0
>Reporter: Federico Mariani
>Priority: Major
>
> let camel users provide a custom git configuration, for example, disable SSL
> verification.
> https://git.eclipse.org/r/plugins/gitiles/jgit/jgit/+/refs/heads/master/Documentation/config-options.md
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18681) Add an example on how to marshal List of JSON files to single AVRO file
[ https://issues.apache.org/jira/browse/CAMEL-18681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18681. -- Resolution: Invalid For request like this you could either use the mailing list or zulip chat. Thanks. > Add an example on how to marshal List of JSON files to single AVRO file > --- > > Key: CAMEL-18681 > URL: https://issues.apache.org/jira/browse/CAMEL-18681 > Project: Camel > Issue Type: Wish > Components: camel-avro >Affects Versions: 3.18.3 > Environment: Ubuntu 18.04 > >Reporter: Andrii Melashchenko >Priority: Minor > > I failed to implement simple route to dump MongoDB Documents queried via > `findAll` query to Avro data format for further usage in AWS Glue (Apache > Hive) + AWS Athena (Trino) as data source. > It will be great if camel team can provide explicit example on how to marshal > List of the Documents to Avro file. > MongoDB -> List -> file.avro (with schema if possible) > Thank you in advance! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18681) Add an example on how to marshal List of JSON files to single AVRO file
[ https://issues.apache.org/jira/browse/CAMEL-18681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Melashchenko updated CAMEL-18681: Summary: Add an example on how to marshal List of JSON files to single AVRO file (was: Add example on how to marshal List of JSON file to single AVRO file) > Add an example on how to marshal List of JSON files to single AVRO file > --- > > Key: CAMEL-18681 > URL: https://issues.apache.org/jira/browse/CAMEL-18681 > Project: Camel > Issue Type: Wish > Components: camel-avro >Affects Versions: 3.18.3 > Environment: Ubuntu 18.04 > >Reporter: Andrii Melashchenko >Priority: Minor > > I failed to implement simple route to dump MongoDB Documents queried via > `findAll` query to Avro data format for further usage in AWS Glue (Apache > Hive) + AWS Athena (Trino) as data source. > It will be great if camel team can provide explicit example on how to marshal > List of the Documents to Avro file. > MongoDB -> List -> file.avro (with schema if possible) > Thank you in advance! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18681) Add example on how to marshal List of JSON file to single AVRO file
Andrii Melashchenko created CAMEL-18681: --- Summary: Add example on how to marshal List of JSON file to single AVRO file Key: CAMEL-18681 URL: https://issues.apache.org/jira/browse/CAMEL-18681 Project: Camel Issue Type: Wish Components: camel-avro Affects Versions: 3.18.3 Environment: Ubuntu 18.04 Reporter: Andrii Melashchenko I failed to implement simple route to dump MongoDB Documents queried via `findAll` query to Avro data format for further usage in AWS Glue (Apache Hive) + AWS Athena (Trino) as data source. It will be great if camel team can provide explicit example on how to marshal List of the Documents to Avro file. MongoDB -> List -> file.avro (with schema if possible) Thank you in advance! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18680) Wrong initialization of KeyStoreParameters causes java.lang.IllegalArgumentException
Jiri Ondrusek created CAMEL-18680:
-
Summary: Wrong initialization of KeyStoreParameters causes
java.lang.IllegalArgumentException
Key: CAMEL-18680
URL: https://issues.apache.org/jira/browse/CAMEL-18680
Project: Camel
Issue Type: Bug
Components: camel-core-api, camel-vertx
Affects Versions: 3.20.0
Reporter: Jiri Ondrusek
Assignee: Jiri Ondrusek
Newly added validation on
[JsseParameters|https://github.com/apache/camel/commit/2d1a56c2282229478f812eb7f573479428d128d3#diff-f9902a7576d2dce46871a88c8ad5694f6bf4036c83d46d3da5cf7a2c84fe6df1R116]
is not respected on several places using KeStoreParamaterts.
I encountered a failure on camel-quarkus/http extension and on several
vertx-http tests in Camel (VertxHttpSSLTest and
VertxHttpSSLGlobalConfigurationTest)
The error message is
{quote}java.lang.IllegalArgumentException: CamelContext must be specified on:
KeyStoreParameters[type=null, password=, provider=null,
resource=/jsse/keystore.p12]{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18646) camel-git - Provide custom configuration
[ https://issues.apache.org/jira/browse/CAMEL-18646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17628282#comment-17628282 ] Federico Mariani commented on CAMEL-18646: -- Hello [~gilvansfilho], thanks for your reply, do you think it is possible/worth creating a temp gitconfig file and a custom SystemReader implementation, in this way it should be possible to: * copy system config to temp config * Update the SystemReader via _SystemReader.setInstance(...)_ * In this way it should be possible to pass options on the camel route ex. git://repo?operation=init=http.sslVerify=true * so that http.sslVerify is added to the temp configuration and we do not mess with user config or ask user to provide a file What do you think? Part of this StackOverflow may help [https://stackoverflow.com/questions/33804097/prevent-jgit-from-reading-the-native-git-config#answer-59110721] > camel-git - Provide custom configuration > > > Key: CAMEL-18646 > URL: https://issues.apache.org/jira/browse/CAMEL-18646 > Project: Camel > Issue Type: Improvement > Components: camel-git >Affects Versions: 3.19.0 >Reporter: Federico Mariani >Priority: Major > > let camel users provide a custom git configuration, for example, disable SSL > verification. > https://git.eclipse.org/r/plugins/gitiles/jgit/jgit/+/refs/heads/master/Documentation/config-options.md -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18679) Bind mount support
Edyta Baluta created CAMEL-18679: Summary: Bind mount support Key: CAMEL-18679 URL: https://issues.apache.org/jira/browse/CAMEL-18679 Project: Camel Issue Type: Improvement Components: camel-docker Reporter: Edyta Baluta That would be very usefull if camel-docker would support DOCKER_BINDS message headers. It's not working so far. Setting headers like Docker_bind is ignored. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18675) camel-resume-api: implement resume strategy auto-instantiation
[ https://issues.apache.org/jira/browse/CAMEL-18675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-18675: - Description: Allow the resume strategies to be instantiated automatically by Camel in way similar to what is done for the Adapters. (was: Currently, the strategies are usually instantiated outside of the route. This makes it both harder for using them as well as harder to get access to the context (i.e.: in order to access the ExecutorServiceManager, for instance). This leads to a solution that is not very elegant use and harder to implement.) > camel-resume-api: implement resume strategy auto-instantiation > -- > > Key: CAMEL-18675 > URL: https://issues.apache.org/jira/browse/CAMEL-18675 > Project: Camel > Issue Type: Improvement >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > > Allow the resume strategies to be instantiated automatically by Camel in way > similar to what is done for the Adapters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18675) camel-resume-api: implement resume strategy auto-instantiation
[ https://issues.apache.org/jira/browse/CAMEL-18675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-18675: - Summary: camel-resume-api: implement resume strategy auto-instantiation (was: Simplify getting access to the CamelContext in Resume Strategies) > camel-resume-api: implement resume strategy auto-instantiation > -- > > Key: CAMEL-18675 > URL: https://issues.apache.org/jira/browse/CAMEL-18675 > Project: Camel > Issue Type: Improvement >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > > Currently, the strategies are usually instantiated outside of the route. This > makes it both harder for using them as well as harder to get access to the > context (i.e.: in order to access the ExecutorServiceManager, for instance). > This leads to a solution that is not very elegant use and harder to implement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18678) Simplify getting access to the CamelContext in Resume Strategies
Otavio Rodolfo Piske created CAMEL-18678: Summary: Simplify getting access to the CamelContext in Resume Strategies Key: CAMEL-18678 URL: https://issues.apache.org/jira/browse/CAMEL-18678 Project: Camel Issue Type: Improvement Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Currently, the strategies are usually instantiated outside of the route. This makes it both harder for using them as well as harder to get access to the context (i.e.: in order to access the ExecutorServiceManager, for instance). This leads to a solution that is not very elegant use and harder to implement. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18677) camel-resume-api: allow setting the cache on the configuration builder
Otavio Rodolfo Piske created CAMEL-18677:
Summary: camel-resume-api: allow setting the cache on the
configuration builder
Key: CAMEL-18677
URL: https://issues.apache.org/jira/browse/CAMEL-18677
Project: Camel
Issue Type: Improvement
Components: camel-resume-api
Reporter: Otavio Rodolfo Piske
Assignee: Otavio Rodolfo Piske
We should be able to configure the cache on the resume strategy configuration
builders:
{code:java}
KafkaResumeStrategyConfigurationBuilder kafkaConfigurationBuilder =
KafkaResumeStrategyConfigurationBuilder.newBuilder()
.withBootstrapServers("kafka-address:9092")
.withTopic("offset")
.withProducerProperty("max.block.ms", "1")
.withMaxInitializationDuration(Duration.ofSeconds(5))
.withCache(myCacheInstance); // <--- like this
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
