[jboss-jira] [JBoss JIRA] (WFLY-5097) @Startup @Singleton Beans Constructed Multiple Times

[ https://issues.jboss.org/browse/WFLY-5097?page=com.atlassian.jira.plugin.... ] Yeray Santana Borges edited comment on WFLY-5097 at 2/13/16 3:49 PM: --------------------------------------------------------------------- After checking this issue, the error is generated because @Singleton and @Stateful were used in the same EJB class. In the attached test file (singleton.zip), the class ApplicationStoreBean.java was annotated with @Singleton and @Stateful. This is a violation of EJB specification as described in section 4.1: A session bean may be either: * stateless—the session bean instances contain no conversational state between methods; any instance can be used for any client. * stateful—the session bean instances contain conversational state which must be retained across methods and transactions. * singleton—a single session bean instance is shared between clients and supports concurrent access. If @Stateless annotation is removed, the issue is not reproduced. After discuss this issue in hipChap, it makes sense adapt the server to avoid these kind of deployments if the point 4.1 is violated. was (Author: yersan): After checking this issue, the error is generated because @Singleton and @Stateful was used tin the same EJB class. In the attached test file (singleton.zip) the class ApplicationStoreBean.java was annotated with @Singleton and @Stateful. This is a violation of EJB specification as described in section 4.1: A session bean may be either: * stateless—the session bean instances contain no conversational state between methods; any instance can be used for any client. * stateful—the session bean instances contain conversational state which must be retained across methods and transactions. * singleton—a single session bean instance is shared between clients and supports concurrent access. If @Stateless annotation is removed, the issue is not reproducced. After discuss this issue in hipChap, it makes sense adapt the server to avoid these kind of deployments if the point 4.1 is violated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)