1 / 11

Session Beans

Session Beans. February 2010 – August 2010 Eric.gerlofsma@hu.nl www.ericgerlofsma.nl. History. EJB 1.0 released march 1998 EJB 1.1 (J2EE 1.2) 1999 Session Beans ( stateless & stateful), Entity Beans Remote Interface EJB 2.0 (J2EE 1.3) 2001 Message-Driven Beans Entity 2.x and EJB QL

thea
Télécharger la présentation

Session Beans

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Session Beans February 2010 – August 2010 Eric.gerlofsma@hu.nl www.ericgerlofsma.nl

  2. History • EJB 1.0 released march 1998 • EJB 1.1 (J2EE 1.2) 1999 • Session Beans ( stateless & stateful), Entity Beans • Remote Interface • EJB 2.0 (J2EE 1.3) 2001 • Message-Driven Beans • Entity 2.x and EJB QL • Local and Remote interfaces • EJB 2.1 (J2EE 1.4) 2003 • EJB Timer Service • Minor EJB QL enhancements • EJB 3.0 (J2EE 1.5) 2005

  3. Contents • Why do we need a SessionBean? • What is a Stateless SessionBean? • What is a Stateful SessionBean? • What was wrong with the 2.1 architecture?

  4. Why do we need a SessionBean?

  5. We created JSF Web Applications. Browser JBOSS ABC-BANK Browser ABC-Library Internet Browser ABC-Pizza

  6. JSP library Deployment files JSP JSP JSP JSP JSP JSP web.xml faces-config.xml jboss-web.xml Security module JAAS Backing Bean library Domain module JSP JSP JSP JSP JSP Bean ABC-BANK.jar A Web Applications looks like this.

  7. Are we completely satisfied? • The domain module is integrated by JBoss in the JSF Web Application. • The domain module is self supporting for: • Security, • Queueing Banking Transactions, • Maintaining Database Transactions

  8. Or do you prefer a container that: • Separates the domain module from the JSF Web Application. • And supports service for: • Security, • Queuing Banking Transactions, • Maintaining Database Transactions

  9. How do you separate front-end from back end? MySQL JBoss HTTP: 8080 JNDI : 1099 JMS : JBoss HTTP: 8080 Browser Internet Internet ABC-BANK JSF ABC-BANK DOMAIN Session Beans Entity Beans In JBoss the EJB Container JSP’s Backing Beans In Tomcat the Servlet Container RMI

  10. Why a physical separation of front-end and back end? MySQL JBoss HTTP: 8080 JNDI : 1099 JMS : Browser Internet ABC-BANK JSF ABC-BANK DOMAIN Session Beans Entity Beans JSP’s Backing Beans RMI

  11. What is a SessionBean? • SessionBeans are general remote RMI Servers implementing the business logic and providing an interface to the business tier. • SessionBeans are transaction managers for accessing Entity Beans. • SessionBeans are called by the EJB-Container if it is allowed by the Security Manager. • Session Beans are automatically registered in a JNDI (Java Naming and Directory Interface); this is some kind of rmiregistry. • There are 2 kinds of SessionBeans, Stateless and Stateful. • SessionBeans have nothing to do with HTTP-Sessions.

More Related