Why we are not keeping Ejb class file in war

Showing Answers 1 - 4 of 4 Answers

Padam

  • Jul 19th, 2006
 

EJB runs on the application server, and war runs on your web server, that the main reason we do not put ejb classes in war file.

  Was this answer useful?  Yes

Srinivas Gorityala

  • Aug 11th, 2006
 

Ejb Application is not a web application,it is an enterprise application which contains

Heavy business component,it shouldnot be able to run on web servers,because web servers are not providing middleware services like transactions,security etc...

so war extesion indicates web application archive,so ejb application should contain jar extesion only.

  Was this answer useful?  Yes

Anuj Kumar Ratra

  • Sep 8th, 2006
 

Deep down all files EAR WAR JAR are zip files just to differentiate their deployment they are grouped with different extensions

Jar for Java file

War for web acrhives jsp and servlets

ear for ejbs

James Samuel

  • Oct 27th, 2006
 

Ejb classes or business components are packaged together and called jar files which are part of the business layer in the runtime. These reside on Application Server. Whereas war modules consists of all presentation components like(html,ccs,jsp,servlets,all markups etc.) These are part of the presentation and run on the webcontainer which is vendor's specific webserver like (javawebserver,tomcat,httpserver,apachewebserver etc). If you are deploying on a full fledged Application server like WebSphere, Weblogic. Dont even worry about webservers its inside the Appserver.When u deploy the application the web component is deployed to the webcontainer and the business component ie.. jar to the ejb container.Hope it helps...

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions