This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
All, As a beginner in Java programming I am often confused by the use of Java Beans and Enterprise Java Beans. My undestanding is that EJB's are used as a business layer (contains the business logic) in web applications or enterprise development. Java Beans alone are more reusable blocks of code typically for Graphical display - applets. Will this new book (this week's give away) address these differences. All opinons and suggestions are welcome. Thanks Jawahar
A JavaBean doesn't HAVE to be associated with a graphical component - it just has to represent an object that has properties. EJB's carry that step further in that they provide basic JavaBean functionality with support for transaction management, safe use in a multi-threaded environment and built-in support for object persistency (in the case of Entity EJBs). The overhead to setup and maintain EJBs (not to mention the effort to create them) is significantly higher than for simple JavaBeans. On the other hand, if you NEED the kinds of functionality that EJBs provide, EJBs give a pre-debugged framework in which to operate so you don't have to re-invent it all.
Customer surveys are for companies who didn't pay proper attention to begin with.