from Quarkus documentation I can read "Quarkus is made of ... Hibernate, RESTEasy, Eclipse Microprofile, etc.". I have an application which uses Thorntail stack so it's compatible with Eclipse Microprofile. Is the MicroProfile stack compatible with Quarkus's stack ? Should I change just the dependencies name, leaving the code untouched ?
Thanks
Related
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?
I used to configure -Djava.security.egd=file:/dev/./urandom in my Dockerfile for Spring Boot applications.
In https://spring.io/guides/gs/spring-boot-docker/ a comment was added that this is not required any more for newer versions:
To reduce Tomcat startup time we added a system property pointing to "/dev/urandom" as a source of entropy. This is not necessary with more recent versions of Spring Boot, if you use the "standard" version of Tomcat (or any other web server).
I am looking for any references for this change in Tomcat or Spring Boot repos, and which Spring Boot versions are affected.
This problem should have been resolved by the JDK Enhancement Proposal : JEP 123, Configurable Secure Random-Number Generation.
According to the JDK 8 Security Enhancements official Oracle document, the /dev/./urandom workaround is no more necessary from JDK 8.
SHA1PRNG and NativePRNG were fixed to properly respect the SecureRandom seed source properties in the java.security file. (The obscure workaround using file:///dev/urandom and file:/dev/./urandom is no longer required.)
I want to use the jackson module parameter-names with Java 8 in my spring boot application. I need to provide the option "-parameters" to the compiler. Could you please let me know how to do this in pom.xml for the spring boot plug-in spring-boot-maven-plugin.
I found only following answer (How to compile Spring Boot applications with Java 8 --parameter flag), but the answer refers to different plug-in.
Thanks.
Spring Boot relies on maven-compiler-plugin. Check Spring Boot parent pom. Or check my answer here
I saw from the Spring IO Platform website (http://spring.io/blog/2014/06/26/introducing-the-spring-io-platform) and it states that Spring IO is certified to work with Java 1.7 and 1.8.
However, the production stack of my company is Java 1.6 only so may I know that does Spring IO Platform BOM support Java 1.6 as well?
We intensive use Spring, Spring Data, Spring Batch, Spring Integration, Spring Retry.
thanks in advance
No, Java 6 isn't supported by Spring IO Platform. That said, I'm not aware of anything in the projects that you have listed that require Java 7 so it may well work but it isn't something that we (Pivotal) have tested or support.
I've been reading about using Spring Boot and Gradle to quickly build RESTful services: https://spring.io/guides/gs/rest-service/. I'd like to give it a try but I need to build a war that's compatible with servlet 2.4 (I know.. life in the 1970's).
The error I get when attempting to deploy the war generated by following the guide above to Sun App Server 8.1 is:
Unknown deployable object type specified: "Cannot determine the J2EE
component type"
The generated war has no web.xml and there may be other expected artifacts.
Configuring a spring-boot application using web.xml seems to suggest that a web.xml can be packaged with a Spring Boot application but doesn't explain how.
Is Spring Boot compatible with older servlet specs? How can Spring Boot and Gradle be used to generate a war that works on older web containers?
Thanks.
The answer to the question you linked to didn't actually go as far as saying that you could easily create a fully-leaded Boot application with Servlet 2.4. I consider that quite a hard, but probably achievable, target if you are prepared to do some legwork, and accept some compromises. You might find this stuff useful: https://github.com/scratches/spring-boot-legacy (I managed to use it to push an app to GAE). But there are some limits to what can be supported for such old technology, and we aren't officially supporting anything other than Servlet 3.0.1 right now.