Official website:

microprofile.io

The very first MicroProfile pom.xml

start.microprofile.io

Spec overview

https://projects.eclipse.org/projects/technology.microprofile

MicroProfile Latest Spec (APIs)

latest release and Maven coordinates

MicroProfile blog

https://microprofile.io/blog/

OpenLiberty Guides

~30 MicroProfile related-guides, from REST and Angular, over Docker, Kubernetes Clouds and MicroProfile JavaDoc

Project overview with links to sources (github)

microprofile.io/projects/

Helidon MicroProfile Guides

MicroProfile specific guides, from tracing over metrics to health

Payara

MicroProfile blog

Quarkus

MicroProfile guides

Thorntail documentation

MicroProfile documentation

Apache TomEE

MicroProfile examples

kumuluzEE

MicroProfile examples

Meecrowave

MicroProfile documentation

SmallRye

Overview over SmallRye projects. Tutorials are partially available (e.g. Reactive Messaging)

Github

List of MicroProfile projects

@rieckpil's "Getting started with Eclipse MicroProfile"

examples and screencasts

Most of the MicroProfile runtimes also support Jakarta EE out-of-the-box. Checkout: Jakarta EE: Links and Resources.

See you at Web, MicroProfile and Java EE Workshops at Munich Airport, Terminal 2 or Virtual Dedicated Workshops / consulting. Is Munich's airport too far? Learn from home: airhacks.io.

MicroProfile REST client provides an alternative to plain JAX-RS client for writing System Tests. A given HTTP endpoint (it doesn't have to be a JAX-RS resource) has to be defined as a Java interface first:

@Path("/")
public interface AirhacksWorkshop {
    @GET
    String websiteContent();
}

package com.airhacks;

import org.eclipse.microprofile.rest.client.RestClientBuilder;
import (...)
public class WorkshopsTests {

    private AirhacksWorkshop workshop;

    @Before
    public void init() throws MalformedURLException {
        URL apiUrl = new URL("http://airhacks.com");
        this.workshop
                = RestClientBuilder
                        .newBuilder()
                        .baseUrl(apiUrl)
                        .build(AirhacksWorkshop.class);
    }

    @Test
    public void content() {
        String content = this.workshop.websiteContent();
        assertNotNull(content);
        assertThat(content, containsString("java"));
    }
}

A System Test is executed within a JUnit runtime and needs the implementation of the MicroProfile REST Client API:

<dependency>
    <groupId>org.jboss.resteasy</groupId>
    <artifactId>resteasy-client-microprofile</artifactId>
    <version>4.3.0.Final</version>
</dependency>

Currently there are Apache CXF, OpenLiberty, Thorntail and RESTEasy (used above) implementations available.

See you at Web, MicroProfile and Java EE Workshops at Munich Airport, Terminal 2 or Virtual Dedicated Workshops / consulting. Is Munich's airport too far? Learn from home: airhacks.io.

Authentication and authorization with MicroProfile JWT and Payara:

Tokens were generated with: jwtenizr.sh, the application was deployed with wad.sh.

Installing Jaeger, creating a microprofile.io / quarkus.io service with MicroProfile OpenTracing from scratch and in 7 minutes:

Subscribe to airhacks.fm podcast via: spotify| iTunes| RSS

The #46 airhacks.fm episode with Amelia Eiras-Blevins (@ameliaeiras) about:

math, physics, opensource, microprofile, JCP, Eclipse Foundation, Jakarta EE, TomEE, and Tomitribe

Simplest possible live- and readiness probes with quarkus.io and Microprofile Health:

See you at Web, MicroProfile and Java EE Workshops at Munich Airport, Terminal 2 or Virtual Dedicated Workshops / consulting. Is Munich's airport too far? Learn from home: airhacks.io.

64th airhacks.tv episode with following topics:

"VSC Config, Concurrency, Supply Chain Management Frameworks, BCE, Microservices, OSGi, Service Gateways, EJBs and CompletableFuture, SSE events and headers, WAD vs. Eclipse Plugins, BCE structure, GlassFish in production, Java EE application framework"

Any questions left? Ask now: https://gist.github.com/AdamBien/87815259f16ea1080df7b34a394958f1 and get the answers at the next airhacks.tv.

See you at Web, MicroProfile and Java EE Workshops at Munich Airport, Terminal 2 or Virtual Dedicated Workshops / consulting. Is Munich's airport too far? Learn from home: airhacks.io.

Injecting values from ConfigMap into a MicroProfile (Configuration) / Java EE application. The project was created with Java EE 8 / MicroProfile essentials archetype and deployed with payara-s2i image to OpenShift:

Subscribe to airhacks.fm podcast via: spotify| iTunes| RSS

An airhacks.fm conversation with Markus Kett (@MarkusKett) about:

C64 and sports games, Weiden is not in Bavarian Forest, soccer as motivation for programming, writing first programs in basic with 17, writing contacts management, PCs are boring machines, but good for business, Java is the best programming language, Pentium 1 was introduced at CEBIT in 1993, the dream about an own booth at CEBIT came true, webdesign software based on applets (XPage) was very successful at SYSTEMS in Munich, Markus was the business man and had no time for programming - like Steve Jobs, self-financing with selling products, competing with Microsoft and Adobe, writing a 4GL Java-based development environment like Visual Basic called XDev, Java Developers don't like the Drag and Drop programming experience, building an IDE from scratch, discussions with Sun Microsystems about StarOffice integration, migrating from Swing to SWT and Eclipse, using Vaadin as UI technology, connecting beautiful UI to DB was too hard, databases have more types than Java what makes code generation hard, in 4GL the database comes first, RapidEclipse is free but commercial support is available, XDev provides tool and project support, RapidClipse understands rich database types and generates JPA POJOs, Hibernate importer, how to write queries in Java, implementing JPA-SQL is based on xtext by itemis and generates JPA-QL from SQL, storing data is still too complicated, serialization looked promising but was too unsecure and only entire objects can be serialized, Kryo, Fast Serializer, JetStream (renamed to Microstream) serializer, the database engine stores objects in any file storage, there is no impedance mismatch, the native Java storage engine, queries are performed with Java 8+ streams, JCA connector passes transactions and security context to the application server, JCA prototypical implementation, kubernetes persistent volumes, Bavarian Forrest is like Canada, the largest walking robot, Roding race car, being a TV host on Giga, constant 30k downloads and the XDev TV, DVDs were more successful than TV, JCon and the coding keynote, Java EE as secret weapon at JCon, stealing (adapting) the "no slides" ideas, the world first free, physical, Java magazine JAVAPRO with 8500 readers, community prefers Java-only conference,

Eclipse Foundation won't get the rights to use Oracle's Java trademarks with the following implications:

"...

1. The javax package namespace may be used within Jakarta EE specifications but may be used “as is” only. No modification to the javax package namespace is permitted within Jakarta EE component specifications. Jakarta EE specifications that continue to use the javax package namespace must remain TCK compatible with the corresponding Java EE specifications.
2. Jakarta EE component specifications using the javax package namespace may be omitted entirely from future Jakarta EE Platform specifications.
3. Specification names must be changed from a “Java EE” naming convention to a “Jakarta EE” naming convention. This includes acronyms such as EJB, JPA or JAX-RS.

..."

Trademarks / licensing issues are quite complex, if you are interested in some background, listen to airhacks.fm episode: #13 From Java EE over EE4j to Jakarta EE with Mike Milinkovich

The javax namespace issue was known for years (see e.g. Reza's Joint Community Open Letter on Java EE Naming and Packaging), now we have a clear resolution. All the Java EE specifications / projects are going to be renamed with the "Jakarta" prefix (see Renaming Java EE Specifications for Jakarta EE) anyway.

Consistency, clarity and simplicity are crucial for the success of Jakarta EE. A clear cut e.g. renaming all packages from javax to e.g. jakarta would introduce a consistent look and feel and branding. A single package strategy is better, than a mix of javax and jakarta namespaces.

Forcing projects to migrate (=search "javax" and replace with "jakarta") or introducing breaking changes every 20 years (J2EE 1.2 was introduced in December 12, 1999) is acceptable. Such a migration could even introduce an opportunity to remove superfluous patterns, layers, indirections and libraries.