[jboss-jira] [JBoss JIRA] (WFLY-6402) EJBs accessible too early (spec violation)

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13349501#comment-13349501 ] 

RH Bugzilla Integration commented on WFLY-6402:
-----------------------------------------------

Petr Penicka <ppenicka at redhat.com> changed the Status of [bug 1310908|https://bugzilla.redhat.com/show_bug.cgi?id=1310908] from VERIFIED to CLOSED

> 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
>         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



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)