Skip to content

Commit

Permalink
Remove references to the removed jakarta.annotation.ManagedBean #750
Browse files Browse the repository at this point in the history
Signed-off-by: Scott M Stark <[email protected]>
  • Loading branch information
starksm64 authored and manovotn committed Jan 30, 2024
1 parent ec24b34 commit 4c4a6ce
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 7 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,8 @@
/**
* <p>
* The container fires an event of this type for every injection point of every Java EE component class supporting injection
* that may be instantiated by the container at runtime, including every managed bean declared using
* {@code jakarta.annotation.ManagedBean}, EJB session or message-driven bean, enabled bean, enabled interceptor or enabled
* decorator.
* that may be instantiated by the container at runtime, including every EJB session or message-driven bean, enabled
* bean, enabled interceptor or enabled decorator.
* </p>
* <p>
* Any observer of this event is permitted to wrap and/or replace the {@link InjectionPoint} by calling either
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,8 @@
/**
* <p>
* The container fires an event of this type for every Java EE component class supporting injection that may be instantiated by
* the container at runtime, including every managed bean declared using {@code jakarta.annotation.ManagedBean}, EJB session or
* message-driven bean, enabled bean, enabled interceptor or enabled decorator.
* the container at runtime, including EJB session or message-driven bean, enabled bean, enabled interceptor or
* enabled decorator.
* </p>
* <p>
* Any observer of this event is permitted to wrap and/or replace the {@link InjectionTarget}. The
Expand Down
4 changes: 2 additions & 2 deletions spec/src/main/asciidoc/javaee/spi_ee.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -62,13 +62,13 @@ When running in Jakarta EE, the container must extend the rules defined in <<pro

==== `ProcessInjectionPoint` event and EJB

When running in Jakarta EE, the container must also fire an event for every injection point of every Jakarta EE component class supporting injection that may be instantiated by the container at runtime, including every managed bean declared using `@ManagedBean`, EJB session or message-driven bean.
When running in Jakarta EE, the container must also fire an event for every injection point of every Jakarta EE component class supporting injection that may be instantiated by the container at runtime, including every EJB session or message-driven bean.

[[process_injection_target_ee]]

==== `ProcessInjectionTarget` event and EJB

When running in Jakarta EE, the container must also fire an event for every Jakarta EE component class supporting injection that may be instantiated by the container at runtime, including every managed bean declared using `@ManagedBean`, EJB session or message-driven bean.
When running in Jakarta EE, the container must also fire an event for every Jakarta EE component class supporting injection that may be instantiated by the container at runtime, including every EJB session or message-driven bean.

The container must extend the rules defined in <<process_injection_target>> for managed bean to EJB session bean and other Jakarta EE component class supporting injection.

Expand Down

0 comments on commit 4c4a6ce

Please sign in to comment.