]
Kabir Khan updated WFLY-6402:
-----------------------------
Fix Version/s: 11.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many
of these so I am not checking the history properly. From the lastModified date of this
issue it looks like it was done for 11.0.0.Final (I am not caring about alpha/beta etc.
for this exercise). If that is incorrect please adjust as needed.
EJBs accessible too early (spec violation)
------------------------------------------
Key: WFLY-6402
URL:
https://issues.jboss.org/browse/WFLY-6402
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 10.0.0.Final
Reporter: Brad Maxwell
Assignee: Fedor Gavrilov
Labels: downstream_dependency
Fix For: 11.0.0.Final
Attachments: auto-test-reproducer.zip
{code}
EJB 3.1 spec, section 4.8.1:
"If the Startup annotation appears on the Singleton bean class or if the
Singleton has been designated via the deployment descriptor as requiring eager
initialization, the container must initialize the Singleton bean instance during the
application startup sequence. The container must initialize all such startup-time
Singletons before any external client requests (that is, client requests originating
outside of the application) are delivered to any enterprise bean components in the
application.
{code}
Wildlfy does not implement this correctly, and allows calls to other EJBs before a
@Startup @Singleton finishes its @PostConstruct call.
This Jira ticket handles two PR's on WFLY:
https://github.com/wildfly/wildfly/pull/8824 (that is already merged)
and
https://github.com/wildfly/wildfly/pull/8989