[jira] [Comment Edited] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113209#comment-17113209 ] Zheng Feng edited comment on CAMEL-14805 at 6/2/20, 7:13 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|REJECT| | |camel-aws-ec2|REJECT| | |camel-aws-ecs|REJECT| | |camel-aws-eks|REJECT| | |camel-aws-iam|REJECT| | |camel-aws-kinesis|REJECT| | |camel-aws-kms|REJECT| | |camel-aws-lambda|REJECT| | |camel-aws-s3|REJECT| | |camel-aws-sdb|REJECT| | |camel-aws-swf|REJECT| | |camel-aws-translate|REJECT| | |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|REJECT| | |camel-aws-ec2|REJECT| | |camel-aws-ecs|REJECT| | |camel-aws-eks| |REJECT| |camel-aws-iam| |REJECT| |camel-aws-kinesis|REJECT| | |camel-aws-kms|REJECT| | |camel-aws-lambda|REJECT| | |camel-aws-s3|REJECT| | |camel-aws-sdb|REJECT| | |camel-aws-swf|REJECT| | |camel-aws-translate|REJECT| | |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 ? > 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)
[jira] [Comment Edited] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113209#comment-17113209 ] Zheng Feng edited comment on CAMEL-14805 at 6/2/20, 7:13 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|REJECT| | |camel-aws-ec2|REJECT| | |camel-aws-ecs|REJECT| | |camel-aws-eks| |REJECT| |camel-aws-iam| |REJECT| |camel-aws-kinesis|REJECT| | |camel-aws-kms|REJECT| | |camel-aws-lambda|REJECT| | |camel-aws-s3|REJECT| | |camel-aws-sdb|REJECT| | |camel-aws-swf|REJECT| | |camel-aws-translate|REJECT| | |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|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 ? > 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)
[jira] [Comment Edited] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Comment Edited] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113209#comment-17113209 ] Zheng Feng edited comment on CAMEL-14805 at 5/29/20, 8:03 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| | | |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| | | |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)
[jira] [Comment Edited] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113209#comment-17113209 ] Zheng Feng edited comment on CAMEL-14805 at 5/29/20, 8: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| | | |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| | | |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| | | |camel-jira| | | |camel-kubernetes| | | |camel-kudu|REJECT|create thread pool| |camel-log|DONE| | |camel-mongodb| | | |camel-netty-http|DONE| | |camel-olingo4| | | |camel-platform-http|DONE| | |camel-quartz|REJECT|quartz schedule create thread pool | |camel-ref|REJECT|add the other endpoint uri | |camel-salesforce| | | |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)
[jira] [Comment Edited] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113209#comment-17113209 ] Zheng Feng edited comment on CAMEL-14805 at 5/28/20, 8:07 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| | | |camel-jira| | | |camel-kubernetes| | | |camel-kudu|REJECT|create thread pool| |camel-log|DONE| | |camel-mongodb| | | |camel-netty-http|DONE| | |camel-olingo4| | | |camel-platform-http|DONE| | |camel-quartz|REJECT|quartz schedule create thread pool | |camel-ref|REJECT|add the other endpoint uri | |camel-salesforce| | | |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| | | |camel-jira| | | |camel-kubernetes| | | |camel-kudu|REJECT|create thread pool| |camel-log|DONE| | |camel-mongodb| | | |camel-netty-http| | | |camel-olingo4| | | |camel-platform-http|DONE| | |camel-quartz|REJECT|quartz schedule create thread pool | |camel-ref|REJECT|add the other endpoint uri | |camel-salesforce| | | |camel-seda| | | |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)
[jira] [Comment Edited] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113209#comment-17113209 ] Zheng Feng edited comment on CAMEL-14805 at 5/28/20, 7:59 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| | | |camel-jira| | | |camel-kubernetes| | | |camel-kudu|REJECT|create thread pool| |camel-log|DONE| | |camel-mongodb| | | |camel-netty-http| | | |camel-olingo4| | | |camel-platform-http|DONE| | |camel-quartz|REJECT|quartz schedule create thread pool | |camel-ref|REJECT|add the other endpoint uri | |camel-salesforce| | | |camel-seda| | | |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| | | |camel-jira| | | |camel-kubernetes| | | |camel-kudu|REJECT|create thread pool| |camel-log|DONE| | |camel-mongodb| | | |camel-netty-http| | | |camel-olingo4| | | |camel-platform-http| | | |camel-quartz| | | |camel-ref|REJECT|add the other endpoint uri | |camel-salesforce| | | |camel-seda| | | |camel-sjms| | | |camel-sql|DONE| | |camel-stream|DONE| | |camel-telegram| | | |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)
[jira] [Comment Edited] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113209#comment-17113209 ] Zheng Feng edited comment on CAMEL-14805 at 5/28/20, 7:30 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| | | |camel-jira| | | |camel-kubernetes| | | |camel-kudu|REJECT|create thread pool| |camel-log|DONE| | |camel-mongodb| | | |camel-netty-http| | | |camel-olingo4| | | |camel-platform-http| | | |camel-quartz| | | |camel-ref|REJECT|add the other endpoint uri | |camel-salesforce| | | |camel-seda| | | |camel-sjms| | | |camel-sql|DONE| | |camel-stream|DONE| | |camel-telegram| | | |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| | | |camel-jira| | | |camel-kubernetes| | | |camel-kudu|REJECT|create thread pool| |camel-log| | | |camel-mongodb| | | |camel-netty-http| | | |camel-olingo4| | | |camel-platform-http| | | |camel-quartz| | | |camel-ref|REJECT|add the other endpoint uri | |camel-salesforce| | | |camel-seda| | | |camel-sjms| | | |camel-sql|DONE| | |camel-stream|DONE| | |camel-telegram| | | |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)
[jira] [Comment Edited] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113209#comment-17113209 ] Zheng Feng edited comment on CAMEL-14805 at 5/27/20, 8:48 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| | | |camel-jira| | | |camel-kubernetes| | | |camel-kudu|REJECT|create thread pool| |camel-log| | | |camel-mongodb| | | |camel-netty-http| | | |camel-olingo4| | | |camel-platform-http| | | |camel-quartz| | | |camel-ref|REJECT|add the other endpoint uri | |camel-salesforce| | | |camel-seda| | | |camel-sjms| | | |camel-sql|DONE| | |camel-stream|DONE| | |camel-telegram| | | |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| | | |camel-jira| | | |camel-kubernetes| | | |camel-kudu|REJECT|create thread pool| |camel-log|| | |camel-mongodb| | | |camel-netty-http| | | |camel-olingo4| | | |camel-platform-http| | | |camel-quartz| | | |camel-ref|REJECT|add the other endpoint uri | |camel-salesforce| | | |camel-seda| | | |camel-sjms| | | |camel-sql|DONE| | |camel-stream|DONE| | |camel-telegram| | | |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)
[jira] [Comment Edited] (CAMEL-14805) Component - Use doInit for wiring instead of doStart
[ https://issues.apache.org/jira/browse/CAMEL-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113209#comment-17113209 ] Zheng Feng edited comment on CAMEL-14805 at 5/27/20, 8:48 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| | | |camel-jira| | | |camel-kubernetes| | | |camel-kudu|REJECT|create thread pool| |camel-log|| | |camel-mongodb| | | |camel-netty-http| | | |camel-olingo4| | | |camel-platform-http| | | |camel-quartz| | | |camel-ref|REJECT|add the other endpoint uri | |camel-salesforce| | | |camel-seda| | | |camel-sjms| | | |camel-sql|DONE| | |camel-stream|DONE| | |camel-telegram| | | |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. * camel-ahc * 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 * camel-dataformat * camel-dozer * camel-file * camel-infinispan * camel-jira * camel-kubernetes * camel-kudu * camel-log * camel-mongodb * camel-netty-http * camel-olingo4 * camel-platform-http * camel-quartz * camel-ref * camel-salesforce * camel-seda * camel-sjms * camel-sql * camel-stream * camel-telegram * camel-timer * camel-xslt 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)
