Jakarta Activation lets you take advantage of standard services to: determine the type of an arbitrary piece of data; encapsulate access to it; discover the operations available on it; and instantiate the appropriate bean to perform the operation(s).
Jakarta Activation is used for data content handling by:
The 2.1.3 release is the bug fix release fixing erroneous
assumption about classes being loaded from Thread.getContextClassLoader
.
The 2.1.2 release is the bug fix release which adds missing
javadoc description to jakarta.activation.MimeTypeEntry
get
methods
and fixes class file version in package-info
.
The 2.1.1 release is the bug fix release which removes the need for accessDeclaredMembers permissions when loading DataHandlers and improves usability in OSGi environment.
The 2.1.0 release is the first release providing standalone API jar file. The implementation, formerly JakartaActivation, is now standalone project - Eclipse Angus. This version of the specification is included in the Jakarta EE 10 Platform.
The 2.0.1 release is the bug fix release of 2.0.0.
The 2.0.0 release is the first release under the jakarta
namespace.
It is also the first release containing full module metadata.
The JavaBeans Activation Framework has been renamed to Jakarta Activation in preparation for inclusion in a future version of Jakarta EE.
The 1.2.1 release is the first release of the Eclipse project for JAF and includes no bug fixes or enhancements. It does include changes to the Maven coordinates. The main jar file is now located at com.sun.activation:jakarta.activation.
This standalone release of JAF uses a
Java Platform Module System
“automatic” module name of jakarta.activation
, which is different than the
module name used in JDK 9 and 10.
A future version will include full module metadata.
The JavaBeans Activation Framework project is now hosted at the Eclipse Foundation as part of the EE4J project.
The JavaBeans Activation Framework 1.2 and earlier API is defined through the Java Community Process as JSR 925.
The Jakarta Activation API documentation is available here.
The following documents summarize the API changes in each release of the JavaBeans Activation Framework API specification:
You can post questions to the jaf-dev mailing list.
Jakarta Activation bugs are tracked in the GitHub Jakarta Activation project issue tracker.
From time to time snapshot releases of the next version of JAF under development are published to the Jakarta Sonatype OSS repository. These snapshot releases have received only minimal testing, but may provide previews of bug fixes or new features under development.
For example, you can download the jakarta.activation.jar file from the Jakarta Activation 1.2.2-SNAPSHOT release here. Be sure to scroll to the bottom and choose the jar file with the most recent time stamp.
You’ll need to add the following configuration to your Maven ~/.m2/settings.xml to be able to use these with Maven:
<profiles>
<!-- to allow loading Jakarta snapshot artifacts -->
<profile>
<id>jakarta-snapshots</id>
<pluginRepositories>
<pluginRepository>
<id>jakarta-snapshots</id>
<name>Jakarta Snapshots</name>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
<checksumPolicy>fail</checksumPolicy>
</snapshots>
<url>https://jakarta.oss.sonatype.org/content/repositories/snapshots/</url>
<layout>default</layout>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
And then when you build use mvn -Pjakarta-snapshots ...
.
If you want the plugin repository to be enabled all the time so you don’t need the -P, add:
<activeProfiles>
<activeProfile>jakarta-snapshots</activeProfile>
</activeProfiles>
By contributing to this project, you agree to these additional terms of use, described in CONTRIBUTING.