List of Java APIs: Difference between revisions

Content deleted Content added
empty section
Andbin (talk | contribs)
Added links
 
(8 intermediate revisions by 7 users not shown)
Line 1:
{{Short description|none}}
 
{{Multiple issues|
{{Citation style|date=December 2017|details=Violates Wikipedia:External links: "Wikipedia articles may include links to web pages outside Wikipedia (external links), but they should not normally be used in the body of an article."}}
Line 28 ⟶ 29:
| E-S-R consortium
| [http://www.e-s-r.net here]
|
|-
| [[Java Data Objects]]
| JDO
| A specification of Java object [[Persistence (computer science)|persistence]].
|
|-
| Android API
| Google
| [https://developer.android.com here]
|
|-
| [[JavaHelp]]
Line 53 ⟶ 51:
| JNDI
| An API for [[directory service]]s.
|
|-
| [[Jakarta Persistence]]
Line 94 ⟶ 91:
| Java library for the Discord API
| [https://github.com/DV8FromTheWorld/JDA available here]
|-
| Mixin
| SpongePowered
| This library adds ability to change existing code
| [https://github.com/SpongePowered/Mixin available here]
|-
| Wikipedia4j
| llmjava
| It's a library that you can use to search and retrieve documents from Wikipedia
| [https://github.com/llmjava/wikipedia4j available here]
|-
| Oshi
| oshi
| Library for working with [[Computer]] components and their parameters
| [https://github.com/oshi/oshi available here]
|-
| [[Google Guava|Guava]]
| Google
| A set of core Java libraries for collections, caching, primitives support, and more.
| [https://github.com/google/guava available here]
|-
| [[Apache Commons]]
| Apache
| A collection of reusable Java components, including utilities for collections, math, IO, and more.
| [https://commons.apache.org/ available here]
|-
| [[Log4j]]
| Apache
| A widely used Java logging library.
| [https://logging.apache.org/log4j/ available here]
|-
| [[JUnit]]
| JUnit
| A widely used testing framework for Java.
| [https://junit.org available here]
|-
| Caffeine
| (none)
| A high-performance caching library for Java.
| [https://github.com/ben-manes/caffeine available here]
|-
| Lombok
| (none)
| A Java library that reduces boilerplate code with annotations.
| [https://projectlombok.org available here]
|-
| [[SLF4J]]
| (none)
| A simple logging facade for Java, often used with Logback or Log4j.
| [https://www.slf4j.org available here]
|-
| Retrofit
| (none)
| A type-safe HTTP client for Java and Android.
| [https://square.github.io/retrofit/ available here]
|-
| OkHttp
| Square
| An HTTP client for Java with features like connection pooling and GZIP compression.
| [https://square.github.io/okhttp/ available here]
|-
| [[Gson]]
| Google
| A library for converting Java objects to JSON and back.
| [https://github.com/google/gson available here]
|-
| [[Jackson (API)|Jackson]]
| FasterXML
| A high-performance JSON processing library.
| [https://github.com/FasterXML/jackson available here]
|-
| Kryo
| EsotericSoftware
| A fast and efficient object graph serialization framework.
| [https://github.com/EsotericSoftware/kryo available here]
|-
| [[Apache Kafka]]
| Apache
| A distributed event streaming platform.
| [https://kafka.apache.org/ available here]
|-
| [[Netty (software)|Netty]]
| (none)
| An asynchronous event-driven network application framework.
| [https://netty.io available here]
|-
| [[Vert.x]]
| Eclipse
| A reactive toolkit for building distributed applications.
| [https://vertx.io available here]
|-
| [[Spring Framework]]
| Spring
| A powerful framework for building Java applications.
| [https://spring.io/ available here]
|-
| [[Micronaut (framework)|Micronaut]]
| (none)
| A lightweight framework for building microservices and cloud-native apps.
| [https://micronaut.io available here]
|-
| [[Hibernate (framework)|Hibernate]]
| (none)
| A powerful ORM (Object-Relational Mapping) framework.
| [https://hibernate.org/ available here]
|-
| Forge
| (none)
| A popular Minecraft modding API for Java Edition.
| [https://files.minecraftforge.net/ available here]
|-
| NeoForge
| (none)
| A community-driven fork of Forge for Minecraft modding.
| [https://github.com/NeoForged/ available here]
|-
| Fabric
| (none)
| A lightweight, modular Minecraft modding toolchain.
| [https://fabricmc.net/ available here]
|-
| Quilt
| (none)
| A community-driven fork of Fabric with additional features.
| [https://quiltmc.org/ available here]
|}
 
 
 
{| class="wikitable"
Line 114 ⟶ 238:
| <code>jakarta.jms</code>
|-
| [[Jakarta Server Faces]]
| JSF
| <code>jakarta.faces</code>
Line 204 ⟶ 328:
 
;Windowing libraries
The windowing library is a set of classes available in the Streams Processing Language (SPL) Runtime C++ API and the SPL Java™ Operator API. The library is used to implement primitive operators that need windows following the SPL window semantics. Using the windowing library provides a consistent window policy semantic across operators, and simplifies the operator implementation.
 
SPL offers both tumbling and sliding windows. Both types of windows keep all the incoming data in memory until its tuple eviction policy triggers. Use the SPL support for windows when the functionality required by the primitive operator can be built using the semantics provided by SPL window constructs.
 
One example operator from the SPL Standard Toolkit that uses the windowing library and syntax is the <kbd>Aggregate</kbd> operator. An example operator that buffers recently received tuples but that does not use the windowing library and syntax is the <kbd>DeDuplicate</kbd> operator. This action occurs because this operator has different eviction and trigger semantics than the ones provided by SPL. This operator needs to maintain only unique tuples and discards all repeated tuples that are received within a time window.
 
With the windowing library, developers can specify different eviction and trigger policies but can implement the event handling actions independently of the window policy details. There are a few differences when implementing primitive operators in C++ and Java that take advantage of the SPL window clause.
 
In the C++ implementation, developers have no obligation to use the window library (the preferred practice is to use library). They are free to use the SPL Operator Code Generation API just to get the specified window policy for a given operator instance. Then, they can generate code using other containers. In addition, developers can check for valid window configurations during code generation time.
 
In the Java implementation, developers must use the window library. This action can be achieved by registering a class that implements <kbd>com.ibm.streams.operator.window.StreamWindowListener<T></kbd> that handles events generated by a window <kbd>(com.ibm.streams.operator.window.StreamWindow<T></kbd>). This use is required because Java operators are not based on code generation. As a result, windows are automatically managed by the runtime to guarantee SPL window semantics. Developers can check for valid window configurations during runtime by checking the window policy associated to a given input port.
* [[Standard Widget Toolkit]] (SWT)
 
Line 223 ⟶ 336:
 
==See also==
* [[Java (software platform)|Java Platform]]
* [[Application programming interface]]
* [[Java ConcurrentMap]]
* [[List of Java Frameworksframeworks]]
 
==External links==