The Eclipse Foundation is home to the Eclipse IDE, Jakarta EE, and hundreds of open source projects, including runtimes, tools, specifications, and frameworks for cloud and edge applications, IoT, AI, automotive, systems engineering, open processor designs, and many others.
The Eclipse Foundation is an international non-profit association supported by our members, including industry leaders who value open source as a key enabler for their business strategies.
Whether you intend on contributing to Eclipse technologies that are important to your product strategy, or simply want to explore a specific innovation area with like-minded organizations, the Eclipse Foundation is the open source home for industry collaboration.
The Eclipse community consists of individual developers and organizations spanning many industries. Stay up to date on our open source community and find resources to support your journey.
The Eclipse Foundation provides our global community of individuals and organizations with a mature, scalable, and vendor-neutral environment for open source software collaboration and innovation.
Jakarta Transactions specifies standard Java interfaces between a transaction manager and the parties involved in a distributed transaction system: the resource manager, the application server, and
Jakarta WebSocket specifies the API that Java developers can use when they want to integrate WebSockets into their applications - both on the server side as well as on the Java client side. An
The Jakarta XML Web Services is a Java programming language API for creating web services, particularly SOAP services. Jakarta XML Web Services is one of the Java XML programming APIs. It is part of
Jakarta Model-View-Controller, or Jakarta MVC for short, is a common pattern in Web frameworks where it is used predominantly to build HTML applications. The model refers to the application’s data
Jakarta Messaging is a Java Message Oriented Middleware API for sending messages between two or more clients. It is a programming model to handle the producer-consumer messaging problem.
Jakarta JSON Processing is a Java API to process (e.g. parse, generate, transform and query) JSON documents. It produces and consumes JSON in a streaming fashion (similar to StAX API for XML) and
Jakarta JSON Binding is a standard binding layer for converting Java objects to/from JSON messages. It defines a default mapping algorithm for converting existing Java classes to JSON, while enabling
Jakarta Interceptors are used to interpose on business method invocations and specific events such as lifecycle events and timeout events that occur on instances of Jakarta EE components and other
The Jakarta EE Platform project produces the Jakarta EE Platform specification, which is an umbrella specification that aggregates all other Jakarta EE specifications. In addition, this Project is
Jakarta Data provides an API to allow easy data access technologies. Thus, a Java developer can split the persistence and the model with several features such as a Repository interface with the method
Jakarta Contexts and Dependency Injection defines a powerful set of complementary services that help to improve the structure of application code. A well-defined lifecycle for stateful objects bound
The Jakarta Connectors Architecture defines a standard architecture for Jakarta EE application components to connect to Enterprise Information Systems.
Jakarta Config is a Java API for working with configurations. It supports externalized configuration allowing applications to use different configurations for different environments (dev, test, prod)
Jakarta Concurrency provides a specification document, API and TCK for using concurrency from application components without compromising container integrity while still preserving the Jakarta EE
Jakarta Authorization defines a low-level SPI for authorization modules, which are repositories of permissions facilitating subject based security by determining whether a given subject has a given
The Java Authentication Service Provider Interface for Containers (JASPIC) defines a service provider interface (SPI) by which authentication providers that implement message authentication mechanisms