Some projects have all data twice. Once as domain objects, and once as data transfer objects. This duplication has a huge cost, so the architecture needs to get a huge benefit from this separation to be worth it.
The @EJB is used to inject EJB’s only and is available for quite some time now. @Inject can inject any managed bean and is a part of the new CDI specification (since Java EE 6). In simple cases you can simply change @EJB to @Inject. In more advanced cases (e.g. when you heavily depend on … Read more
Why really use them? (Why not just stick to POJO?) IF you need a component that accesses the database, or accesses other connectivity/ directory resources, or is accessed from multiple clients, or is intended as a SOA service, EJBs today are usually “bigger, stronger, faster (or at least more scalable) and simpler” than POJOs. They … Read more
(Updated Feb 2022) First of all, “Java EE” has since Sep 2019 been renamed to “Jakarta EE“, starting with version 8. Historically, there was also the term “J2EE” which covered versions 1.2 until 1.4. The term “Java EE” covered versions 5 until 8. See also Jakarta EE, History on Wikipedia. Is Jakarta EE just a … Read more
I’m very new to Java EE and I’m trying to understand the concept of Local interfaces and Remote interfaces. In the initial versions of the EJB specification, EJBs were “assumed” to be remote components and the only way to invoke them was to make a remote call, using RMI semantics and all the overhead it … Read more