Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <28655173.post@talk.nabble.com>
Date: Mon, 24 May 2010 02:36:25 -0700 (PDT)
From: zm <zzzz_mmmm@hotmail.com>
To: users@maven.apache.org
Subject: Re: Maven EAR + EJB ... jars with prefixed "lib/" except for EJB
In-Reply-To: <63ADC1A8-1AC7-49D0-9F14-EC30321FD4DA@resolvesw.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <28618592.post@talk.nabble.com> <4BF6792D.20007@ObjectWay.it>
 <63ADC1A8-1AC7-49D0-9F14-EC30321FD4DA@resolvesw.com>


Stephen Coy-3 wrote:
>=20
> On 21/05/2010, at 10:14 PM, Nicola Musatti wrote:
>=20
>> Are you sure about this? I'm asking because this is not the behaviour I'=
m
>> seeing for a WAR deployed to Websphere 7.0.0.7. In order for the
>> containing EAR's jar's to be visible from the WAR I have to specify them
>> explicitly in the WAR's manifest.
>=20
>=20
> From "JavaTM Platform, Enterprise Edition (Java EE) Specification, v5"
>=20
> EE.8.2.1=09Bundled Libraries
>=20
> 1. ...
>=20
> 2. A .ear file may contain a directory that contains libraries packaged i=
n
> JAR files. The library-directory element of the.earfile=E2=80=99s deploym=
ent
> descriptor contains the name of this directory. If a library-directory
> element isn=E2=80=99t specified, or if the .ear file does not contain a d=
eployment
> descriptor, the directory named lib is used. An empty library-directory
> element may be used to specify that there is no library directory.
> All files in this directory (but not subdirectories) with a .jar extensio=
n
> must be made available to all components packaged in the EAR file,
> including application clients. These libraries may reference other
> libraries, either bundled with the application or installed separately,
> using any of the techniques described herein.
>=20
> 3. A web application may include libraries in the WEB-INF/lib directory.
> See the Servlet specification for details. These libraries may reference
> other libraries, either bundled with the application or installed
> separately, using any of the techniques described herein.
>=20
> The usual reason for this not working is using an old (J2EE 1.3 or 1.4)
> DTD/schema in the application.xml file.
>=20
> Cheers,
>=20
> Steve C
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>=20
>=20
>=20

Perfect, that was exactly what I was thinking, that the specification shoul=
d
define this.

This eases the work of making a cross-application-server EAR archive. Also
not needing the manifest entries makes it more easy to maintain the pom
files for maven.

We have so much stuff to worry about, that these small definitions help
alot.

I'll definitely try it on JBoss, WebSphere and Geronimo to check it out

Thanks.


Note about posting: I post in nabble.com, this time I'll post using Interne=
t
Explorer.
--=20
View this message in context: http://old.nabble.com/Maven-EAR-%2B-EJB-...-j=
ars-with-prefixed-%22lib-%22-except-for-EJB-tp28618592p28655173.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org