Help coderanch get a
new server
by contributing to the fundraiser
  • 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
  • Ron McLeod
  • Paul Clapham
  • Devaka Cooray
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Carey Brown
  • Mikalai Zaikin
Bartenders:
  • Lou Hamers
  • Piet Souris
  • Frits Walraven

EJB specifications

 
Ranch Hand
Posts: 63
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I know all the concepts of EJB. But I haven't read EJB specs yet. What I want to know from you is:
1. Are the app deployment specifications the same for every app server.
That is, in Weblogic, I have to use WEB-INF dir which has web.xml folder, and the app root directory has a .war file(for web apps)
If I want to deploy my bean in Websphere, is the directory structure same?
This takes me back to my original question, are there specs by sun as to how to name the directories and deployment descriptors.
2. How easy/tough is it to move my app from one server to another server(in terms ofthe knowledge that I would require. I know that EJBs can be moved from one server to another server without making any changes in the code).
Thanks,
Chandana
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The structure of an .ear is always the same, as is the structure of a .war. However, this does not mean that the applications are portable as such.
First of all, each application server vendor has the option of using a vendor-specific deployment descriptor for a J2EE module, which obviously isn't portable.
Second, there are some differences in how the application interacts with the container. For example, some application servers have some constraints on how a JNDI name should look like. You should take a look at TSS' clustering experiences to see examples of real-life portability issues.
 
Ranch Hand
Posts: 2713
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
One of the other major pains in migrating between Application Servers is the difference in class loading.
 
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Chris is back.
 
Chris Mathews
Ranch Hand
Posts: 2713
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Pradeep Bhat:
Chris is back.


Yes, after an extended sabbatical I have returned! Unlike Lasse, I have made a resolution to spend more time on the Ranch over the next year. Just don't tell my wife or kids!
Thanks for noticing Pradeep... now where is that emoticon for the smiley with a tear in its eye when you need it?
 
Pradeep bhatt
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Chris, I am still waiting for your JMX article?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic