I currently have Flo installed with my Spring XD installation, however when I try to create a composed job the DSL fails to generate and I am not allowed to finish creating the job. Any ideas why this could be happening? I have spring xd 1.2.1 and have tried Flo 1.3.0 and 1.2.1
Flo with batch support is only supported with Spring XD 1.3.x+. You'll need to upgrade your XD installation to use it.
Related
I resolve some fixes vulnerabilites in a java application and we have a critical issue https://nvd.nist.gov/vuln/detail/cve-2016-1000027 the point here is the current version of springboot is 2.7.2 and migrate version for use springboot 3.0.0 the camel 3 context not load, Does anyone know if spring boot 3 is compatible with any version of camel3?
Camel 4 will support Spring Boot 3. Until then, I'd recommend upgrading to the latest Spring Boot 2.7.x release.
I am upgrading to spring boot 2.7.0 do I need to also upgrade all the Managed Dependencies mentioned in https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-dependencies/2.7.0 in my project also ?
Thanks
Just upgrade the spring boot parent version and let it handle its related dependencies
Read these points:
https://www.baeldung.com/spring-boot-starter-parent#spring-boot-starter-parent
https://www.baeldung.com/spring-boot-starter-parent#managing-dependencies
I have a Spring boot 2.25.1 application which is using Camel 2.25.1 with camel-kafka everything is working fine..
In my Kafka consumer, I have a need to add the feature to pause consumption on demand so I upgraded to camel 3.18.1 so I can use the pausable feature.
After upgrading to 3.18.1 I am getting error FileNotFound with class file TimeoutAwareAggregationStategy.class.
when I opened camel-core 3.18.1 jar this class does not exist which was available in came 2.25.1 version.
Please suggest.
I was expecting smoother upgrade from camel 2.25.1 to camel 3.18.1.
According to the Camel upgrade guide for Camel 2.x to 3, the camel-core was modularized and broken up into multiple jar files. In that upgrade guide, they mention a lot of changes to Aggregation Strategies. While I couldn't find a direct implementation of the AggregationStrategy interface called TimeoutAwareAggregationStategy, I can see that class exists in camel-core in version 2.25.4 and the AggregationStrategy interface is moved to camel-api in version 3.0.
I was expecting smoother upgrade from camel 2.25.1 to camel 3.18.1
Normally, when upgrading a major version to a newer major version, there will be major changes that you have to account for. These changes are almost always covered in the change list or upgrade guide.
In start.spring.io, when Spring Boot 2.7.1 is selected it reports that Apache Camel "Requires Spring Boot >= 2.0.0.M1 and < 2.7.0-M1" (see screenshot below).
Is there a specific reason for this or where can I find more information on this?
The Camel team have not yet indicated that camel-spring-boot-starter supports Spring Boot 2.7. Until they're ready to support 2.7, the combination is disabled. Support for Spring Boot 2.7 seems to be part of Camel 3.18 which, at the time of writing, has not been released.
The application is created using spring boot version 1.2.5 Release. I can see that it includes an embedded tomcat version which is 8.0.23. Is it possible to upgrade to a recent tomcat version, let's say, tomcat 9 with spring boot 1.2.5 and still run the application? Or do we need to upgrade the spring boot version to be compatible with tomcat 9? Is there any documentation for the spring boot version compatibility with Tomcat? Thank you.
Why do you want to upgrade it? What is the newer version of tomcat going to bring?
I personally go with the defaults for the spring version unless there is a specific need or issue.
That being said this question may have some pointers
How to change embedded tomcat's version in existing spring boot app?
You may be able to just set the property
9.0.5
It would be preferable to upgrade to the latest Spring Boot release (currently 2.2.5-RELEASE) to avail yourself of the latest features. There are many tutorials, migration guides, problem solutions, etc., out there to guide you, of which here are just a couple:
https://spring.io/blog/2018/03/12/upgrading-start-spring-io-to-spring-boot-2
Global CORS configuration breaks when migrating to Spring Boot 2.0.x
You didn't specify a reason for keeping your Spring Boot version at 1.2.5-RELEASE and only upgrading tomcat, but if you really must, there are other answers, such as here: How to change embedded tomcat's version in existing spring boot app?