Java Ecosystem Buzzes with Value Objects Preview, WildFly 41 GA, and AI Innovations for Fusion Applications
The Java landscape is a dynamic ecosystem, and the week of July 13th, 2026, has been particularly active with significant updates across core Java technologies and popular frameworks. Headlining this week’s developments is the reintroduction of Value Objects (Preview) into OpenJDK’s Candidate status, signaling a crucial step forward for Project Valhalla. Alongside this, WildFly 41 has achieved General Availability, bringing a host of enhancements and updated platform support. Developers leveraging Open Liberty, TornadoVM, Apache TomEE, Java Operator SDK, LangChain4j, and Micronaut have also received point and maintenance releases, each offering valuable fixes and new capabilities. Furthermore, the Quarkus ecosystem sees the emergence of a novel build-time extension, Quarkus Shim, while Oracle is making waves with its new AI-native builder experience for Fusion Applications, underscoring the growing integration of artificial intelligence within enterprise software development.
OpenJDK Takes a Step Closer to Value Objects
A significant development within the OpenJDK community this week is the reintroduction of JEP 401, "Value Objects (Preview)," to Candidate status. This initiative, a core component of the ambitious Project Valhalla, aims to fundamentally enhance the Java language by introducing value objects. The journey for this JEP began in August 2020 with JEP Draft 8251554, then known as "Object Classes and Values (Preview)." Its recent advancement signifies a renewed focus and progress in defining objects that are distinguished solely by their data, rather than by their identity.
Value objects, as defined by JEP 401, are characterized by several key attributes: they must contain only final fields, they lack distinct identity (meaning two value objects with the same contents are considered equal), and their equality is determined exclusively by the values of their constituent fields. This paradigm shift has the potential to unlock substantial performance improvements by enabling more efficient memory layouts and garbage collection, particularly for data-centric applications. The move to Candidate status indicates that the JEP has passed initial review and is being considered for inclusion in a future JDK release, pending further testing and feedback. This is a critical phase, as it involves rigorous examination by the OpenJDK Development Kit (JDK) Enhancement Proposal (JEP) process, which includes review by the Java Language Architect, the Java Virtual Machine (JVM) team, and other relevant experts. The re-introduction suggests that initial concerns have been addressed and the proposal is on a clearer path toward becoming a permanent feature of the Java language.
JDK Early-Access Builds Continue to Evolve
In parallel with the progress on language features, the OpenJDK project continues its rapid development cycle with early-access builds for upcoming JDK releases. For JDK 27, Build 31 was released this past week. This build represents an incremental update over Build 30, incorporating fixes for a variety of identified issues. The JDK development process is iterative, with early-access builds serving as crucial testing grounds for developers to experiment with new features and provide feedback. These builds are not intended for production environments but are vital for the broader community to identify potential bugs and performance regressions long before a stable release. The release notes for JDK 27 Build 31 detail the specific bug fixes and any minor enhancements, providing transparency into the ongoing refinement of this future Java platform release.
Similarly, JDK 28 also saw its early-access builds advance with the release of Build 7. This update, following Build 6, also includes a series of bug fixes aimed at stabilizing the next major JDK iteration. The concurrent development of multiple JDK versions highlights the OpenJDK community’s commitment to both delivering timely improvements to existing LTS (Long-Term Support) releases and pushing the boundaries of innovation for future platforms. The early-access program for both JDK 27 and JDK 28 allows developers to prepare for future language and platform changes, ensuring a smoother transition when these versions become production-ready. The continuous stream of updates underscores the agile nature of open-source development, where transparency and community involvement are paramount.
WildFly 41 Lands with Enhanced Features and Platform Support
The application server landscape is energized by the General Availability (GA) release of WildFly 41. This release is not merely a collection of bug fixes; it introduces several compelling new features and significant platform updates. Notably, bootable JARs have been integrated into the wildfly-cloud-galleon-pack and the wildfly-maven-plugin feature packs, simplifying the deployment and packaging of WildFly applications. This enhancement is particularly beneficial for cloud-native deployments and microservices architectures, where streamlined packaging and rapid deployment are critical.
Furthermore, WildFly 41 now offers container, S2I builder, and runtime images built with JDK 25, replacing the previous JDK 17 editions. This move signifies WildFly’s commitment to staying current with the latest Java Development Kit versions, ensuring that applications deployed on WildFly benefit from the performance improvements, security patches, and new features introduced in JDK 25. The adoption of newer JDK versions is a crucial aspect of maintaining a secure and performant application server environment, and this update demonstrates WildFly’s proactive approach. Additionally, several features have been promoted from preview to community and default stability levels, indicating their readiness for broader adoption and production use. This promotion process is a testament to the maturity and stability of these features, providing developers with greater confidence in their utilization. The release notes for WildFly 41 provide comprehensive details on all these changes, making it an essential read for anyone managing or developing applications on the WildFly platform. The progression of features through stability levels is a well-established practice in enterprise software, ensuring that new capabilities are thoroughly vetted before becoming standard.
Open Liberty 26.0.0.7 Addresses Security and Functionality
The Open Liberty runtime continues its rapid release cadence with the GA release of version 26.0.0.7. This update brings a mix of crucial bug fixes and new functionalities, with a particular emphasis on security enhancements. A significant change is the default tracking of logged-out Single Sign-On (SSO) cookies. This measure prevents the replay of these cookies after a user has logged out, bolstering the security posture of applications relying on SSO mechanisms. This is a proactive step to mitigate potential vulnerabilities that could arise from improperly managed session tokens.
In terms of functional improvements, Open Liberty 26.0.0.7 now offers the ability to disable the /health endpoints when using MicroProfile Health 4.0 with a file-based health check mechanism. This provides developers with more granular control over their application’s health reporting, allowing them to tailor it to specific deployment scenarios. Beyond these specific features, this release also addresses eight Common Vulnerabilities and Exposures (CVEs). These fixes target critical security issues such as denial-of-service attacks, HTTP request smuggling, and server-side request forgery, underscoring Open Liberty’s ongoing commitment to providing a secure and robust runtime environment. The proactive patching of CVEs is a critical aspect of maintaining enterprise-grade software, and this release demonstrates that commitment.
TornadoVM 5.1.0 Enhances CUDA and PTX Backends, Boosts Performance
For developers looking to leverage heterogeneous computing, TornadoVM 5.1.0 offers significant advancements, particularly for its CUDA and PTX backends. This release introduces support for the E4M3 and E5M2 eight-bit floating-point storage formats within the CUDA backend. This capability is crucial for applications that can benefit from reduced precision for memory efficiency and potentially faster computations, especially in areas like machine learning and scientific simulations where such formats are increasingly adopted.
The addition of an opt-in staged host-to-device transfer path for both PTX and CUDA backends is another key enhancement. This feature allows for more optimized data movement between the host and the device, potentially reducing latency and improving overall application performance. Performance optimizations are also evident within the withIntraPlanConcurrency() method of the TornadoExecutionPlan class. This optimization aims to reduce bookkeeping costs associated with intra-plan concurrency, leading to more efficient execution of parallel tasks. These updates reflect TornadoVM’s continuous effort to bridge the gap between high-level Java code and low-level hardware acceleration, making it more accessible and performant for a wider range of use cases. The focus on heterogeneous computing aligns with industry trends towards utilizing specialized hardware for accelerated processing.
Apache TomEE 10.2.0 Resolves Key Logging and Exception Handling Issues
Apache TomEE 10.2.0 has been released, focusing on dependency upgrades and critical bug fixes that enhance the stability and reliability of the TomEE platform. A notable resolution addresses an issue where the sslTruststorePassword parameter within the HttpConnection inner class of HttpConnectionFactory was not being masked or stripped during logging. This fix is crucial for security, as sensitive credentials should not be exposed in log files. By ensuring this parameter is properly handled, TomEE reinforces secure logging practices.
Another significant bug fix resolves an AuthenticationException that was being thrown from within the authenticate() method of the JNDIContext class. Previously, this exception would lose the original cause thrown by a RemoteException, making it difficult to diagnose the root cause of authentication failures. The resolution ensures that the full exception chain is preserved, providing developers with more actionable information for debugging. These fixes, along with other dependency upgrades, solidify TomEE’s position as a robust and secure Java EE application server. The meticulous attention to detail in resolving logging and exception handling issues demonstrates a mature development process focused on operational stability.
Java Operator SDK 5.5.0 Streamlines Resource Management with Patching and Matching
The Java Operator SDK has seen a significant update with version 5.5.0, introducing substantial improvements to resource management capabilities for Kubernetes operators. A key highlight is the introduction of a complete and consistent family of update, patch, and create methods within the ResourceOperations class. These methods now fully support both RFC 6902 (JavaScript Object Notation – JSON Patch) and RFC 7386 (JSON Merge Patch) specifications. This enables developers to implement more sophisticated and precise resource modifications within their operators, aligning with industry standards for declarative management.
Furthermore, a new Matcher interface has been introduced. This provides developers with the flexibility to plug in custom matching strategies into the overloaded matchAndFilter() method within the Options class. This feature is invaluable for building more intelligent and adaptable operators that can intelligently identify and process specific resources based on custom criteria, going beyond simple equality checks. These enhancements streamline the development of complex operators and contribute to more robust and maintainable Kubernetes control plane components. The adoption of RFC standards for patching is a significant step towards interoperability and best practices in resource manipulation.
LangChain4j 1.18.0 Introduces BDI Agents and Enhanced TTS/Batch API Support
LangChain4j, a popular library for building LLM-powered applications in Java, has released version 1.18.0, which includes a formal release alongside its twenty-eighth beta release. This update brings notable features, including the introduction of a new Belief-Desire-Intention (BDI) agentic pattern. The BDI model, inspired by cognitive psychology, provides a structured framework for developing agents that can reason, plan, and act based on their internal beliefs, desires, and intentions. This pattern is expected to facilitate the creation of more sophisticated and goal-oriented AI agents within Java applications.
In terms of model integration, LangChain4j 1.18.0 introduces a TextToSpeechModel interface, offering support for the OpenAI Text-to-Speech API. This allows developers to easily integrate text-to-speech capabilities into their applications, generating natural-sounding audio from text. Additionally, a new MistralAiBatchChatModel class has been added to support the Mistral AI Batch API. This enables developers to process multiple chat requests in a single API call, significantly improving efficiency and reducing latency for batch operations. These additions demonstrate LangChain4j’s commitment to expanding its integration with cutting-edge AI services and providing developers with powerful tools for building advanced language model applications. The inclusion of BDI agents signifies a move towards more sophisticated agent architectures in the LLM space.
Quarkus Introduces "Quarkus Shim" for Build-Time Code Manipulation
The Quarkus ecosystem has gained a new experimental extension called "Quarkus Shim." Developed by the Quarkus team, this extension offers a powerful mechanism for developers to modify the behavior of Java classes during the Quarkus build process. The core functionality of Quarkus Shim lies in its ability to add, wrap, or replace existing class behavior without requiring runtime instrumentation or Java agents. This means that the transformations applied by Quarkus Shim are baked into the application at build time, ensuring that the modified classes function seamlessly across JVM mode, development mode, and native executables.
This build-time code manipulation capability opens up new possibilities for customizing and optimizing applications within the Quarkus framework. Developers can leverage Quarkus Shim for various purposes, such as injecting custom logic, optimizing performance-critical sections of code, or integrating with legacy libraries in a non-intrusive manner. The extension is built with Quarkus 3.37.3, indicating its alignment with the latest versions of the framework and its experimental nature suggests that it is still undergoing active development and refinement. This innovative approach to code modification at build time is a testament to Quarkus’s focus on developer productivity and performance optimization. The ability to perform these modifications without runtime overhead is a significant advantage for performance-sensitive applications.
Oracle Unveils AI-Native Builder for Fusion Applications
Oracle is making significant strides in integrating artificial intelligence into its enterprise application suite with the introduction of a new AI-native builder experience for Oracle AI Agent Studio for Fusion Applications. This innovative offering allows customers to create and natively run "Fusion Agentic Applications" directly within Oracle Fusion Cloud Applications. The new builder experience is designed to provide a unified framework that accommodates no-code, low-code, and pro-code development approaches, catering to a diverse range of user skill sets and project requirements.
By enabling the creation of agentic applications within the Fusion Applications environment, Oracle is empowering businesses to embed intelligent automation and AI-driven decision-making directly into their core business processes. This could manifest in various ways, such as intelligent assistants for customer service agents, automated workflow optimization, or proactive insights for financial planning. The "Fusion-native" aspect of this framework ensures seamless integration with existing Fusion Cloud Applications data and functionalities, offering a cohesive and powerful solution for enterprise AI adoption. It is important to note that both Oracle AI Agent Studio and Oracle Fusion Cloud Applications are subscription services, reflecting Oracle’s strategy of delivering advanced capabilities through its cloud-based offerings. This move signals Oracle’s commitment to a future where AI is not an add-on but an intrinsic part of enterprise software solutions. The convergence of no-code, low-code, and pro-code development within a single framework is a trend aimed at democratizing AI development and accelerating its adoption across organizations.
