Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Deploying EJBs

Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,
I've deployed EJBs on Weblogic Server 5.1.0, as Jar files, as well as directory structures. Weblogic's documentation states that it is useful to deploy EJBs as directory structures during development, and as jars in production.
I can see the advantage with using directory structure deployment in development(takes out the additional step to create a jar file). What I don't see is the added advantage a jar file would give us in production. Can you see it? Thanks in anticipation.
Ranch Hand
Posts: 919
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That's a good question. Functionally, the two methods are identical - both will allow you the mechanisms for making your classes available. So I'd say that the advantages of using a jar file for deployment are:
1. It is more convenient for deployment procedures to distribute one jar file than to distribute an entire directory structure.
2. The risks at deployment time are lower, there's no possibility of obscure class files being accidentally moved or removed.
3. You can explicitly state the location of the jar file on the classpath, this offers a deployment flexpoint (you could move the jar file and change the classpath quickly and reliably and it makes it more obvious where these classes are being accessed).
4. The classes are in a reliable re-deployable self-contained form once it is in a jar file. No possibility of missing directories or wayward class files.
Generally, I think that to deploy with a jar file is just so much more manageable, and simpler. And increased simplicity in deployment is always a benefit. Can anyone else think of any other reasons one way or the other?
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic