enterprise java beans part i n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Enterprise Java Beans Part I PowerPoint Presentation
Download Presentation
Enterprise Java Beans Part I

Loading in 2 Seconds...

play fullscreen
1 / 29

Enterprise Java Beans Part I - PowerPoint PPT Presentation


  • 82 Views
  • Uploaded on

Enterprise Java Beans Part I. Kyungmin Cho 2001/04/10. Agenda. JavaBeans and Enterprise JavaBeans EJB component model EJB Architecture. JavaBeans and Enterprise JavaBeans. Defining E nterprise J ava B eans(1). A server-side component architecture

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Enterprise Java Beans Part I' - wilbur


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
enterprise java beans part i

Enterprise Java BeansPart I

Kyungmin Cho

2001/04/10

agenda
Agenda
  • JavaBeans and Enterprise JavaBeans
  • EJB component model
  • EJB Architecture
defining e nterprise j ava b eans 1
Defining Enterprise JavaBeans(1)
  • A server-side component architecture
  • Model to enable efficient development and deployment of Java applications :
    • Transactional,Portable
    • Distributed,Multi-tier
    • Scalable
    • Secure
defining e nterprise j ava b eans 2
Defining Enterprise JavaBeans(2)
  • EJB is not JavaBeans
  • a Server Component specification for Java
  • Separates business and system programming
  • Portability of business objects
  • Extensibility through vendor features
defining javabeans 1
Defining JavaBeans(1)
  • A client-side component architecture
  • Portable, platform-independent component model written in the java programming language
  • Acts as a bridge between proprietary component models
  • Provides a seamless and powerful means for developers to build components that run in ActiveX container applications
javabeans vs enterprise javabeans 1
JavaBeans

Can be either visible or non-visible

Client > Server

Java.bean.*

Intra-processor

Easier to develop than EJB

EJB

Are decidedly non-visible, remote objects

Server

Javax.ejb.*

Inter-processor

More difficult to develop than JavaBeans

JavaBeans Vs. Enterprise JavaBeans(1)
javabeans vs enterprise javabeans 2
JavaBeans Vs. Enterprise JavaBeans(2)

Server

Enterprise information

Services

Client

Java Beans

Container

Java Beans

EJB1

Database

Java Beans

Existing

application

EJB2

Client

Java Beans

EJB3

Server manages

resources such

as threads,

connection pooling,

caching, and

state management

Java Beans

agenda1
Agenda
  • JavaBeans and Enterprise JavaBeans
  • EJB component model
  • EJB Architecture
what is component
What is component?
  • Components are made by assembling objects.
component system
Component System
  • Component system is fundamental for assembling and managing components.
client component
Client component
  • Component = button, list, spread sheet, etc.
  • Container = window, form, etc.
server component 1
Server component(1)
  • Component
    • Interface is separated from implementation.
  • Container
    • Manages message-passing between client and component
    • Automatically carry out standard infrastructure services such as transaction and security, etc.
agenda2
Agenda
  • JavaBeans and Enterprise JavaBeans
  • EJB component model
  • EJB Architecture
  • What can we do with EJB?
ejb design goals
EJB Design Goals
  • Simplify development/deployment of distributed applications
  • Achieve broad industry acceptance
  • The right expert focuses on the right job
  • Platform independent and protocol neutral
  • Enable development of portable components - Truly enable reuse
what is special about ejbs
What Is Special About EJBs?
  • Learn once
  • Write Once, Run Anywhere TM
  • Portable and interoperable
  • Flexible and extensible
  • Scalable
  • Easier to write distributed applications
  • Transaction management
  • CORBA compatible
ejb architecture roles
EJB Architecture Roles
  • Bean provider
  • Container provider
  • Server provider
  • Application assembler
  • Deployer
  • System administrator
ejb component feature 1
EJB component feature(1)
  • Include business logic
  • Produce and manage instance at run time
  • Can be customized by editing environment entry.
  • Service information is separated from EJB class. This makes Service information to be managed by tools when assembling and deploying application.
  • Client can access EJB through container.
ejb component feature 2
EJB component feature(2)
  • If EJB uses services which are defined in EJB specification, EJB can be deployed in all EJB containers.
  • EJB don’t need recompiling and editing source code.
ejb server 1
EJB Server(1)
  • Provides System Services
    • Transaction support
    • Database access
    • System resource
    • Namespace
  • Implementations
    • Middleware servers
    • Application servers
    • Database servers
ejb server 2
EJB Server(2)
  • Supplies containers for EJBs
  • API between server and container is currently vendor specific
  • Server could provide several container

types to provide various extended

services to different beans

ejb container 1
EJB container(1)
  • Currently provided by EJB Server
  • EJB access to server resource through standard API
  • May Contain one or multiple classes
  • Tools for EJB creation and deployment
ejb container 2
EJB container(2)
  • Some standard services
    • Persistence
    • EJB instance creation & location
    • Namespace
    • Transaction control
    • Swapping
    • Security
  • Custom services
    • Application-specific
    • Bridge to existing systems