[
https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113209#comment-17113209
]
Zheng Feng edited comment on CAMEL-14805 at 6/2/20, 1:00 AM:
-------------------------------------------------------------
[~gnodet], I get a list of extension from the camel-quarkus currently, which
the camel component has the doStart.
||Component||Status||Reason||
|camel-ahc|REJECT|create thread pool|
|camel-aws2-s3| | |
|camel-aws-ec2| | |
|camel-aws-ecs| | |
|camel-aws-eks| | |
|camel-aws-iam| | |
|camel-aws-kinesis| | |
|camel-aws-kms| | |
|camel-aws-lambda| | |
|camel-aws-s3| | |
|camel-aws-sdb| | |
|camel-aws-swf| | |
|camel-aws-translate| | |
|camel-bean|DONE| |
|camel-dataformat|DONE| |
|camel-dozer|DONE| |
|camel-file|DONE| |
|camel-infinispan|REJECT|start a server and create thread |
|camel-jira|REJECT|create the http client |
|camel-kubernetes|REJECT|OKHttp client create thread pool |
|camel-kudu|REJECT|create thread pool|
|camel-log|DONE| |
|camel-mongodb|REJECT| resolve the MongClient from the camelContext and it
potentially open the connection and run the command |
|camel-netty-http|DONE| |
|camel-olingo4|REJECT|create the asyn http client |
|camel-platform-http|DONE| |
|camel-quartz|REJECT|quartz schedule create thread pool |
|camel-ref|REJECT|add the other endpoint uri |
|camel-salesforce|REJECT|create a http client and start it |
|camel-seda|DONE| |
|camel-sjms|REJECT|create connections pool |
|camel-sql|DONE| |
|camel-stream|DONE| |
|camel-telegram|REJECT|create thread pool |
|camel-timer|DONE| |
|camel-xslt|DONE| |
I'd like to take a look at these component at first and ignore what use the
XXXClient to open the network connection which I think should not be moved to
doInit(). I just wonder what component you have been investigating ?
was (Author: zhfeng):
[~gnodet], I get a list of extension from the camel-quarkus currently, which
the camel component has the doStart.
||Component||Status||Reason||
|camel-ahc|REJECT|create thread pool|
|camel-aws2-s3| | |
|camel-aws-ec2| | |
|camel-aws-ecs| | |
|camel-aws-eks| | |
|camel-aws-iam| | |
|camel-aws-kinesis| | |
|camel-aws-kms| | |
|camel-aws-lambda| | |
|camel-aws-s3| | |
|camel-aws-sdb| | |
|camel-aws-swf| | |
|camel-aws-translate| | |
|camel-bean|DONE| |
|camel-dataformat|DONE| |
|camel-dozer|DONE| |
|camel-file|DONE| |
|camel-infinispan|REJECT|start a server and create thread |
|camel-jira|REJECT|create the http client |
|camel-kubernetes| | |
|camel-kudu|REJECT|create thread pool|
|camel-log|DONE| |
|camel-mongodb|REJECT| resolve the MongClient from the camelContext and it
potentially open the connection and run the command |
|camel-netty-http|DONE| |
|camel-olingo4|REJECT|create the asyn http client |
|camel-platform-http|DONE| |
|camel-quartz|REJECT|quartz schedule create thread pool |
|camel-ref|REJECT|add the other endpoint uri |
|camel-salesforce|REJECT|create a http client and start it |
|camel-seda|DONE| |
|camel-sjms|REJECT|create connections pool |
|camel-sql|DONE| |
|camel-stream|DONE| |
|camel-telegram|REJECT|create thread pool |
|camel-timer|DONE| |
|camel-xslt|DONE| |
I'd like to take a look at these component at first and ignore what use the
XXXClient to open the network connection which I think should not be moved to
doInit(). I just wonder what component you have been investigating ?
> Component - Use doInit for wiring instead of doStart
> ----------------------------------------------------
>
> Key: CAMEL-14805
> URL: https://issues.apache.org/jira/browse/CAMEL-14805
> Project: Camel
> Issue Type: Improvement
> Reporter: Claus Ibsen
> Assignee: Zheng Feng
> Priority: Major
> Fix For: 3.4.0
>
>
> We should move logic from start to init for wiring and other similar things
> that can be setup as early as possible for lightweight camel.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
