• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

why ejb doesnt run in webserver

 
Ranch Hand
Posts: 689
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i know that webserver supports http protocol and application server supports
multiple protocols like http,ftp,smtp,pop.....
servlet,jsp runs well but why not EJB after it also uses http protocol for transfering data :roll:

thanking you !
 
Java Cowboy
Posts: 16084
88
Android Scala IntelliJ IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
To run servlets (and JSPs, which are compiled into servlets), you need a servlet container. A plain webserver is not enough. Tomcat is an example of a servlet container.

To run EJBs, you need an EJB container. The EJB container provides the environment in which you can deploy EJBs and controls the lifecycle of the EJBs. Tomcat does not include an EJB container, so you can't run EJBs in Tomcat.

It doesn't have anything to do with the protocols that the server supports.
[ July 19, 2006: Message edited by: Jesper Young ]
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The EJB container and the web container each provide some set of services. The designers found a pretty clear line between services that help you build web apps and services that help you build client-agnostic business components, so they put them in two containers.

There's probably some history that a lot of EJB ideas were borrowed from CORBA and COM and Forte 4GL (call them lessons learned) while a lot of web ideas were borrowed from IIS and others.

HTTP is one bit of overlap. I don't think the HTTP service in the EJB container is meant to be public, is it? We only call our EJB container via remote EJB calls and JMS.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic