In EJB 3.1, now you do not need to define any interfaces for Session Beans, just like JPA Entities and Message Driven Beans.
In EJB 3.1, now you do not
need to define any interfaces for Session Beans, just like JPA Entities and
Message Driven Beans. All you have to do is annotate a POJO with the @Stateless
or @Stateful to get a fully functional EJB.
- The Singleton Beans A new feature of
Singleton Beans is added in EJB 3.1 that is used to store application-wide
shared data. The JEE container maintains a single shared instance of an EJB
3.1 Singleton that can cache state across the application
tier. Like all other EJBs, Singletons are simply annotated POJOs.
- Support for direct use of EJBs in the servlet
container, including simplified packaging options. Like the web.xml file
that resides in the WEB-INF directory, you would be able to place an EJB jar into the WEB-INF/lib directory.
- Support for stateful web services via
Stateful Session Bean web service endpoints.