Documentação do Projeto Organizar a Arquitetura do Projeto Desenvolver o Core da Aplicação Sistema de Autentificação Spring Security
Rafael-Lasso Updated
Hello, is there a possibility to run liquibase cassandra extension via spring boot? Can’t find any example online. Also I’ve done some research: spring-projects/spring-boot#29991 (comment) , #4 (comment). Seems confusing, could someone show me an example, if its possible ? thanks
dzasti Updated
k-h0shikawa Updated
k-h0shikawa Updated
k-h0shikawa Updated
Refactoring 거의 끝나간다.. Spring framework -> Gradle Spring boot data JPA 적용 OracleDB -> MySQL frontend(No template engine) jsp -> vite-react IDE Eclipse -> IntelliJ
Jason-Kwonn Updated
Many our our existing test projects, and other utilities are not all up to the latest 3.1.x version. In the past a similar issue was opened to perform the latest upgrade for example 2.6-> 2.7. #21588
I recently configured the library in my Spring Boot project and have two questions: Is Cassandra migration supposed to throw an exception on an invalid migration and not stop the app from running? Other beans are initialized before ending the migration scripts, is it on purpose or my local problem?
dzasti Updated
Spring Boot 2.7 Support Ends in November: We should upgrade all services to the newest SB Version (Currently 3.1) Preparations Upgrade to Spring Boot 2.7.x Upgrade Spring Security to 5.8 in digiwf-spring-security and use digiwf-spring-security lib in each application (#758) Migrate Autoconfigurations (#634) Remove deprecated libs Remove digiwf-spring-cloudstream-utils (#757) Remove digiwf-asyncapi-docs (#647) Use aggregation for digiwf-integrations (#760) Migration Use Aggregation to split parent module into multiple modules to migrate each part of the application separately (#759) For each module (#767, #762, #761, #763, #764, #765, #766, #768): Upgrade Spring Boot to v3.x Upgrade Spring Security Configure Properties Upgrade dependencies for each application Finish migration (#770) Ref Arch refactoring (#769) In addition to that we should remove/add some RefArch Legacy: GracefullShutdown -> SB Probes with proper Openshift Config - RefArch MR ErrorMapping to 4xx - RefArch MR Maybe more: Additional Info Spring Boot Migration Guide [RefArch Migration Guide:
After successfully migrating to spring boot we should undo the maven aggregation and use inheritance again for digiwf-connector digiwf-engine digiwf-gateway digiwf-libs digiwf-schema-registry digiwf-process digiwf-task Todo Use maven inheritance for the maven modules
Create Spring Boot project with dependencies: h2 database for development postgres driver - prod flyway migration spring security(?) spring security oauth starter vaadin spring jpa jjwt lombok devTools
DmitriyIvanov89 Updated
web-ark-plugin 支持模块使用tomcat runtime-sofa-boot-plugin 支持兼容sofaboot内容(SofaFramework管理、JvmService缓存、卸载关闭sofaruntime、biz健康检查) spring-boot-ark-plugin 支持兼容springboot内容(卸载关闭springcontext)
yuanyuancin Updated stale
k-h0shikawa Updated
Describe the solution you'd like With Spring-Boot 2.7 the spring auto configuration location moved from spring.factories to META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports. We should adjust our auto configurations to the new format. For more information checkout the Spring Boot Release Notes:
Course on Udemy - Part of my PDP
JohanSchoubben Updated
HTTPS, HTTP/2; Authentication: login and all requests should check user's identity, integrity of data and its corruption. Possible solution can include JWT. How to check passwords' equality with AuthenticationManager? Authorization: check user's permissions to access endpoints and complete actions there: Add roles
Danver98 Updated
The main branch is on the same state as the spring-3.0.x branch. 1. the latest 3.0.x version of Spring boot is 3.0.10. Please consider upgrading to it (the pom.xml currently uses 3.0.4) 2. The states, the project would be based on Spring Boot 2.7.x, which it isn't. Please update that accordingly. 3. In the pom.xml you define a separate spring.boot.configuration-processor version. Please consider using the same spring.boot.version version. 4. Even the commercial support for Spring Boot 2.5.x ended more than two weeks ago, but it is still has it's own auto-configuration, that is officially supported. Spring Boot 3.1.x released almost 4 month ago now, but there still is no auto-configuration nor official support (the Spring Boot 3.0.x integration does work completely fine with Spring Boot 3.1.x too, though). Please consider adding a Spring Boot 3.1.x auto-configuration. If you wish, I can also open a PR.
A carbon aware scheduler (earliest, latest). Time shifting, forecast region (electricitymaps etc..)
WtfJoke Updated java
Spring Boot Admin Server information Version: 3.1.4 Spring Boot version: 3.0.9 Configured Security: N/A Webflux or Servlet application: servlet Client information Spring Boot versions: 3.0.9 Used discovery mechanism: self registration Webflux or Servlet application: servlet Description The clustering is working fine and applications are being clustered on all servers. The problem is that if a new version of a given application is deployed, then the old instance is never removed from Spring Admin. yaml hazelcast: cluster-name: spring-admin metrics: enabled: false management-center: enabled: false retention-seconds: 30 jmx: enabled: false map: spring-boot-admin-event-store: backup-count: 1 in-memory-format: OBJECT merge-policy: batch-size: 100 class-name: PutIfAbsentMergePolicy time-to-live-seconds: 30 eviction: eviction-policy: NONE spring-boot-admin-sent-notifications: backup-count: 1 in-memory-format: OBJECT merge-policy: batch-size: 100 class-name: PutIfAbsentMergePolicy time-to-live-seconds: 30 eviction: eviction-policy: LRU network: reuse-address: true outbound-ports: - 33000-35000 port: auto-increment: false port: 5701 join: auto-detection: enabled: false multicast: enabled: false tcp-ip: enabled: false aws: enabled: true hz-port: 5701 service-name: dev-admin-server interfaces: enabled: true interfaces: - 10.171.0-240.*
Previous Next