Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spec updates for Flow #375

Merged
merged 1 commit into from
Nov 14, 2023
Merged

Spec updates for Flow #375

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions specification/src/main/asciidoc/jakarta-concurrency.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,7 +153,7 @@ need to be available.

Jakarta EE depends on various context information to be available on the
thread when interacting with other Jakarta EE services such as JDBC data
sources, Jakarta Messaging providers and Jakarta Enterrise Beans. When using Jakarta EE services from a
sources, Jakarta Messaging providers and Jakarta Enterprise Beans. When using Jakarta EE services from a
non-container thread, the following behaviors are required:

* Saving the application component thread’s container context.
Expand All @@ -174,7 +174,7 @@ Containers (represented here in a single rectangle) provide environments
for application components to safely interact with Jakarta EE Standard
Services (represented in the rectangles directly below the Enterprise Bean/Web
Container rectangle). Four new concurrency services (represented by four
dark-gray rectangles) allow application components and Jakarta EE Standard
orange horizontal rectangles) allow application components and Jakarta EE Standard
Services to run asynchronous tasks without violating container
contracts.

Expand Down Expand Up @@ -206,6 +206,9 @@ as "tasks" will be referred to throughout the specification:
* `java.util.function.Supplier`
** `get()`

===== Flow Contextual Invocation Points
The `java.util.concurrent.Flow` class provides interfaces for establishing flow-controlled components. Container context and management constructs are also propagated to methods on the `java.util.concurrent.Flow.Subscriber` interface, including the inherited methods in `java.util.concurrent.Flow.Processor`.

===== Optional Contextual Invocation Points

The following callback methods run with unspecified context by default,
Expand Down