Re: Distribution of production systems??

[Brown Bay]

Hello,

Thanks for the reply. Thanks for the short explanation, I am assuming here
that war is the way to go for me ;) (pardon the pun)

So, that gets me to my second question, should a war created through ant or
java's war utility be able to work on any application server (certified or
not). because the .war i created worked on Tomcat and websphere out of the
box, but did not work on weblogic. shouldnt a .war work on any application
server?

Please let me know your experiences.

Thanks,

Brown.

-

From: "Shapira, Yoav" <[EMAIL PROTECTED]>


Hi,
JARs and WARs and EARs, oh my ;)

A WebApplicationArchive (WAR) contains the files for a web application,
e.g. servlets, JSPs, static files (html, images, libraries, etc.) and so
on, as well as that web application's deployment descriptor (web.xml).

An EAR typically
contains more than a WAR in that it contains EJBs and their libraries,
information, descriptors, etc.  It may also contain other,
server-specific
deployment details.  It is common for an EAR file to contain one or more
WAR files.  An EAR file will have the application descriptor,
application.xml.

Personally, I use Ant's WAR and EAR tasks to create those files.  I'm
sure
other people have their favorites, as some IDEs have built-in support
for
this.

Hope this helps,
Yoav

>-Original Message-
>From: Brown Bay [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, March 21, 2002 9:21 AM
>To: Tomcat Users List
>Subject: Distribution of production systems??
>
>I have an application that is ready to ship and uses basically servlets
and
>JSPs. Our preferred system of choice is Tomcat/Apache, but there might
be
>scenarios where customers would like to choose Websphere or BEA or
. In
>this case we are considering packaging the application as a .war file
and
>sending this accross.
>
>I tried the .war file generated with BEA yesterday and it did not work
,
>but
>the same war file worked with Websphere Studio. So my question is what
are
>the distribution methods that developers out there use to distribute
their
>web applications.
>
>2nd question is what are EAR files and how do they differ from WAR
files.
>
>Thanks in advance.
>
>TP
>
>--
>To unsubscribe:   
>For additional commands: 
>Troubles with the list: 


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 



--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: Distribution of production systems??

[Shapira, Yoav]

Hi,
JARs and WARs and EARs, oh my ;)

A WebApplicationArchive (WAR) contains the files for a web application,
e.g. servlets, JSPs, static files (html, images, libraries, etc.) and so
on, as well as that web application's deployment descriptor (web.xml).  

An EAR typically
contains more than a WAR in that it contains EJBs and their libraries,
information, descriptors, etc.  It may also contain other,
server-specific
deployment details.  It is common for an EAR file to contain one or more
WAR files.  An EAR file will have the application descriptor,
application.xml.

Personally, I use Ant's WAR and EAR tasks to create those files.  I'm
sure
other people have their favorites, as some IDEs have built-in support
for
this.  

Hope this helps,
Yoav

>-Original Message-
>From: Brown Bay [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, March 21, 2002 9:21 AM
>To: Tomcat Users List
>Subject: Distribution of production systems??
>
>I have an application that is ready to ship and uses basically servlets
and
>JSPs. Our preferred system of choice is Tomcat/Apache, but there might
be
>scenarios where customers would like to choose Websphere or BEA or
. In
>this case we are considering packaging the application as a .war file
and
>sending this accross.
>
>I tried the .war file generated with BEA yesterday and it did not work
,
>but
>the same war file worked with Websphere Studio. So my question is what
are
>the distribution methods that developers out there use to distribute
their
>web applications.
>
>2nd question is what are EAR files and how do they differ from WAR
files.
>
>Thanks in advance.
>
>TP
>
>--
>To unsubscribe:   
>For additional commands: 
>Troubles with the list: 


--
To unsubscribe:   
For additional commands: 
Troubles with the list: