@Version("1.0")

Package org.eclipse.microprofile.reactive.messaging

IMPORTANT This package is a copy from the original package from the specification. The original can be found on https://github.com/eclipse/microprofile-reactive-messaging. This copy is there to experiment around the spec. New features or changes are marked with the `experimental` tag and Experimental annotation. The MicroProfile Reactive Messaging API.

This API provides a mechanism for declaring managed streams. CDI managed beans may declare methods annotated with Incoming and/or Outgoing to declare a message subscriber, publisher or processor.

The container is responsible for running, maintaining liveness, and stopping the message streams on context shutdown. Containers should implement restarting in case a stream fails, with an appropriate backoff strategy in the event of repeat failures.

The application should use Reactive Streams to provide the message stream handlers. Generally, use of org.eclipse.microprofile.reactive.streams builders should be used in preference to either Reactive Streams interfaces directly, or container specific implementations of streams.

Here is an example use of this API: 

   @ApplicationScoped
   public class EmailPublisher {
     @Incoming("notifications")
     @Outgoing("emails")
     public ProcessorBuilder<Message<Notification>, Message<Email>> publishEmails() {
       return ReactiveStreams.<Message<Notification>>builder()
         .filter(msg -> msg.getPayload().isEmailable())
         .map(msg -> {
           Email email = convertNotificationToEmail(msg.getPayload());
           return Message.of(email, msg::ack);
         });
     }

     private Email convertNotificationToEmail(Notification notification) {
       ...
     }
   }