RE: Simple not working with Quarkus
Thanks a lot... It worked. I was having hunch that I am missing some dependency
but was not aware of which one.
Just a further thought... Since simple would almost always need
camel-quarkus-bean, I think we should either include it as dependency for core,
or remove simple out of core and along with simple have bean as dependency for
simple.
Thanks and Regards,
Hemang Ajmera
Vacation Alert: 26th Jan, 2022
-Original Message-
From: James Netherton
Sent: 27 January 2022 15:22
To: users@camel.apache.org
Subject: Re: Simple not working with Quarkus
EXTERNAL SENDER: Do not click any links or open any attachments unless you
trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce
jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez
l'assurance que le contenu provient d'une source sûre.
> Caused by: org.apache.camel.NoSuchLanguageException: No language could
> be
found for: bean
You need to add a dependency on camel-quarkus-bean.
--
James
On Thu, 27 Jan 2022 at 09:34, Ajmera, Hemang C
wrote:
> Hi
>.simple is not working with quarkus version 2.6.3 which uses camel
> version 3.14.0.
>
> I have included camel-quarkus-core in pom.xml.
>
> I am getting below error. Kindly let me know if I am missing anything.
>
> 2022-01-27 12:38:33,463 ERROR [io.qua.dep.dev.IsolatedDevModeMain]
> (Timer-0) Failed to start quarkus: java.lang.RuntimeException:
> java.lang.RuntimeException: Failed to start quarkus
> at
> io.quarkus.dev.appstate.ApplicationStateNotification.waitForApplicationStart(ApplicationStateNotification.java:51)
> at
> io.quarkus.runner.bootstrap.StartupActionImpl.runMainClass(StartupActionImpl.java:122)
> at io.quarkus.deployment.dev
> .IsolatedDevModeMain.restartApp(IsolatedDevModeMain.java:233)
> at io.quarkus.deployment.dev
> .IsolatedDevModeMain.restartCallback(IsolatedDevModeMain.java:214)
> at io.quarkus.deployment.dev
> .RuntimeUpdatesProcessor.doScan(RuntimeUpdatesProcessor.java:516)
> at io.quarkus.deployment.dev
> .RuntimeUpdatesProcessor.doScan(RuntimeUpdatesProcessor.java:417)
> at
> org.apache.camel.quarkus.core.devmode.CamelHotReplacementSetup$1.run(CamelHotReplacementSetup.java:36)
> at java.base/java.util.TimerThread.mainLoop(Timer.java:566)
> at java.base/java.util.TimerThread.run(Timer.java:516)
> Caused by: java.lang.RuntimeException: Failed to start quarkus
> at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)
> at io.quarkus.runtime.Application.start(Application.java:101)
> at
> io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:104)
> at io.quarkus.runtime.Quarkus.run(Quarkus.java:67)
> at io.quarkus.runtime.Quarkus.run(Quarkus.java:41)
> at io.quarkus.runtime.Quarkus.run(Quarkus.java:120)
> at io.quarkus.runner.GeneratedMain.main(Unknown Source)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> io.quarkus.runner.bootstrap.StartupActionImpl$1.run(StartupActionImpl.java:103)
> at java.base/java.lang.Thread.run(Thread.java:833)
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException:
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route4 at: >>>
> Choice[[When[simple{${exchangeProperty[CamelJdbcRowCount]>0}} ->
> [SetHeader[CamelHttpResponseCode, constant{204}],
> SetBody[org.apache.camel.builder.ExpressionClause@790a50e5
> Otherwise[[SetHeader[CamelHttpResponseCode,
> org.apache.camel.builder.ExpressionClause@139fa961],
> SetBody[org.apache.camel.builder.ExpressionClause@72b159dc <<< in
> route: Route(route4)[From[rest:put:/{service_id}/{key_data}] -> [Se...
> because of No language could be found for: bean
> at
> org.apache.camel.quarkus.core.CamelBootstrapRecorder.start(CamelBootstrapRecorder.java:47)
> at
> io.quarkus.deployment.steps.CamelBootstrapProcessor$boot173480958.depl
> oy_0(Unknown
> Source)
> at
> io.quarkus.deployment.steps.CamelBootstrapProcessor$boot173480958.depl
> oy(Unknown
> Source)
> ... 13 more
> Caused by: java.lang.RuntimeException:
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route4 at: >>>
> Choice[[When[simple{${e
Simple not working with Quarkus
ultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49) at org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:868) at org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:758) at org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2861) at org.apache.camel.quarkus.core.FastCamelContext.doInit(FastCamelContext.java:166) at org.apache.camel.support.service.BaseService.init(BaseService.java:83) at org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2567) at org.apache.camel.support.service.BaseService.start(BaseService.java:111) at org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2586) at org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:247) at org.apache.camel.quarkus.main.CamelMain.doStart(CamelMain.java:94) at org.apache.camel.support.service.BaseService.start(BaseService.java:119) at org.apache.camel.quarkus.main.CamelMain.startEngine(CamelMain.java:139) at org.apache.camel.quarkus.main.CamelMainRuntime.start(CamelMainRuntime.java:49) ... 16 more Caused by: org.apache.camel.language.simple.types.SimpleIllegalSyntaxException: No language could be found for: bean at org.apache.camel.language.simple.SimplePredicateParser.parsePredicate(SimplePredicateParser.java:82) at org.apache.camel.language.simple.SimpleLanguage.createPredicate(SimpleLanguage.java:142) at org.apache.camel.language.simple.SimpleLanguage.createPredicate(SimpleLanguage.java:158) at org.apache.camel.reifier.language.SimpleExpressionReifier.createPredicate(SimpleExpressionReifier.java:46) at org.apache.camel.reifier.language.ExpressionReifier.createPredicate(ExpressionReifier.java:232) at org.apache.camel.reifier.AbstractReifier.createPredicate(AbstractReifier.java:125) at org.apache.camel.reifier.ExpressionReifier.createPredicate(ExpressionReifier.java:48) at org.apache.camel.reifier.ExpressionReifier.createFilterProcessor(ExpressionReifier.java:39) at org.apache.camel.reifier.WhenReifier.createProcessor(WhenReifier.java:32) at org.apache.camel.reifier.WhenReifier.createProcessor(WhenReifier.java:24) at org.apache.camel.reifier.ProcessorReifier.createProcessor(ProcessorReifier.java:815) at org.apache.camel.reifier.ChoiceReifier.createProcessor(ChoiceReifier.java:68) at org.apache.camel.reifier.ProcessorReifier.makeProcessor(ProcessorReifier.java:838) at org.apache.camel.reifier.ProcessorReifier.addRoutes(ProcessorReifier.java:579) at org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:236) ... 31 more Caused by: org.apache.camel.NoSuchLanguageException: No language could be found for: bean at org.apache.camel.impl.engine.DefaultLanguageResolver.noSpecificLanguageFound(DefaultLanguageResolver.java:89) at org.apache.camel.impl.engine.DefaultLanguageResolver.resolveLanguage(DefaultLanguageResolver.java:63) at org.apache.camel.impl.engine.AbstractCamelContext$4.apply(AbstractCamelContext.java:1814) at org.apache.camel.impl.engine.AbstractCamelContext$4.apply(AbstractCamelContext.java:1797) at java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1708) at org.apache.camel.impl.engine.AbstractCamelContext.resolveLanguage(AbstractCamelContext.java:1797) at org.apache.camel.language.simple.SimpleExpressionBuilder$KeyedOgnlExpressionAdapter.init(SimpleExpressionBuilder.java:939) at org.apache.camel.language.simple.ast.SimpleFunctionExpression.createExpression(SimpleFunctionExpression.java:63) at org.apache.camel.language.simple.ast.SimpleFunctionStart.doCreateLiteralExpression(SimpleFunctionStart.java:74) at org.apache.camel.language.simple.ast.SimpleFunctionStart.createExpression(SimpleFunctionStart.java:64) at org.apache.camel.language.simple.SimplePredicateParser.createPredicates(SimplePredicateParser.java:554) at org.apache.camel.language.simple.SimplePredicateParser.doParsePredicate(SimplePredicateParser.java:154) at org.apache.camel.language.simple.SimplePredicateParser.parsePredicate(SimplePredicateParser.java:76) Thanks and Regards, Hemang Ajmera Hemang C Ajmera | Technical Architect Asia Pacific Communications, Media and Utilities Delivery Center | CGI Block 5, DLF-SEZ, Manapakkam, Chennai - 600089, India O: +91-44-6647-3828 | M: +91-89397-07557 | M: +91-98841-66619 | VOIP: 8083828 hemang.ajm...@cgi.com<mailto:hemang.ajm...@cgi.com> | www.cgi.com<http://www.cgi.com/>
RE: Converting ;< ;> to <> in camel
Hi You can use xpath to extract ciRequestXML. That should automatically have proper xml which can be parsed again. Thanks and Regards, Hemang Ajmera -Original Message- From: Wilken Marci J Sent: 03 December 2021 00:55 To: users@camel.apache.org Subject: Converting ;< ;> to <> in camel EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. Is there a transform or type converter that will convert escaped xml to standard xml I get this from a legacy axis 1.4 system R SelectClientPerpetratorInfo13887 I need to convert the ciRequestXML from personNo String 0 WL8AA7Q to personNo String 0 WL8AA7Q So that I can parse the xml (am using Jackson) into a POJO Without doing this .process(new Processor() { @SuppressWarnings("unchecked") public void process(Exchange exchange) throws Exception { //log.info(exchange.getIn().getHeader("RequestBeginDate").getClass().getName()); List params = (List) exchange.getIn().getBody(); String inboundRequest = ((String)params.get(2)).trim() .replaceAll("<","<") // fix anything that has been escaped .replaceAll(">",">") .replaceAll("<","<") // fix anything that has been escaped .replaceAll(">",">") ; log.info("Inbound Request: " + inboundRequest); exchange.getMessage().setBody(inboundRequest); }}) Regards- Marci Wilken She/Her/Hers Operations Architect Office of Information Services OHA/DHS/CAF-CW/OR-KIDS Desk: 503.378.2405 Cell: 503.979.9680 CONFIDENTIALITY NOTICE This email may contain information that is privileged, confidential, or otherwise exempt from disclosure under applicable law. If you are not the addressee or it appears from the context or otherwise that you have received this email in error, please advise me immediately by reply email, keep the contents confidential, and immediately delete the message and any attachments from your system. personNo String 0 WL8AA7Q
Dynamic route
Hi I have a use case where I need to have multiple subscriber to same kafka topic. Each subscriber would be identical with different parameters like consumer group name, and target url. However, the number of subscribers are not known in advance. What would be the best approach. Any pointers should be fine.
RE: Change of email for subscription
Hi I think this should be as simple as unsubscribe from this email and subscribe to another... Details to subscribe/unsubscribe are present at https://camel.apache.org/community/mailing-list/ Thanks and Regards, Hemang Ajmera -Original Message- From: SRIKANT MVS Sent: 21 November 2021 22:36 To: users@camel.apache.org Subject: Change of email for subscription EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. Hi Team, I would like to change my email address for subscribing to the camel user queries to mantha.srik...@outlook.com. Kindly do the needful. -Thanks Srikant Mantha
RE: Camel 3.4 documentation
Hi I also think it might be good to have documentation of previous LTS versions. Since we are not intending to make any changes in version 3.4.x, can we just not regenerate pages for version 3.4.x and use what we have already generated in antora. That means that https://camel.apache.org/components/3.4.x would just remain as it is, even if we update design/css etc. but still it would be very much helpful to the users who have not yet fully migrated to latest LTS versions. Thanks and Regards, Hemang Ajmera Vacation Alert: 13th Oct to 20th Oct -Original Message- From: Andrea Cosentino Sent: 28 September 2021 20:38 To: users@camel.apache.org Subject: Re: Camel 3.4 documentation EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. I think we could have troubles at building the website giving the work done on antora updates. That's why 3.4.x has been removed and also because there won't be new releases. Il mar 28 set 2021, 17:04 Jeremy Ross ha scritto: > I like this idea, but have no idea what's involved in making it happen. > > On Tue, Sep 28, 2021 at 8:06 AM Calle Andersson < > calleanders...@hotmail.com> > wrote: > > > Sure, it is possible to find the documentation in the source code > > but unfortunately it isn't as easy to browse the documentation there > > as it is on the documentation pages which I refered to. > > > > If it isn't to much troubles, is it possible to keep all LTS > > versions in the documentation pages for a longer time? After all, > > documentation for > 2.x > > is still available and it's not always possible to migrate to a > > never LTS version in the same pace as a LTS becomes obsolite (i.e. > > in about 1 > year). > > > > Regards, > > Calle > > > > > > > > > > Från: Claus Ibsen > > Skickat: tisdag 28 september 2021 13:58 > > Till: users@camel.apache.org > > Ämne: Re: Camel 3.4 documentation > > > > Hi > > > > You can find component docs in the source code, you can browse on > > github for the 3.4.x branch and look in src/main/docs for the > > components > > > > On Tue, Sep 28, 2021 at 1:41 PM Calle Andersson > > wrote: > > > > > > Hi, > > > > > > I just noticed the "3.4.x (LTS)" option has been removed from the > > > Camel > > Components documentation pages > > (https://urldefense.com/v3/__https://camel.apache.org/components/__;!!AaIhyw!_YdIcPReSO17gNecUNkRPmmZyQQ_2py1lJ55EZ3g6RzUSEKaIvbE_fqDOzufS-OC$ > > ). > Is > > there an alternative location where I can find the 3.4.x documentation? > > > > > > (I currently use Wildfly Camel ( > > https://urldefense.com/v3/__https://github.com/wildfly-extras/wildfl > > y-camel__;!!AaIhyw!_YdIcPReSO17gNecUNkRPmmZyQQ_2py1lJ55EZ3g6RzUSEKaI > > vbE_fqDO5c_CIGu$ ) but it still uses Camel > > 3.4 and it doesn't seem to get updated anytime soon.) > > > > > > Regards, > > > Calle > > > > > > > > -- > > Claus Ibsen > > - > > https://urldefense.com/v3/__http://davsclaus.com__;!!AaIhyw!_YdIcPRe > > SO17gNecUNkRPmmZyQQ_2py1lJ55EZ3g6RzUSEKaIvbE_fqDO_cV0XPD$ > > @davsclaus Camel in Action 2: > > https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!AaIhy > > w!_YdIcPReSO17gNecUNkRPmmZyQQ_2py1lJ55EZ3g6RzUSEKaIvbE_fqDO8DBF5RW$ > > > > >
RE: Springboot creating new Kakfa components
Hi
Earlier, I was about to update the kafka component manually after it was
initialized by springboot. Now that is not happening. Springboot is updating
kafka component after my updates. As a workaround I am not using kafka
springboot boot and only using plain camel kafka component.
But the question still remains, how to update springboot component using our
custom code before starting camel routes.
Thanks and Regards,
Hemang Ajmera
-Original Message-
From: Mark Nuttall
Sent: 16 July 2021 20:08
To: users@camel.apache.org
Subject: Re: Springboot creating new Kakfa components
EXTERNAL SENDER: Do not click any links or open any attachments unless you
trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce
jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez
l'assurance que le contenu provient d'une source sûre.
Fyi, using Spring Boot and/or Camel, you can and should specify kafka
properties in property / yaml files. You dont need to create a Kafka Component.
Spring/Camel will do that for you. That is what they do. That way it will be
configured correctly.
https://urldefense.com/v3/__https://docs.spring.io/spring-boot/docs/current/reference/html/application-properties.html*application-properties.integration__;Iw!!AaIhyw!8qQFRYs8bIDrDZgwoMSFfS39IinvKmF7nHY6RJqTjM1Q43bmugjiG2DOFIoCNire$
https://urldefense.com/v3/__https://camel.apache.org/camel-spring-boot/3.7.x/kafka-starter.html__;!!AaIhyw!8qQFRYs8bIDrDZgwoMSFfS39IinvKmF7nHY6RJqTjM1Q43bmugjiG2DOFERkYOX3$
On Thu, Jul 15, 2021 at 11:10 AM Ajmera, Hemang C
wrote:
> Hi
>
>I am configuring kafka component using some default values
> configured via springboot configurations. This code works fine for
> camel 3.4.5, however it is not working with camel 3.11.0. I checked
> the migration documents, but didn’t find anything significant. When I
> check the output, kakfa is configured with default values and not with what I
> am providing.
> Here is the code which is used for configuration kafka component
>
>
>
> @Configuration
>
> @EnableConfigurationProperties(KafkaComponentProperties.class)
>
> public class KafkaComponentFactory {
>
>
>
> @Autowired(required = false)
>
> KafkaComponentProperties kafkaProp;
>
>
>
> @Bean("kafka")
>
> public KafkaComponent createKafkaComponent() throws KafkaException
> {
>
>
>
> KafkaComponent kafka = new KafkaComponent();
>
> KafkaConfiguration kafkaConfiguration = new
> KafkaConfiguration();
>
>
>
>
> kafkaConfiguration.setSaslMechanism(kafkaProp.getSaslMechanism());
>
>
>
> kafkaConfiguration.setSecurityProtocol(kafkaProp.getSecurityProtocol()
> );
>
> kafkaConfiguration.setGroupId(kafkaProp.getGroupId());
>
> kafkaConfiguration.setBrokers(kafkaProp.getBrokers());
>
>
> kafkaConfiguration.setSslTruststorePassword(kafkaProp.getSslTruststore
> Password());
>
>
> kafkaConfiguration.setSslKeystorePassword(kafkaProp.getSslKeystorePass
> word());
>
>
> kafkaConfiguration.setSslTruststoreLocation(kafkaProp.getSslTruststore
> Location());
>
>
> kafkaConfiguration.setSslKeystoreLocation(kafkaProp.getSslKeystoreLoca
> tion());
>
>
> kafkaConfiguration.setAutoCommitEnable(kafkaProp.getAutoCommitEnable()
> );
>
>
> kafkaConfiguration.setAllowManualCommit(kafkaProp.getAllowManualCommit
> ());
>
>
> kafkaConfiguration.setSslEndpointAlgorithm(kafkaProp.getSslEndpointAlg
> orithm());
>
>
>
> kafka.setConfiguration(kafkaConfiguration);
>
>
>
> System.setProperty("java.security.auth.login.config",
> kafkaProp.getKafkaClientConfigFilePath());
>
>
>
> return kafka;
>
>
>
> }
>
>
>
>
>
>
>
> Thanks and Regards,
>
> Hemang Ajmera
>
>
>
> *Hemang C Ajmera* | Technical Architect
>
> Asia Pacific Communications, Media and Utilities Delivery Center | CGI
>
> Block 5, DLF-SEZ, Manapakkam, Chennai – 600089, India
> O: +91-44-6647-3828 | M: +91-89397-07557 | M: +91-98841-66619 | VOIP:
> 8083828
>
> hemang.ajm...@cgi.com | http://www.cgi.com
>
> [image: Description: Description: Description: Description: Description:
> Description: Description:
> C:\Users\rahul.muthalali\AppData\Local\Microsoft\Windows\Temporary
> Internet Files\Content.Word\Top_Employer_India_English_2016.gif]
>
>
>
RE: Springboot creating new Kakfa components
Hi
I did further investigation and noticed that only below five fields are
switching values before kafka endpoint is created.
Here is the new values in KafkaConfiguration which it uses
allowManualCommit -> false
sslEndpointAlgorithm -> "https"
securityProtocol -> "PLAINTEXT"
saslMechanism -> GSSAPI"
kerberosPrincipalToLocalRules -> "DEFAULT"
This looks like a bug somewhere in code.
Thanks and Regards,
Hemang Ajmera
From: Ajmera, Hemang C
Sent: 15 July 2021 20:40
To: users@camel.apache.org
Subject: Springboot creating new Kakfa components
EXTERNAL SENDER: Do not click any links or open any attachments unless you
trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n'ouvrez aucune pièce jointe à
moins qu'ils ne proviennent d'un expéditeur fiable, ou que vous ayez
l'assurance que le contenu provient d'une source sûre.
Hi
I am configuring kafka component using some default values configured via
springboot configurations. This code works fine for camel 3.4.5, however it is
not working with camel 3.11.0. I checked the migration documents, but didn't
find anything significant. When I check the output, kakfa is configured with
default values and not with what I am providing. Here is the code which is used
for configuration kafka component
@Configuration
@EnableConfigurationProperties(KafkaComponentProperties.class)
public class KafkaComponentFactory {
@Autowired(required = false)
KafkaComponentProperties kafkaProp;
@Bean("kafka")
public KafkaComponent createKafkaComponent() throws KafkaException {
KafkaComponent kafka = new KafkaComponent();
KafkaConfiguration kafkaConfiguration = new KafkaConfiguration();
kafkaConfiguration.setSaslMechanism(kafkaProp.getSaslMechanism());
kafkaConfiguration.setSecurityProtocol(kafkaProp.getSecurityProtocol());
kafkaConfiguration.setGroupId(kafkaProp.getGroupId());
kafkaConfiguration.setBrokers(kafkaProp.getBrokers());
kafkaConfiguration.setSslTruststorePassword(kafkaProp.getSslTruststorePassword());
kafkaConfiguration.setSslKeystorePassword(kafkaProp.getSslKeystorePassword());
kafkaConfiguration.setSslTruststoreLocation(kafkaProp.getSslTruststoreLocation());
kafkaConfiguration.setSslKeystoreLocation(kafkaProp.getSslKeystoreLocation());
kafkaConfiguration.setAutoCommitEnable(kafkaProp.getAutoCommitEnable());
kafkaConfiguration.setAllowManualCommit(kafkaProp.getAllowManualCommit());
kafkaConfiguration.setSslEndpointAlgorithm(kafkaProp.getSslEndpointAlgorithm());
kafka.setConfiguration(kafkaConfiguration);
System.setProperty("java.security.auth.login.config",
kafkaProp.getKafkaClientConfigFilePath());
return kafka;
}
Thanks and Regards,
Hemang Ajmera
Hemang C Ajmera | Technical Architect
Asia Pacific Communications, Media and Utilities Delivery Center | CGI
Block 5, DLF-SEZ, Manapakkam, Chennai - 600089, India
O: +91-44-6647-3828 | M: +91-89397-07557 | M: +91-98841-66619 | VOIP: 8083828
hemang.ajm...@cgi.com<mailto:hemang.ajm...@cgi.com> |
www.cgi.com<http://www.cgi.com/>
[Description: Description: Description: Description: Description: Description:
Description: C:\Users\rahul.muthalali\AppData\Local\Microsoft\Windows\Temporary
Internet Files\Content.Word\Top_Employer_India_English_2016.gif]
Springboot creating new Kakfa components
Hi
I am configuring kafka component using some default values configured via
springboot configurations. This code works fine for camel 3.4.5, however it is
not working with camel 3.11.0. I checked the migration documents, but didn't
find anything significant. When I check the output, kakfa is configured with
default values and not with what I am providing. Here is the code which is used
for configuration kafka component
@Configuration
@EnableConfigurationProperties(KafkaComponentProperties.class)
public class KafkaComponentFactory {
@Autowired(required = false)
KafkaComponentProperties kafkaProp;
@Bean("kafka")
public KafkaComponent createKafkaComponent() throws KafkaException {
KafkaComponent kafka = new KafkaComponent();
KafkaConfiguration kafkaConfiguration = new KafkaConfiguration();
kafkaConfiguration.setSaslMechanism(kafkaProp.getSaslMechanism());
kafkaConfiguration.setSecurityProtocol(kafkaProp.getSecurityProtocol());
kafkaConfiguration.setGroupId(kafkaProp.getGroupId());
kafkaConfiguration.setBrokers(kafkaProp.getBrokers());
kafkaConfiguration.setSslTruststorePassword(kafkaProp.getSslTruststorePassword());
kafkaConfiguration.setSslKeystorePassword(kafkaProp.getSslKeystorePassword());
kafkaConfiguration.setSslTruststoreLocation(kafkaProp.getSslTruststoreLocation());
kafkaConfiguration.setSslKeystoreLocation(kafkaProp.getSslKeystoreLocation());
kafkaConfiguration.setAutoCommitEnable(kafkaProp.getAutoCommitEnable());
kafkaConfiguration.setAllowManualCommit(kafkaProp.getAllowManualCommit());
kafkaConfiguration.setSslEndpointAlgorithm(kafkaProp.getSslEndpointAlgorithm());
kafka.setConfiguration(kafkaConfiguration);
System.setProperty("java.security.auth.login.config",
kafkaProp.getKafkaClientConfigFilePath());
return kafka;
}
Thanks and Regards,
Hemang Ajmera
Hemang C Ajmera | Technical Architect
Asia Pacific Communications, Media and Utilities Delivery Center | CGI
Block 5, DLF-SEZ, Manapakkam, Chennai - 600089, India
O: +91-44-6647-3828 | M: +91-89397-07557 | M: +91-98841-66619 | VOIP: 8083828
hemang.ajm...@cgi.com<mailto:hemang.ajm...@cgi.com> |
www.cgi.com<http://www.cgi.com/>
[Description: Description: Description: Description: Description: Description:
Description: C:\Users\rahul.muthalali\AppData\Local\Microsoft\Windows\Temporary
Internet Files\Content.Word\Top_Employer_India_English_2016.gif]
RE: salesforce connection with camel
Hi
I think since proxy is on port 80, mostly it is not secured. You need to use
false for secure.
Thanks and Regards,
Hemang Ajmera
-Original Message-
From: WEIQUAN YUAN
Sent: 09 April 2021 23:41
To: users@camel.apache.org
Subject: Re: salesforce connection with camel
EXTERNAL SENDER: Do not click any links or open any attachments unless you
trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce
jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez
l'assurance que le contenu provient d'une source sûre.
WEIQUAN YUAN14:10
Yes, I added configration here
camel.component.salesforce.http-proxy-host=cdhwg01.prod.prv
camel.component.salesforce.http-proxy-port=80
camel.component.salesforce.http-proxy-secure = true but it gves me this error
Caused by: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext
connection?
at
sun.security.ssl.SSLEngineInputRecord.bytesInCompletePacket(SSLEngineInputRecord.java:146)
at
sun.security.ssl.SSLEngineInputRecord.bytesInCompletePacket(SSLEngineInputRecord.java:64)
at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:475)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:398)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:377)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:626)
at org.eclipse.jetty.io.ssl.SslConnection.unwrap(SslConnection.java:417)
at
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:705)
On Fri, Apr 9, 2021 at 1:00 PM Jeremy Ross wrote:
> You don't have to specify grant_type. Your authentication failed. If
> you're using password auth, make sure your password is actually
> password+API token.
>
> On Thu, Apr 8, 2021 at 10:49 AM WEIQUAN YUAN
> wrote:
>
> > It is proxy issue, now I moved application out of proxy env , the
> > problem fixed.
> > but I got another error
> >
> > how to set grant type in the camel salesforce configuration? I
> > didn't see that option for grant_type
> >
> > Caused by: org.apache.camel.component.salesforce.api.SalesforceException:
> > {errors:[{"errorCode":"invalid_grant","message":"Login error
> > code:[invalid_grant] description:[authentication
> > failure]"}],statusCode:400}
> >
> > On Wed, Apr 7, 2021 at 9:54 AM Ajmera, Hemang C
> >
> > wrote:
> >
> > > Hi
> > > For login-url please try using
> > > https://urldefense.com/v3/__https://login.salesforce.com__;!!AaIhy
> > > w!90D1GG5HePOz1cTEl9LRi5gFxuKsHbsm2-amafLiGAIE_pF8Tbyz6yqXwuC2w44N
> > > $ for production environment or
> > > https://urldefense.com/v3/__https://test.salesforce.com__;!!AaIhyw
> > > !90D1GG5HePOz1cTEl9LRi5gFxuKsHbsm2-amafLiGAIE_pF8Tbyz6yqXwjAp69Ky$
> > >
> > > No need to add anything extra for oauth... Salesforce component
> > > will
> take
> > > care of those.
> > >
> > > Thanks and Regards,
> > > Hemang Ajmera
> > >
> > >
> > > -Original Message-
> > > From: WEIQUAN YUAN
> > > Sent: 05 April 2021 23:54
> > > To: users@camel.apache.org
> > > Subject: salesforce connection with camel
> > >
> > >
> > > EXTERNAL SENDER: Do not click any links or open any attachments
> unless
> > > you trust the sender and know the content is safe.
> > > EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune
> pièce
> > > jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou
> > > que
> vous
> > > ayez l'assurance que le contenu provient d'une source sûre.
> > >
> > > Here is my properties
> > >
> > > camel.component.salesforce.client-secret=xxx
> > > camel.component.salesforce.client-id=xxx
> > > camel.component.salesforce.authentication-type=USERNAME_PASSWORD
> > > camel.component.salesforce.login-url=
> > >
> > >
> >
> https://urldefense.com/v3/__https://test.salesforce.com/services/oauth
> 2/token__;!!AaIhyw!_IOZlEZxP07kluK-vgfSr9h3SzufPQRZxVXryo4w5up9MTcN-P8
> FPmPd_iPVZ5cj$
> > > camel.component.salesforce.user-name=xxx
> > >
> > > and I run this route
> > >
> > > from("timer:tick")
> > > .setHeader("Sforce-Limit-Info", constant("api-usage"))
> > > .to("salesforce:getGlobalObjects")
> > > .process(exchange -> {
> > > Message in = exchange.getIn();
> > > String apiLimits = in.getHeader("Sforce-Limit-Info",
> > > String.class); Sys
RE: salesforce connection with camel
Hi
For login-url please try using https://login.salesforce.com for production
environment or https://test.salesforce.com
No need to add anything extra for oauth... Salesforce component will take care
of those.
Thanks and Regards,
Hemang Ajmera
-Original Message-
From: WEIQUAN YUAN
Sent: 05 April 2021 23:54
To: users@camel.apache.org
Subject: salesforce connection with camel
EXTERNAL SENDER: Do not click any links or open any attachments unless you
trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce
jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez
l'assurance que le contenu provient d'une source sûre.
Here is my properties
camel.component.salesforce.client-secret=xxx
camel.component.salesforce.client-id=xxx
camel.component.salesforce.authentication-type=USERNAME_PASSWORD
camel.component.salesforce.login-url=
https://urldefense.com/v3/__https://test.salesforce.com/services/oauth2/token__;!!AaIhyw!_IOZlEZxP07kluK-vgfSr9h3SzufPQRZxVXryo4w5up9MTcN-P8FPmPd_iPVZ5cj$
camel.component.salesforce.user-name=xxx
and I run this route
from("timer:tick")
.setHeader("Sforce-Limit-Info", constant("api-usage"))
.to("salesforce:getGlobalObjects")
.process(exchange -> {
Message in = exchange.getIn();
String apiLimits = in.getHeader("Sforce-Limit-Info", String.class);
System.out.print("sales force works ? " + apiLimits);
})
.end();
I think that installed all the certifcates I has below(loginURL, instanceURL),
but still got the error
"org.apache.camel.RuntimeCamelException:
org.apache.camel.component.salesforce.api.SalesforceException: Unexpected login
error: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target"
There is not proxy between camel application and SF.
then I injected those properties in URL as below to run in POSTman
https://urldefense.com/v3/__https://test.salesforce.com/services/oauth2/token?client_id=XXX&format=json&client_secret=XXX&grant_type=password&username=&password=XXX__;!!AaIhyw!_IOZlEZxP07kluK-vgfSr9h3SzufPQRZxVXryo4w5up9MTcN-P8FPmPd_jFwPZN3$
it successfully returns me access token, what is wrong with my local env?
how can I debug this issue?
--
~
Weiquan Yuan
Located in Ottawa, Canada
RE: Camel Java DSL Cheat
Hi This seems to be really useful. I think we should include this in camel documentation, so that it can be easily reference by anyone who is new to camel. Thanks and Regards, Hemang Ajmera -Original Message- From: ski n Sent: 11 January 2021 19:45 To: users@camel.apache.org Subject: Camel Java DSL Cheat EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. Hi All, For a project I created a lot of Camel routes. Sometimes I noticed that I need to look up how to do something. To look it up more quickly I created a cheat sheet for the Java DSL. Maybe also useful for others: https://urldefense.com/v3/__https://github.com/assimbly/camel-examples__;!!AaIhyw!4nwellmXk5yNYCygr4_WfufWZQxWS7zJPDitTEVxM6OD72BqL1LDAkz30H74Dker$ In case you miss something just make a PR. Kind regards, Raymond
RE: Salesforce streaming issue
Hi
Thanks I got the details. I may try it out tomorrow after ci/cd does the
build.
Thanks and Regards,
Hemang Ajmera
-Original Message-
From: Claus Ibsen
Sent: 18 December 2020 18:50
To: users@camel.apache.org
Cc: Jean-Baptiste Onofre ; Dev ; Andy
Stebbing
Subject: Re: Salesforce streaming issue
EXTERNAL SENDER: Do not click any links or open any attachments unless you
trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce
jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez
l'assurance que le contenu provient d'une source sûre.
There are standard apache snapshot maven repos, you can find details from ASF
website.
But mind that it takes overnight for CI server to build and publish to it - so
its often quicker to build yourself.
On Fri, Dec 18, 2020 at 2:18 PM Ajmera, Hemang C wrote:
>
> Hi
>Can you please share maven repo setting using which I can directly use
> snapshot version of compiled jar file. I found compiling camel was a big task
> which I want to avoid. I will also give it a try. If possible springboot
> camel-salesforce-starter will be preferred, then I can try running the
> production code directly with snapshot version in lower environment.
>
>
> Thanks and Regards,
> Hemang Ajmera
>
>
> -Original Message-
> From: Jean-Baptiste Onofre
> Sent: 18 December 2020 18:24
> To: Dev
> Cc: users@camel.apache.org; Andy Stebbing ;
> Ajmera, Hemang C
> Subject: Re: Salesforce streaming issue
>
>
> EXTERNAL SENDER: Do not click any links or open any attachments unless you
> trust the sender and know the content is safe.
> EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce
> jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez
> l'assurance que le contenu provient d'une source sûre.
>
> Thanks for the update Zoran.
>
> I gonna take a look and test.
>
> Regards
> JB
>
> > Le 18 déc. 2020 à 13:12, Zoran Regvart a écrit :
> >
> > Hi Cameleers,
> > this has been targeted for releases 3.7.1 and 3.8.0, if you can, it
> > would be of great help to test this before we release.
> >
> > zoran
> >
> > On Wed, Dec 16, 2020 at 3:44 PM Zoran Regvart wrote:
> >>
> >> Hi Cameleers,
> >> I've created a PR[1], which I think fixes the problem, I encourage
> >> folk to provide feedback and test on your end if possible.
> >>
> >> I've tested with the `SubscriptionHelperIntegrationTest`. And manually by:
> >>
> >> 1/ Starting a streaming app with the route:
> >>
> >> from("salesforce:Account?sObjectName=Account&rawPayload=true&sObjec
> >> tQ
> >> uery=SELECT
> >> Id, Name FROM Account")¬
> >> .log(LoggingLevel.INFO, "salesforce", "${body}")
> >>
> >> 2/ creating an Account record, and noticing the output in the
> >> log/console from the `log` component
> >>
> >> 3/ rejecting traffic to Salesforce using iptables:
> >> $ iptables -A OUTPUT -d 85.222.0.0/16 -j REJECT
> >>
> >> 4/ disrupting the established connection using ss:
> >> $ ss -K dst 85.222.154.145 # or whatever IP was in the output of
> >> lsof -p $PID -a -i 6 -n
> >>
> >> 5/ noticing the messages in the log with back-off like:
> >>
> >> Connect failure: {failure={exception=java.io.EOFException:
> >> HttpConnectionOverHTTP@45d7880c::DecryptedEndPoint@621bd87d{l=/192.168.1.76:43432,r=eu18.salesforce.com/85.222.155.145:443...
> >> Restarting on unexpected disconnect from Salesforce...
> >> Handshake failure: {failure={exception=java.net.ConnectException:
> >> Connection refused, message={...
> >> Handshake failure: {failure={exception=java.net.ConnectException:
> >> Connection refused, message={...
> >>
> >> 5/ allowing traffic to Salesforce (removing the rule):
> >> $ iptables -D OUTPUT 4 # happens to be 4th rule that I've added in
> >> 3/, check with iptables -L OUTPUT --line-numbers
> >>
> >> 6/ seeing consumer reconnecting:
> >>
> >> Set Replay extension to replay from `-1` for channel
> >> `/topic/Account` Subscribing to channel /topic/Account...
> >> Successfully restarted!
> >> Subscribed to channel /topic/Account
> >>
> >> 7/ creating a new Account record, and seeing the message logged
> >> from the `log` component.
> >>
> >> zoran
> >>
> >> [1]
> >> https://urldefense.com/v3/__https://github.com/apache/camel/pull/47
> >> 78
> >> __;!!AaIhyw!_Vo0r3EhR2gpAnmiN1U-XwM3Z9ZaLIrFENHuHqbcLNhiY9FIm8ffp1i
> >> 8c
> >> EVEwBZG$
> >>
> >> --
> >> Zoran Regvart
> >
> >
> >
> > --
> > Zoran Regvart
>
--
Claus Ibsen
-
https://urldefense.com/v3/__http://davsclaus.com__;!!AaIhyw!5kJ7zs-QkcZ5_SZ9pvMUap5xAsp64UeZDINCVbIww8HcBME_pFACTMnc0mauqbia$
@davsclaus Camel in Action 2:
https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!AaIhyw!5kJ7zs-QkcZ5_SZ9pvMUap5xAsp64UeZDINCVbIww8HcBME_pFACTMnc0kghjrc4$
RE: Salesforce streaming issue
Hi
Can you please share maven repo setting using which I can directly use
snapshot version of compiled jar file. I found compiling camel was a big task
which I want to avoid. I will also give it a try. If possible springboot
camel-salesforce-starter will be preferred, then I can try running the
production code directly with snapshot version in lower environment.
Thanks and Regards,
Hemang Ajmera
-Original Message-
From: Jean-Baptiste Onofre
Sent: 18 December 2020 18:24
To: Dev
Cc: users@camel.apache.org; Andy Stebbing ; Ajmera,
Hemang C
Subject: Re: Salesforce streaming issue
EXTERNAL SENDER: Do not click any links or open any attachments unless you
trust the sender and know the content is safe.
EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce
jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez
l'assurance que le contenu provient d'une source sûre.
Thanks for the update Zoran.
I gonna take a look and test.
Regards
JB
> Le 18 déc. 2020 à 13:12, Zoran Regvart a écrit :
>
> Hi Cameleers,
> this has been targeted for releases 3.7.1 and 3.8.0, if you can, it
> would be of great help to test this before we release.
>
> zoran
>
> On Wed, Dec 16, 2020 at 3:44 PM Zoran Regvart wrote:
>>
>> Hi Cameleers,
>> I've created a PR[1], which I think fixes the problem, I encourage
>> folk to provide feedback and test on your end if possible.
>>
>> I've tested with the `SubscriptionHelperIntegrationTest`. And manually by:
>>
>> 1/ Starting a streaming app with the route:
>>
>> from("salesforce:Account?sObjectName=Account&rawPayload=true&sObjectQ
>> uery=SELECT
>> Id, Name FROM Account")¬
>> .log(LoggingLevel.INFO, "salesforce", "${body}")
>>
>> 2/ creating an Account record, and noticing the output in the
>> log/console from the `log` component
>>
>> 3/ rejecting traffic to Salesforce using iptables:
>> $ iptables -A OUTPUT -d 85.222.0.0/16 -j REJECT
>>
>> 4/ disrupting the established connection using ss:
>> $ ss -K dst 85.222.154.145 # or whatever IP was in the output of lsof
>> -p $PID -a -i 6 -n
>>
>> 5/ noticing the messages in the log with back-off like:
>>
>> Connect failure: {failure={exception=java.io.EOFException:
>> HttpConnectionOverHTTP@45d7880c::DecryptedEndPoint@621bd87d{l=/192.168.1.76:43432,r=eu18.salesforce.com/85.222.155.145:443...
>> Restarting on unexpected disconnect from Salesforce...
>> Handshake failure: {failure={exception=java.net.ConnectException:
>> Connection refused, message={...
>> Handshake failure: {failure={exception=java.net.ConnectException:
>> Connection refused, message={...
>>
>> 5/ allowing traffic to Salesforce (removing the rule):
>> $ iptables -D OUTPUT 4 # happens to be 4th rule that I've added in
>> 3/, check with iptables -L OUTPUT --line-numbers
>>
>> 6/ seeing consumer reconnecting:
>>
>> Set Replay extension to replay from `-1` for channel `/topic/Account`
>> Subscribing to channel /topic/Account...
>> Successfully restarted!
>> Subscribed to channel /topic/Account
>>
>> 7/ creating a new Account record, and seeing the message logged from
>> the `log` component.
>>
>> zoran
>>
>> [1]
>> https://urldefense.com/v3/__https://github.com/apache/camel/pull/4778
>> __;!!AaIhyw!_Vo0r3EhR2gpAnmiN1U-XwM3Z9ZaLIrFENHuHqbcLNhiY9FIm8ffp1i8c
>> EVEwBZG$
>>
>> --
>> Zoran Regvart
>
>
>
> --
> Zoran Regvart
RE: Apache Camel EOL Versions
Hi My understanding was that LTS version will be supported for 1 year. So even if 3.7 is release version 3.4 will be continued to be supported for bugs and security fixes. Did I misunderstood something? This is the reference https://camel.apache.org/blog/2020/03/LTS-Release-Schedule/ Thanks and Regards, Hemang Ajmera -Original Message- From: Zoran Regvart Sent: 15 December 2020 21:42 To: Symphoni Bush - NOAA Affiliate Cc: users@camel.apache.org Subject: Re: Apache Camel EOL Versions EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. Hi Symphoni, I wonder where you found the owner mail alias? Moving the conversation to the users mailing list. I'll try to answer to the best of my abilities, others may correct me. Answer differs slightly based on the major version (2.x or 3.x). For 2.x we supported the latest two releases. Since version 3.x we support the latest and last two LTS versions. Exception to that is when we released 3.0 we opted to support the latest 2.x release as well. All other versions should be considered EOL at the release of a newer version. This is with respect to what we're willing to do here at ASF. Organizations providing commercial support for Camel would most likely have their own definition of support and EOL dates. So the date a version is considered EOL is: 1/ for 2.x releases: when a new minor release was done, the second oldest minor release was considered EOL, for example 2.25.0 was released on 2020-01-23, making 2.23.x EOL from that date. 2/ for non-LTS 3.x: we consider non-LTS releases EOL as soon as a newer non-LTS is released, for example 3.6.0 was released on 2020-09-20 making 3.5.0 EOL on that date. 3/ for LTS 3.x: we support the last two LTS releases (currently 3.4 and soon 3.7), 3.4 will be EOL with the the LTS release done after 3.7 List of versions and release dates is available in the release archive on the website here: https://urldefense.com/v3/__https://camel.apache.org/releases/__;!!AaIhyw!8JFXRBAgcpSfw70r1k6EnsebuUKzZTTL_40k3z4yUhPywv-HIeEhZcvJ91E7908T$ It goes back only to 2.18 as that's where we stopped migrating old data to the new website. For older dates you need to either go to the mailing list archives or to the wiki[1] which was the source for the old website. You can find further information in the LTS schedule for 2020 blog post: https://urldefense.com/v3/__https://camel.apache.org/blog/2020/03/LTS-Release-Schedule/__;!!AaIhyw!8JFXRBAgcpSfw70r1k6EnsebuUKzZTTL_40k3z4yUhPywv-HIeEhZcvJ94ppx4Js$ zoran [1] https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/CAMEL/Download__;!!AaIhyw!8JFXRBAgcpSfw70r1k6EnsebuUKzZTTL_40k3z4yUhPywv-HIeEhZcvJ97YrWBkI$ On Tue, Dec 15, 2020 at 4:25 PM Symphoni Bush - NOAA Affiliate wrote: > > Good morning, > > I am trying to figure out what versions of Apache Camel are EOL and if so, > what dates these versions became EOL. If there is somewhere this information > is stored, please let me know. > > Thanks -- Zoran Regvart
RE: Are you using binary distribution?
I am relying on maven for binaries and git for sourcecode. IMHO binary distribution may not be needed. Github has release feature, where we can have binaries can be downloaded from there. Many users might be used to that way of downloading binary, so if needed, that can be alternate place for download if anyone needs it. However CI/CD pipeline might need updates for github release to work. Thanks and Regards, Hemang Ajmera -Original Message- From: Zoran Regvart Sent: 14 December 2020 19:08 To: Dev ; users@camel.apache.org Subject: Are you using binary distribution? EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. Hi Cameleers, we're discussing binary distribution on two issues[1][2]. The binary distribution is the tar.gz/ZIP file linked from the Camel website. By ASF policy we only ship source code, and the binary distribution is optional. Back in the dark days, before using build tools that knew about dependency management (Maven, Gradle...) folk used to use the binary distribution. I've found some statistics on downloads/per day, for us[3]/eu[4] and created these charts: https://urldefense.com/v3/__https://s.apache.org/camel-dl-us__;!!AaIhyw!8ibMqXkFVhQZbXiUiDEZIMhodvHt6ZT0-9hO37pz6vxmkpWyl1rF-cNDiSwKzT18$ https://urldefense.com/v3/__https://s.apache.org/camel-dl-eu__;!!AaIhyw!8ibMqXkFVhQZbXiUiDEZIMhodvHt6ZT0-9hO37pz6vxmkpWyl1rF-cNDic4MBCm6$ The data is over 2 and 1/4 years, we've had 19.7+-8.8 via US, and 20.24+-8.43 in via EU per day. So not that much IMHO. I'm wondering if anyone is still relying on these, and if so what would a binary distribution look like for sub projects? Should we do the same as we do for the Camel core? Please reply on this thread or chime in on those issues for sub-project specific concerns. Thanks :) zoran [1] https://urldefense.com/v3/__https://github.com/apache/camel-quarkus/issues/2045__;!!AaIhyw!8ibMqXkFVhQZbXiUiDEZIMhodvHt6ZT0-9hO37pz6vxmkpWyl1rF-cNDiZ80_jXD$ [2] https://urldefense.com/v3/__https://github.com/apache/camel-kafka-connector/issues/754__;!!AaIhyw!8ibMqXkFVhQZbXiUiDEZIMhodvHt6ZT0-9hO37pz6vxmkpWyl1rF-cNDiVlO1Pqs$ [3] https://urldefense.com/v3/__https://www-us.apache.org/dyn/stats/camel.log__;!!AaIhyw!8ibMqXkFVhQZbXiUiDEZIMhodvHt6ZT0-9hO37pz6vxmkpWyl1rF-cNDiStt2eyy$ [4] https://urldefense.com/v3/__https://www-eu.apache.org/dyn/stats/camel.log__;!!AaIhyw!8ibMqXkFVhQZbXiUiDEZIMhodvHt6ZT0-9hO37pz6vxmkpWyl1rF-cNDicRsFgPE$ -- Zoran Regvart
RE: Salesforce Platform Events Subscription Retries
Hi We are also facing the issue with 3.4.4 version of salesforce component. We are facing since version 2.3 and I am not able to reproduce it successfully all the time and couldn't find the issue for sure. As a workaround (which is not good, but works fine for us), we are restarting integration at regular interval using replay id as -2. Also we keep track of replay id, so if the replay id is already processed, we ignore it. Thanks and Regards, Hemang Ajmera -Original Message- From: Zoran Regvart Sent: 30 November 2020 14:59 To: users@camel.apache.org Subject: Re: Salesforce Platform Events Subscription Retries EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. Hi Andy, sounds like an issue we would not encounter when developing/running integration tests. We have a number of issues (some of them have been fixed) relating to streaming/push APIs with Salesforce. Perhaps if you find that the recent versions did not fix your issue you could contribute the logic of your custom error handler. Sounds like you've also arrived at a setup where you can reproduce and test the fix. I'm guessing it could fit within the SubscriptionHelper class. zoran On Fri, Nov 27, 2020 at 4:14 AM Andy Stebbing wrote: > > Hi There, > I'm using the salesforce component for receiving platform events and > have been using it for a few months and is generally quite stable. > > My question is around the durability of the subscription, for normal > network dropouts or timeouts etc, it handles it very well, but > recently Salesforce have had some big outages in my org and it causes > the subscription to stop working without re-subscribing again. > > I can replicate the issue locally, running my camel route so it > initially subscribes to the events then I firewall block the > Salesforce destination then i restart the route. It fails and then > unsubscribes from the events and when i open the firewall it connects > but never re-subscribes to the events again. Any new events from > Salesforce are not consumed and the service remains offline. > > I've bridged the error handler to one I've defined within the same > camel context so that I could detect the salesforce exception when it > happens and then to use the control bus to restart the route which > then does the subscription. But seems like an overkill, especially if > this is a bug that might end up being fixed. > > Has anyone else experienced this? Are there any solutions to get around this? > > Many thanks! -- Zoran Regvart
RE: Redesigning the Camel website front page
Hi It is excellent! Just few suggestion 1. For mobile view, if we do not display the large logo for each sections, it will be more helpful in small screen. 2. Do we need a "Download" in main menu? I guess that might not be very useful, since mostly maven/gradle is used. Also in my case, I use with springboot, so jar with springboot starter is what is used as beginning point. Other thought was, that in the download page, we can add the maven/gradle dependency details. That way it might be easy to directly use that. Thanks and Regards, Hemang Ajmera -Original Message- From: Zoran Regvart Sent: 31 July 2020 22:24 To: Dev ; users@camel.apache.org Cc: Aashna Jena ; Aemie Hitesh Jariwala ; Maria Arias de Reyna Dominguez Subject: Redesigning the Camel website front page EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE:Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. Hi Cameleers, in the past few months we had a lot of help with the Camel website from two interns from the Outreachy program. We're now at a point where we're redesigning the website front page and we would like to hear some feedback from you. Take a look at the preview: https://deploy-preview-442--camel.netlify.app/ And if you wish to provide some feedback chime in on the pull request: https://github.com/apache/camel-website/pull/442 thanks! zoran -- Zoran Regvart
RE: [presentation] Apache Camel 3 talk by Claus Ibsen and Andrea Cosentino
Thanks for quick response! Thanks and Regards, Hemang Ajmera -Original Message- From: Claus Ibsen Sent: 30 July 2020 14:06 To: users@camel.apache.org Subject: Re: [presentation] Apache Camel 3 talk by Claus Ibsen and Andrea Cosentino Hi Its posted both on youtube at https://www.youtube.com/watch?v=m4ZqGukr2CU And on the streaming platform where you can see the chat, questions, and polls, etc https://www.crowdcast.io/e/camel-3--integration-in/1 On Thu, Jul 30, 2020 at 9:47 AM Ajmera, Hemang C wrote: > > Hi > > Can we get recording of the sessions, I could not find this. > > > Thanks and Regards, > Hemang Ajmera > > > -Original Message- > From: Claus Ibsen > Sent: 27 July 2020 20:15 > To: users@camel.apache.org > Subject: Re: [presentation] Apache Camel 3 talk by Claus Ibsen and > Andrea Cosentino > > Hi > > Thanks Jonathan for having us at the event. > > I posted a bit about this talk on my social media to help spread the word. > > On Mon, Jul 27, 2020 at 3:42 PM Jonathan Vila Lopez > wrote: > > > > Hi > > I would like to share with all the Apache Camel followers, that > > tomorrow afternoon ( CEST ) the BarcelonaJUG will have a > > presentation about the recently released Apache Camel 3, the > > integration platform in the era of Kubernetes and Serverles.. > > It's a free and online event , in English, tomorrow Tuesday 28th at > > 19.00 CEST > > https://www.meetup.com/es-ES/BarcelonaJUG/events/271746564/ > > > > Hope to see you there. > > > > Happy coding. > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
RE: [presentation] Apache Camel 3 talk by Claus Ibsen and Andrea Cosentino
Hi Can we get recording of the sessions, I could not find this. Thanks and Regards, Hemang Ajmera -Original Message- From: Claus Ibsen Sent: 27 July 2020 20:15 To: users@camel.apache.org Subject: Re: [presentation] Apache Camel 3 talk by Claus Ibsen and Andrea Cosentino Hi Thanks Jonathan for having us at the event. I posted a bit about this talk on my social media to help spread the word. On Mon, Jul 27, 2020 at 3:42 PM Jonathan Vila Lopez wrote: > > Hi > I would like to share with all the Apache Camel followers, that > tomorrow afternoon ( CEST ) the BarcelonaJUG will have a presentation > about the recently released Apache Camel 3, the integration platform > in the era of Kubernetes and Serverles.. > It's a free and online event , in English, tomorrow Tuesday 28th at > 19.00 CEST https://www.meetup.com/es-ES/BarcelonaJUG/events/271746564/ > > Hope to see you there. > > Happy coding. -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
RE: Camel website: documentation or projects
Hi Earlier in UI the mouse over on menu would should be direct link for Components documents Now mouse over is not working. May be we can enable that once we migrate to one page... That will help in quick navigation. Thanks and Regards, Hemang Ajmera -Original Message- From: Jean-Baptiste Onofre Sent: 18 June 2020 12:23 To: users@camel.apache.org Cc: Dev Subject: Re: Camel website: documentation or projects I agree with Andrea. Single page and links to docs make sense. Regards JB > Le 18 juin 2020 à 08:51, Andrea Cosentino a écrit : > > I'd say this should be under Documentation and I'd expect to find > description of projects and links to docs, I guess. > > One page it's for sure more clear than two. > > Thanks for your time on this :-) > > Il giorno mer 17 giu 2020 alle ore 23:05 Zoran Regvart > ha scritto: > >> Hi Cameleers, >> we have a discussion on pull request #397[1] about merging the >> Documentation and Projects sections on the website. This came about >> from a fair bit of duplication we currently have between those two >> pages and we're trying to consolidate and simplify. >> >> We're looking for community feedback on this: >> - would you expect this unified page to be under "Projects" or under >> "Documentation"? >> - what do you expect to find on this page (description, links, etc?) >> >> thanks :) >> >> zoran >> >> [1] https://github.com/apache/camel-website/pull/397 >> -- >> Zoran Regvart >>
Error handling when all redeliveries are exhausted
Hi I tried searching documents are also "Camel in Action - 2" to find how do I put the custom logic when all redelivery attempts are exhausted in error handler. Any pointer here will be helpful. Thanks and Regards, Hemang Ajmera Hemang C Ajmera | Technical Architect Asia Pacific Communications, Media and Utilities Delivery Center | CGI Block 5, DLF-SEZ, Manapakkam, Chennai - 600089, India O: +91-44-6647-3828 | M: +91-89397-07557 | M: +91-98841-66619 | VOIP: 8083828 hemang.ajm...@cgi.com<mailto:hemang.ajm...@cgi.com> | www.cgi.com<http://www.cgi.com/> [Description: Description: Description: Description: Description: Description: Description: C:\Users\rahul.muthalali\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.Word\Top_Employer_India_English_2016.gif]
RE: Salesforce not working with camel 3.2
Hi Thanks for confirming the issue and creating Jira ticket. It is marked as New Feature in Jira. Shouldn’t this be a bug? Thanks and Regards, Hemang Ajmera -Original Message- From: Jean-Baptiste Onofre Sent: 17 April 2020 17:07 To: users@camel.apache.org Subject: Re: Salesforce not working with camel 3.2 Hi, Yes, I also identified the same issue: it works with Camel 3.0.1 and 3.1.0 but not in 3.2.0. I created https://issues.apache.org/jira/browse/CAMEL-14927 <https://issues.apache.org/jira/browse/CAMEL-14927> to fix it as I’m also impacted. Regards JB > Le 17 avr. 2020 à 12:26, Ajmera, Hemang C a écrit : > > Hi >I am try to use salesforce component, but getting null point exception > with camel 3.2. The code is working fine with camel 3.1. > > I did little debugging and found that in SalesforceComponent at line 260, > “config.setHttpClient(httpClient);” HttpClient is set to null and later in > the code httpClient is initialized at line on line 328. > > So eventually salesforceComponent.config.httpClient is null and which is why > we are getting null point exception. > > Here is the detailed error message > > > . ___ _ _ > /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ > _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) > ' || .__|_| |_|_| |_\__, | / / / / > =|_|==|___/=/_/_/_/ > :: Spring Boot ::(v2.2.6.RELEASE) > > 2020-04-17 15:39:44.832 INFO 18872 --- [ main] > c.t.electron.fi.IntegrationApplication : No active profile set, falling > back to default profiles: default > 2020-04-17 15:39:45.692 INFO 18872 --- [ main] > trationDelegate$BeanPostProcessorChecker : Bean > 'org.apache.camel.spring.boot.CamelAutoConfiguration' of type > [org.apache.camel.spring.boot.CamelAutoConfiguration] is not eligible for > getting processed by all BeanPostProcessors (for example: not eligible for > auto-proxying) > 2020-04-17 15:39:45.923 INFO 18872 --- [ main] > o.apache.camel.support.LRUCacheFactory : Detected and using > LURCacheFactory: camel-caffeine-lrucache > 2020-04-17 15:39:46.436 INFO 18872 --- [ main] > o.a.c.s.boot.SpringBootRoutesCollector : Loading additional Camel XML > routes from: classpath:camel/*.xml > 2020-04-17 15:39:46.437 INFO 18872 --- [ main] > o.a.c.s.boot.SpringBootRoutesCollector : Loading additional Camel XML rests > from: classpath:camel-rest/*.xml > 2020-04-17 15:39:46.469 INFO 18872 --- [ main] > o.a.c.i.e.DefaultManagementStrategy : JMX is enabled > 2020-04-17 15:39:46.973 INFO 18872 --- [ main] > o.a.camel.component.http.HttpComponent : Created ClientConnectionManager > org.apache.http.impl.conn.PoolingHttpClientConnectionManager@21a66d45 > 2020-04-17 15:39:47.021 INFO 18872 --- [ main] > o.a.c.impl.engine.AbstractCamelContext : Apache Camel 3.2.0 (CamelContext: > camel-1) is starting > 2020-04-17 15:39:47.045 INFO 18872 --- [ main] > org.eclipse.jetty.util.log : Logging initialized @4151ms to > org.eclipse.jetty.util.log.Slf4jLog > 2020-04-17 15:39:47.068 INFO 18872 --- [ main] > o.a.c.support.jsse.SSLContextParameters : Available providers: SUN version > 1.8. > 2020-04-17 15:39:47.757 INFO 18872 --- [ main] > o.a.c.c.s.internal.SalesforceSession : Login at Salesforce loginUrl: > https://test.salesforce.com/services/oauth2/token > <https://test.salesforce.com/services/oauth2/token> > 2020-04-17 15:39:50.118 INFO 18872 --- [ main] > o.a.c.c.s.internal.SalesforceSession : Login successful > 2020-04-17 15:39:50.118 WARN 18872 --- [ main] > o.a.c.c.salesforce.SalesforceComponent : Missing property packages, > getSObject* operations will NOT work without property rawPayload=true > 2020-04-17 15:39:50.119 INFO 18872 --- [ main] > o.a.c.impl.engine.AbstractCamelContext : StreamCaching is not in use. If > using streams then its recommended to enable stream caching. See more details > at http://camel.apache.org/stream-caching.html > <http://camel.apache.org/stream-caching.html> > 2020-04-17 15:39:50.127 WARN 18872 --- [ main] > o.a.c.c.salesforce.SalesforceConsumer: Property sObjectName or > sObjectClass NOT set, messages will be of type java.lang.Map > 2020-04-17 15:39:50.209 ERROR 18872 --- [ main] > o.a.c.impl.engine.AbstractCamelContext : Error starting CamelContext > (camel-1) due to exception thrown: null > > java.lang.NullPointerException: null > at > org.apache.camel.component.salesforce.i
Salesforce not working with camel 3.2
:124) ~[camel-spring-3.2.0.jar:3.2.0] at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:157) ~[camel-spring-3.2.0.jar:3.2.0] at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:403) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:360) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:897) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:553) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at com.teliacompany.electron.fi.IntegrationApplication.main(IntegrationApplication.java:10) [classes/:na] Caused by: java.lang.NullPointerException: null at org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper.createClient(SubscriptionHelper.java:343) ~[camel-salesforce-3.2.0.jar:3.2.0] at org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper.doStart(SubscriptionHelper.java:111) ~[camel-salesforce-3.2.0.jar:3.2.0] at org.apache.camel.support.service.BaseService.start(BaseService.java:115) ~[camel-api-3.2.0.jar:3.2.0] at org.apache.camel.support.service.ServiceHelper.startService(ServiceHelper.java:84) ~[camel-api-3.2.0.jar:3.2.0] at org.apache.camel.component.salesforce.SalesforceConsumer.doStart(SalesforceConsumer.java:320) ~[camel-salesforce-3.2.0.jar:3.2.0] at org.apache.camel.support.service.BaseService.start(BaseService.java:115) ~[camel-api-3.2.0.jar:3.2.0] at org.apache.camel.impl.engine.AbstractCamelContext.startService(AbstractCamelContext.java:3056) ~[camel-base-3.2.0.jar:3.2.0] at org.apache.camel.impl.engine.AbstractCamelContext.doStartOrResumeRouteConsumers(AbstractCamelContext.java:3394) ~[camel-base-3.2.0.jar:3.2.0] at org.apache.camel.impl.engine.AbstractCamelContext.doStartRouteConsumers(AbstractCamelContext.java:3325) ~[camel-base-3.2.0.jar:3.2.0] at org.apache.camel.impl.engine.AbstractCamelContext.safelyStartRouteServices(AbstractCamelContext.java:3230) ~[camel-base-3.2.0.jar:3.2.0] at org.apache.camel.impl.engine.AbstractCamelContext.doStartOrResumeRoutes(AbstractCamelContext.java:2992) ~[camel-base-3.2.0.jar:3.2.0] at org.apache.camel.impl.engine.AbstractCamelContext.doStartCamel(AbstractCamelContext.java:2790) ~[camel-base-3.2.0.jar:3.2.0] at org.apache.camel.impl.engine.AbstractCamelContext.doStartContext(AbstractCamelContext.java:2643) ~[camel-base-3.2.0.jar:3.2.0] at org.apache.camel.impl.engine.AbstractCamelContext.doStart(AbstractCamelContext.java:2606) ~[camel-base-3.2.0.jar:3.2.0] at org.apache.camel.spring.boot.SpringBootCamelContext.doStart(SpringBootCamelContext.java:43) ~[camel-spring-boot-3.2.0.jar:3.2.0] at org.apache.camel.support.service.BaseService.start(BaseService.java:115) ~[camel-api-3.2.0.jar:3.2.0] at org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2448) ~[camel-base-3.2.0.jar:3.2.0] at org.apache.camel.spring.SpringCamelContext.start(SpringCamelContext.java:121) ~[camel-spring-3.2.0.jar:3.2.0] ... 14 common frames omitted Thanks and Regards, Hemang Ajm
Blank, Non - String variable in dozer
Hi In one of the dozer mapping I wanted to use hardcoded blank value, so I used the variable mapping feature as mentioned on https://camel.apache.org/components/latest/dozer-component.html#_variable_mappings This feature does not work if the value is blank. Also in other situation , I wanted to use hardcoded "0" which was int and not string. 0 Currently I am using Custom Mapping<https://camel.apache.org/components/latest/dozer-component.html#_custom_mappings> to return "" and 0 respectively to solve my problem, but I feel it not as elegant as part of the mapping goes in different java file which does not have any logic but to return hardcoded value. Do you have any better suggestion? Thanks and Regards, Hemang Ajmera Hemang C Ajmera | Technical Architect Asia Pacific Communications, Media and Utilities Delivery Center | CGI Block 5, DLF-SEZ, Manapakkam, Chennai - 600089, India O: +91-44-6647-3828 | M: +91-89397-07557 | M: +91-98841-66619 | VOIP: 8083828 hemang.ajm...@cgi.com<mailto:hemang.ajm...@cgi.com> | www.cgi.com<http://www.cgi.com/> [Description: Description: Description: Description: Description: Description: Description: C:\Users\rahul.muthalali\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.Word\Top_Employer_India_English_2016.gif]
RE: Release cycle
Thanks for quick reply! Thanks and Regards, Hemang Ajmera -Original Message- From: Andrea Cosentino Sent: 07 November 2019 13:43 To: users@camel.apache.org Subject: Re: Release cycle 2.25.0 will be released in Q1 2020. 2.24.3 still doesn't have an ETA. There is no guidelines about release nor fixed timeline, when we have enough material to release, we release. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, November 7, 2019, 9:10:20 AM GMT+1, Ajmera, Hemang C wrote: Hi Wanted to know when camel 2.24.3 and 2.25.0 would be released. Also wanted to understand how release date of came is determined in general. Is there any guidelines or fixed timeline for next release? Thanks and Regards, Hemang Ajmera
Release cycle
Hi Wanted to know when camel 2.24.3 and 2.25.0 would be released. Also wanted to understand how release date of came is determined in general. Is there any guidelines or fixed timeline for next release? Thanks and Regards, Hemang Ajmera
