Data Engineering: The industry has come a long way from organizing unstructured data to adopting today's modern data pipelines. See how.
What metrics does your organization use to measure success? MTTR? Frequency of deploys? Other? Tell us!
Principal Consultant at Improving Enterprises
Plano, US
Joined Aug 2006
Craig Walls has been professionally developing software for over 14 years (and longer than that for the pure geekiness of it). He is the author of Spring in Action (now in its second edition) and XDoclet in Action, both published by Manning and is currently writing about OSGi and Spring-DM.
Stats
Reputation: | 148 |
Pageviews: | 76.9K |
Articles: | 0 |
Comments: | 3 |
Nothing here yet! Would you like to post an article?
Spring Web Flow
Getting Started with Spring-DM
Spring Annotations
Spring Configuration
Comments
Oct 02, 2024 · Reza Ganji
Exactly what I had planned to reply.
Spring AI is a dedicated AI library for Spring (and something I'm quite fond of...enough to be writing a book about it). But to be clear, Spring AI is an application-level component for consuming models offered by OpenAI, Mistral, Anthropic, Google Vertex, etc. It is *not* a component for creating or publishing models.
Therefore, a more fair comparison would be to compare Spring AI with things like LangChain or LlamaIndex. Comparing Spring AI with PyTorch or anything like that is an unfair comparison, as they address two very different concerns.
LangChain and LlamaIndex are great when dealing with Python and Node. But when comparing Spring AI with LlamaIndex or LangChain, the most notable takeaway is that many enterprise applications are built in Java with Spring. Integrating Python or Node-based LlamaIndex and LangChain would be cumbersome at best. But Spring AI, being available for Java (and Kotlin) and built within the Spring portfolio of projects, offers a solution that plugs into the existing language and framework choices of many enterprise applications. In short, "No Python? No problem."
May 01, 2008 · Vera Tushurashvili
I can't say for certain whether it has anything to do with Wicket 1.3.3 or not. We're still using 1.3.0 because we were too close to a release of our app to go to a newer version of Wicket. I do recall seeing some odd behavior when going from 1.3.0 to 1.3.1 some time ago, so I switched back and never tried again (again, too close to a release to take any risks).
As for more info...have you looked in the "serviceability" folder? There are some logs in there that might help you.
May 01, 2008 · Vera Tushurashvili