Spring AI-03.快速入门（Getting Started）

最新推荐文章于 2025-11-23 15:08:04 发布
最新推荐文章于 2025-11-23 15:08:04 发布
阅读量103 收藏
点赞数
CC 4.0 BY-SA版权
分类专栏： Java全套教程 Spring AI 人工智能(AI) 文章标签： spring 人工智能 java Spring AI
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/youyong/article/details/148451809

Spring AI-03.快速入门（Getting Started）

本节提供了如何开始使用 Spring AI 的切入点。您应根据需求按照以下各节中的步骤操作。

Spring AI 支持 Spring Boot 3.4.x。当 Spring Boot 3.5.x 发布后，我们也将提供支持。

Spring Initializr

访问 start.spring.io，并为新应用选择您想要使用的 AI 模型和向量存储。

构件仓库
里程碑版本 - 使用 Maven 中央仓库

从 1.0.0-M6 版本开始，版本可在 Maven 中央仓库中获取。无需对构建文件进行任何更改。

快照版本 - 添加快照仓库

要使用快照版本（及 1.0.0-M6 里程碑之前的版本），您需要在构建文件中添加以下快照仓库：

在 Maven 或 Gradle 构建文件中添加以下仓库定义：

Maven

了解本专栏 订阅专栏 解锁全文 超级会员免费看
Spring AI 的 Getting Started
莫凡的博客
10-25 575
【代码】Spring AI 的 Getting Started。
【Spring AI】03. 开始
u011046509的博客
04-28 1490
如下面的代码片段所示，可以为一个或多个spring-ai模块（例如spring-ai-openai）的Starter依赖项进行无版本声明。就像熟悉 JavaScript 生态系统的人的“create-react-app”命令一样，Spring CLI 提供了一个创建基于 Spring 的项目spring boot new的命令。Spring AI BOM 声明了 Spring AI 版本使用的所有依赖项的推荐版本。相反，您使用的 BOM 版本决定了使用的依赖项版本。
Spring AI 快速入门
moments的博客
12-17 4470
四次工业革命推动了人类社会发展和变革第一次工业革命（18世纪60年代~19世纪中期，大约是1760年到1860年）：也称为蒸汽时代，发源于英格兰中部地区，是资本主义工业化的早期阶段；蒸汽机的发明及运用成为了这个时代的标志，因此历史学家称这个时代为“蒸汽时代”；蒸汽时代的显著特征是机械化生产和大规模生产，推动了生产力的飞跃，带来了极大的经济增长；这一时期也出现了第一批大型企业和跨国公司；
Spring AI 快速入门：从环境搭建到核心组件集成
-曾牛的博客
04-25 2085
通过本文的步骤，您已掌握Spring AI的核心入门知识：从项目创建到依赖管理，再到按需集成不同AI组件。零配置启动：通过Spring Initializr和BOM简化依赖管理多供应商支持：统一接口下无缝切换OpenAI、Hugging Face等模型企业级适配：天然兼容Spring Boot生态的安全、监控、微服务等特性无论您是要开发智能客服、代码生成工具，还是复杂的RAG系统，Spring AI都能成为您的高效开发引擎。
Spring AI 使用教程
乐于分享，共同成长
05-24 2735
Spring AI 使用教程
spring-ai快速集成deepseek大模型
shaowei的专栏
02-12 681
spring-ai快速集成deepseek。 Spring AI致力于简化AI项目的开发与部署流程，使Java开发者能够更高效地将AI技术集成到业务系统中。它提供了开箱即用的工具和接口，方便集成和管理各种AI模型。
Spring AI——从入门到应用（持续更新）
intwei的博客
05-08 2224
Spring AI——从入门到精通(会话、MCP、RAG、Agent)
Ai框架Spring Cloud Alibaba Ai引入maven依赖报错Unresolved dependency: ‘org.springframework.ai:spring-ai-core:
A-Itfuture的博客
06-28 8119
原始的Spring AI并没有国内相关大模型的接入，对国内开发者不太友好。总的来说，Spring Cloud Alibaba AI 目前基于Spring AI 0.8.1版本 API 完成通义系列大模型的接入。于是，根据官方文档进行一次尝鲜体验！
08:28:41,486 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - 'File' option has the same value "C:\Users\DELL/logs/nacos/config.log" as that given for appender [CONFIG_LOG_FILE] defined earlier. 08:28:41,486 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 08:28:41,486 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 08:28:41,487 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - 'File' option has the same value "C:\Users\DELL/logs/nacos/naming.log" as that given for appender [NAMING_LOG_FILE] defined earlier. 08:28:41,487 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 08:28:41,487 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 08:28:41,487 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - 'File' option has the same value "C:\Users\DELL/logs/nacos/remote.log" as that given for appender [REMOTE_LOG_FILE] defined earlier. 08:28:41,487 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 08:28:41,487 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 2025-08-23T08:28:41.490+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] com.atguigu.study.HelloLangChain4JApp : Starting HelloLangChain4JApp using Java 21.0.8 with PID 18276 (E:\杨哥mysql\langchain4J-2025.8.22\01code\langchain4j-atguiguV5\langchain4j-01helloworld\target\classes started by DELL in E:\杨哥mysql\langchain4J-2025.8.22\01code\langchain4j-atguiguV5) 2025-08-23T08:28:41.491+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] com.atguigu.study.HelloLangChain4JApp : No active profile set, falling back to 1 default profile: "default" 2025-08-23T08:28:41.980+08:00 WARN 18276 --- [langchain4j-01helloworld] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.nacos.NacosConfigAutoConfiguration' of type [com.alibaba.cloud.nacos.NacosConfigAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). The currently created BeanPostProcessor [nacosAnnotationProcessor] is declared through a non-static factory method on that class; consider declaring it as static instead. 2025-08-23T08:28:41.984+08:00 WARN 18276 --- [langchain4j-01helloworld] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'nacosConfigProperties' of type [com.alibaba.cloud.nacos.NacosConfigProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [nacosAnnotationProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE. 08:28:41,990 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - 'File' option has the same value "C:\Users\DELL/logs/nacos/config.log" as that given for appender [CONFIG_LOG_FILE] defined earlier. 08:28:41,990 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 08:28:41,990 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 08:28:41,991 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - 'File' option has the same value "C:\Users\DELL/logs/nacos/naming.log" as that given for appender [NAMING_LOG_FILE] defined earlier. 08:28:41,991 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 08:28:41,991 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 08:28:41,991 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - 'File' option has the same value "C:\Users\DELL/logs/nacos/remote.log" as that given for appender [REMOTE_LOG_FILE] defined earlier. 08:28:41,991 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 08:28:41,991 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 08:28:41,993 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 08:28:41,993 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 08:28:41,993 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 08:28:41,993 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 08:28:41,994 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 08:28:41,994 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 08:28:42,024 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 08:28:42,024 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 08:28:42,024 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 08:28:42,024 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 08:28:42,024 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 08:28:42,024 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 2025-08-23T08:28:42.029+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] c.a.n.p.a.s.c.ClientAuthPluginManager : [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.impl.NacosClientAuthServiceImpl success. 2025-08-23T08:28:42.029+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] c.a.n.p.a.s.c.ClientAuthPluginManager : [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.ram.RamClientAuthServiceImpl success. 2025-08-23T08:28:42.031+08:00 WARN 18276 --- [langchain4j-01helloworld] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'nacosConfigManager' of type [com.alibaba.cloud.nacos.NacosConfigManager] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [nacosAnnotationProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE. 2025-08-23T08:28:42.171+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port 9001 (http) 2025-08-23T08:28:42.182+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat] 2025-08-23T08:28:42.182+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] o.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/10.1.41] 2025-08-23T08:28:42.248+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext 2025-08-23T08:28:42.248+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 734 ms 2025-08-23T08:28:42.687+08:00 WARN 18276 --- [langchain4j-01helloworld] [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dashscopeRerankModel' defined in class path resource [com/alibaba/cloud/ai/autoconfigure/dashscope/DashScopeAutoConfiguration$DashScopeRerankConfiguration.class]: Failed to instantiate [com.alibaba.cloud.ai.dashscope.rerank.DashScopeRerankModel]: Factory method 'dashscopeRerankModel' threw exception with message: DashScope API key must be set. Use the connection property: spring.ai.dashscope.api-key or spring.ai.dashscope.rerank.api-key property. 2025-08-23T08:28:42.689+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat] 2025-08-23T08:28:42.697+08:00 INFO 18276 --- [langchain4j-01helloworld] [ main] .s.b.a.l.ConditionEvaluationReportLogger : Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled. 2025-08-23T08:28:42.708+08:00 ERROR 18276 --- [langchain4j-01helloworld] [ main] o.s.boot.SpringApplication : Application run failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dashscopeRerankModel' defined in class path resource [com/alibaba/cloud/ai/autoconfigure/dashscope/DashScopeAutoConfiguration$DashScopeRerankConfiguration.class]: Failed to instantiate [com.alibaba.cloud.ai.dashscope.rerank.DashScopeRerankModel]: Factory method 'dashscopeRerankModel' threw exception with message: DashScope API key must be set. Use the connection property: spring.ai.dashscope.api-key or spring.ai.dashscope.rerank.api-key property. at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:657) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:645) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1375) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1205) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:569) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:529) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:339) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:373) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:337) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.DefaultListableBeanFactory.instantiateSingleton(DefaultListableBeanFactory.java:1222) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingleton(DefaultListableBeanFactory.java:1188) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:1123) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:987) ~[spring-context-6.2.7.jar:6.2.7] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:627) ~[spring-context-6.2.7.jar:6.2.7] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) ~[spring-boot-3.5.0.jar:3.5.0] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:753) ~[spring-boot-3.5.0.jar:3.5.0] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:439) ~[spring-boot-3.5.0.jar:3.5.0] at org.springframework.boot.SpringApplication.run(SpringApplication.java:318) ~[spring-boot-3.5.0.jar:3.5.0] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1362) ~[spring-boot-3.5.0.jar:3.5.0] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1351) ~[spring-boot-3.5.0.jar:3.5.0] at com.atguigu.study.HelloLangChain4JApp.main(HelloLangChain4JApp.java:12) ~[classes/:na] Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.alibaba.cloud.ai.dashscope.rerank.DashScopeRerankModel]: Factory method 'dashscopeRerankModel' threw exception with message: DashScope API key must be set. Use the connection property: spring.ai.dashscope.api-key or spring.ai.dashscope.rerank.api-key property. at org.springframework.beans.factory.support.SimpleInstantiationStrategy.lambda$instantiate$0(SimpleInstantiationStrategy.java:199) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiateWithFactoryMethod(SimpleInstantiationStrategy.java:88) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:168) ~[spring-beans-6.2.7.jar:6.2.7] at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:653) ~[spring-beans-6.2.7.jar:6.2.7] ... 21 common frames omitted Caused by: java.lang.IllegalArgumentException: DashScope API key must be set. Use the connection property: spring.ai.dashscope.api-key or spring.ai.dashscope.rerank.api-key property. at org.springframework.util.Assert.hasText(Assert.java:253) ~[spring-core-6.2.7.jar:6.2.7] at com.alibaba.cloud.ai.autoconfigure.dashscope.DashScopeConnectionUtils.resolveConnectionProperties(DashScopeConnectionUtils.java:66) ~[spring-ai-alibaba-autoconfigure-1.0.0-M6.1.jar:1.0.0-M6.1] at com.alibaba.cloud.ai.autoconfigure.dashscope.DashScopeAutoConfiguration$DashScopeRerankConfiguration.dashscopeRerankModel(DashScopeAutoConfiguration.java:415) ~[spring-ai-alibaba-autoconfigure-1.0.0-M6.1.jar:1.0.0-M6.1] at com.alibaba.cloud.ai.autoconfigure.dashscope.DashScopeAutoConfiguration$DashScopeRerankConfiguration$$SpringCGLIB$$0.CGLIB$dashscopeRerankModel$0(<generated>) ~[spring-ai-alibaba-autoconfigure-1.0.0-M6.1.jar:1.0.0-M6.1] at com.alibaba.cloud.ai.autoconfigure.dashscope.DashScopeAutoConfiguration$DashScopeRerankConfiguration$$SpringCGLIB$$FastClass$$1.invoke(<generated>) ~[spring-ai-alibaba-autoconfigure-1.0.0-M6.1.jar:1.0.0-M6.1] at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:258) ~[spring-core-6.2.7.jar:6.2.7] at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:393) ~[spring-context-6.2.7.jar:6.2.7] at com.alibaba.cloud.ai.autoconfigure.dashscope.DashScopeAutoConfiguration$DashScopeRerankConfiguration$$SpringCGLIB$$0.dashscopeRerankModel(<generated>) ~[spring-ai-alibaba-autoconfigure-1.0.0-M6.1.jar:1.0.0-M6.1] at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) ~[na:na] at java.base/java.lang.reflect.Method.invoke(Method.java:580) ~[na:na] at org.springframework.beans.factory.support.SimpleInstantiationStrategy.lambda$instantiate$0(SimpleInstantiationStrategy.java:171) ~[spring-beans-6.2.7.jar:6.2.7] ... 24 common frames omitted 什么错误怎么解决
08-24
Use the connection property: spring.ai.dashscope.api-key or spring.ai.dashscope.rerank.api-key property. ``` #### 原因分析： 你的应用尝试使用阿里云 DashScope 的 AI 模型（如 rerank 模型），但没有在...
Ai框架Spring Cloud Alibaba Ai引入maven依赖报错Unresolved dependency ‘org.springframework.aispring-ai-core
web13093320398的博客
02-10 604
尚未发布到 Maven Central Repository，您需要在 Maven 中另外配置 Repository 地址：https://docs.spring.io/spring-ai/reference/0.8-SNAPSHOT/getting-started.html#repositories。请注意，您需要更改maven配置文件中的 * ，因为此配置会将所有 maven 依赖请求重定向到 aliyun maven 仓库。搜了一下spring-ai-core这个包，发现没有0.8.1的版本！
Spring Boot + Spring AI快速体验
2509_94006535的博客
11-21 1026
Spring AI是Spring的一个子项目，是Spring专门面向于AI的应用框架。Spring AI 项目旨在简化整合人工智能功能的应用程序开发，避免不必要的复杂性。汲取了著名的 Python 项目 LangChain 和 LlamaIndex 的灵感，但 Spring AI 并不是这些项目的直接移植。该项目的成立的信念：下一波生成式人工智能应用程序不仅将面向Python开发人员，而且将在许多编程语言中无处不在。@Bean。
springboot接入deepseek深度求索 java
最新发布
2509_94082931的博客
11-23 294
以下是在springboot中接入aideepseek的过程。官网并没有java的示例。
My-Agent - 基于Java和Spring AI的智能体开发平台
持续分享有趣的技术干货
11-19 694
My-Agent是一个基于Java和SpringAI构建的智能体开发平台，采用前后端分离架构（React+SpringBoot），提供完整的AI智能体生命周期管理方案。核心特性包括：多模型支持（OpenAI/Ollama等）、可视化工作流编排、知识库检索（基于PgVector）以及工具集成扩展能力。平台采用模块化设计，支持流式对话、对话记忆管理等交互功能，并具备完善的监控与安全机制（JWT认证）。技术栈涵盖JDK21、SpringBoot3、MySQL8、PostgreSQL（PgVector）和Redis
spring全局懒加载(default-lazy-init)导致的afterPropertiesSet不执行问题
豆豆的博客
11-21 434
Spring配置default-lazy-init="true"会导致所有Bean延迟初始化，影响afterPropertiesSet方法的执行时机。解决方案包括：1)为关键Bean显式设置lazy-init="false"；2)使用@Lazy(false)注解；3)编程式强制初始化；4)使用DependsOn控制顺序。最佳实践建议分层配置策略，核心组件立即初始化，业务组件懒加载，并通过配置文件分离和环境区分优化配置。实际应用中，Web应用的请求处理相关Bean和批处
Spring Boot 集成 Spring AI：实现大模型对话与MCP Client
iioSnail的博客
11-20 820
上篇文章中（Spring Boot 集成 Spring AI：实现可被大模型调用的 MCP Server），我们构建了一个MCP Server，提供了查询个人信息、查询订单信息、下单等操作。但是，上篇文章我们使用的是Cherry Studio作为客户端来与后端进行交互。实际生产中，让客户去下载Cherry Studio，然后配置MCP Server显然不显示。因此，本篇文章将会教会你如何使用 Spring AI 构建一个简单的聊天界面，并支持MCP Client.
Spring Security安全框架原理与实战
u013157943的博客
11-19 360
Spring Security安全框架原理与实战
springcloud springboot nacos版本对应
2509_94006919的博客
11-23 314
nacos 1.1.4版本存在服务异常离线问题，请谨慎使用。2.0.4.RELEASE(停止维护，建议升级)1.5.1.RELEASE(停止维护，建议升级)
Springboot 3项目整合Knife4j接口文档（接口分组详细教程）
2509_94100925的博客
11-23 811
springboot 3开始javax包改成了jakarta，而swagger-oas等包中依然使用的是javax，所以报错。另外springfox已经停止更新有段时间了，并且不支持OpenAPI 3标准，升级Springboot 3.0以后会有更多问题暴露出来。而SpringBoot 3只支持OpenAPI 3规范，因此Spring官网推荐了Springdocspringfox 3.0.0： 同时兼容OpenAPI 2以及OpenAPI 3，但是停更很久了。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

程序员勇哥

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值