Best practices recommend entity beans for data access and session beans as frontline controllers between the Web tier and business tier or between the client tier and the business tier, depending on the type of application. Business logic should be implemented with session beans and/or plain old Java objects (POJOs). If you will be receiving asynchronous messages within your workflow framework, message-driven beans are very effective and highly recommended. With this in mind, the following chart loosely illustrates the interactions between these components:
Browser <--> Servlet <--> Stateless Session Bean <--> Entity Bean <--> Data
Swing App <--> Stateful Session Bean <--> Entity Bean <--> Data
App <--> Session Bean <--> Message-Driven Bean <--> Message Store
Dig deeper on Java Web Services
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.