THIRY, Jean Luc wrote:

> 
> Right, you have to consider all the "normalized" aspects of Java to be
> able to take an application from one platform to another.
> 
> Currently, the java specifications lack a few elements or have defined
> elements without all the details and editors have designed those services
> in a way that they work. As soon as you use application server specific
> feature you loose the portability of an application. As an example in EJB
> 1.1, the deployment descriptor was not normalized so you had to rewrite
> them to deploy them on another application server
> 
> -----Message d'origine-----
> De : Neo Gigs [mailto:gigsvoo@y...]
> Envoye : lundi 21 octobre 2002 10:53
> A : Java 2 Enterprise Edition
> Objet : [j2ee] Re: Applications Servers in J2EE
> 
> 
> raymurphy@g... wrote:
>> I'm just becoming involved in a J2EE project, but our objectives so far
>> will be limited to producing a proof-of-concept .... For political
>> reasons
> 
>> (stemming from implementation of another Java project), the client is
>> committed to using Websphere as the application server. Not having looked
>> at Websphere yet, this in itself is not a concern, but I do have one
>> question about the significance of the choice of application server in a
>> J2EE application - having chosen one specific application server for your
>> application (be it Websphere, WebLogic or whatever ..) how easy would it
>> be to change to another application server later on during your
>> development ?
>> 
>> Thanks.
>> 
>> Ray
>> 
>> 
> 
> Its all depends the architecture and the design of the J2EE application
> you are writting, stick with the standard J2EE specification and you
> need less effort to porting from one J2EE certified server to another.
> 
> 

Hi there,

If we are clear about the J2EE specifications, in common all J2EE certified 
application servers should have obey the rules where those customized 
deployment is a "optional".

For e.g.

In BEA Weblogic, the default J2EE deployment are: web.xml, application.xml, 
ejb-jar.xml, application-client.xml, ra.xml, while the customized for BEA 
Weblogic are: weblogic.xml, weblogic-ejb-jar.xml, 
client-application-runtime.xml and weblogic-ra.xml

As far as I concerned that most of the vendors do have a support 
documentation for 2 sets of J2EE and vendor-specific deployment files.



-- 
Thanks,

Neo Gigs
"Follow the white rabbit..."