Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Granularity in packing an Enterprise App  RSS feed

 
Sandeep Kumar JakkarajuuuX
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear BigMoose

Hope you have updgraded yourself to JEE 5. I am doing the same.

This email is in reference to the packaging question of an ear.

Should I have the ejb.jar in ejb container and war in webcontainer ?

OR

Should I have the ear !!! with both ejb and war !!!


Please help atleast some hints
 
Bijj shar
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
if you want to deploy on two different server answer is yes Or if you can pack in single ear and deploy on server
 
Maneesh Godbole
Bartender
Posts: 11445
18
Android Eclipse IDE Google Web Toolkit Java Mac Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
SunJava Developer wrote:


Please check your private messages for an important administrative matter
 
Reza Rahman
author
Ranch Hand
Posts: 580
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sandeep,

Unless there is a specific reason to do otherwise, generally an EAR with an embedded WAR and EJB-JAR is the simplest choice. That's how most IDE Java EE 5 project setup wizards (such as the one for Eclipse) operate.

Hope it helps,
Reza
 
Sandeep Kumar JakkarajuuuX
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sir

I am feeling that EJB is somewhat container specific ... doesnt seem to be the Java way !!!

BigMoosse ate my @EJB post !!!
 
Reza Rahman
author
Ranch Hand
Posts: 580
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sandeep,

I don't think any EJB 3 code-base really needs to be container specific. For example, the EJB 3 in Action code has been ported to three application servers and multiple versions of the same application server with no changes to the code (even though JBoss 4.2 is not fully Java EE 5 certified, but JBoss 5 is). I also have EJB 3 clients that use JBoss for development and a commercial application server is production/QA with the same code-base. The only thing that changes is the configuration of application server resources such as data sources. Of course, you can use container-specific features, but I generally have not seen a need to do so.

Can you kindly tell me what makes you think EJB 3 applications are not portable? It would be good to know in order to dispel any future mis-conceptions, whatever choice you are personally inclined to make.

The "Java-way" one could argue is about standards, code portability and being vendor agnostic, which is what EJB 3 is much more towards vis-a-vis some other solutions.

Best regards,
Reza

P.S.: The moderators deleted your post probably because it was not suitable for a moderated forum like JavaRanch. Being moderated generally serves to make all JavaRanch forums a useful place to participate in discussions for everyone IMO. It might be useful to review the tips for asking questions effectively...
 
RaviNada Kiran
Ranch Hand
Posts: 528
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
see deployment of an EJB application . Refer to the tutorials on BEA.This will give you an Idea.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!