To respond to the question of what an .ear or Enterprise Archive was:
It is part of the J2EE specification that encapsulates the .war ( Web
Archive ), the EJB .jar, and Client .jar.
The hierarchy is as follows: EAR can contain multiple .WAR and EJBjar and
.car (Client jar).
The naming convention can differ slightly, but the essence should be the
same.
This allows a single file to be deployed to migrate all components of a
J2EE application.
-Adam
ROSSEL Olivier
<olivier.rossel@a To:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
irbus.com> cc:
Subject: RE: Cocoon and J2EE
06/12/02 09:57 AM
Please respond to
cocoon-users
> OK, I see. Thank you Olivier.
>
> Finally if I want the basic stuff I need cocoon.jar (and
> others? Do you exist a description list of the additionnal
> libraries?) in my "something.war" (or cocoon.war).
> But do you have to include this cocoon.war in each Enterprise
> ARchive??
>
> Thank you
> Sylvain
I think that the jars in wikiland.war (minus chaperon.jar) are
the basic stuff.
I do not know what a Entreprise Archive is, but in any .war you make
you need all the .jars of Cocoon.
A .war is a hermetic context, with its own classes.
If a .ear is (simply) an enhanced .war, then in any .ear that will embed
Cocoon, you need
to put all the .jar.
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
