Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (athena.apache.org: domain of donald.brown@gmail.com
 designates 216.239.58.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=wEGg2sW2Oh55G5KbJAj5lr4lxFAI9McaptoZQpket6mJconcsg/V4VY5jgUAFReilT
         fgF/Xvokrj0TAeKOeUeCWKT/bMeiBqK7AOKo2inIlwfadvVWg/LEdWhNomZ8sq0tGliV
         zvA4I0xijtckz+VYS/1gDSEtT9GBrRIk17T8g=
Message-ID: <1c661f2f0807140048x5a3fffeci94362ca3a7faeb43@mail.gmail.com>
Date: Mon, 14 Jul 2008 17:48:56 +1000
From: "Don Brown" <donald.brown@gmail.com>
To: "Struts Developers List" <dev@struts.apache.org>
Subject: Re: [s2] Struts 2 OSGi Plugin
In-Reply-To: <aae96ca0807140042w4071151ft321f08535d51ea86@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <436d9a250707290742i4d4aaa67ibbd991f4140591eb@mail.gmail.com>
	 <436d9a250707291702p6ee3b0ake72cc85ea47ba6c4@mail.gmail.com>
	 <18415829.post@talk.nabble.com>
	 <d8bdeb6f0807112144v3891f3e9hf1c04691bc9a7c0e@mail.gmail.com>
	 <1c661f2f0807112351n6eef6ebduba97439c80009658@mail.gmail.com>
	 <18435680.post@talk.nabble.com>
	 <436d9a250807132245l25ac3e54vfeeea4283ae289b@mail.gmail.com>
	 <aae96ca0807140031p211d4de9wa40ad2c5d07739e@mail.gmail.com>
	 <1c661f2f0807140035g213d17a6kccc86f114c86282@mail.gmail.com>
	 <aae96ca0807140042w4071151ft321f08535d51ea86@mail.gmail.com>

Well, at least in my experience so far, for libraries, it is usually
enough to take the default manifest, if there is a version of the jar
available that has one, but for frameworks, you may want to customize
exactly what packages are depended upon and, more importantly, what
dependencies are bundled in the jar.  For example, for the Struts 2
bundle, I wanted XWork, OGNL, Freemarker, and several Struts 2 plugins
in the bundle, so I ended up constructing my own bundle with its own
OSGi headers.  Freemarker just wasn't working, for whatever reason,
when deployed as its own bundle, and packaging the rest of the deps
into the struts bundle made deployment a lot easier.  I've found if
you can reduce the number of bundles you deploy, the less complicated
your life will become.

That said, adding OSGi manifest entries to your library would
certainly be appreciated.

Don

On Mon, Jul 14, 2008 at 5:42 PM, Antonio Petrelli
<antonio.petrelli@gmail.com> wrote:
> 2008/7/14 Don Brown <donald.brown@gmail.com>:
>> Actually, that bit isn't a problem - we could bundle the tiles jars in
>> the struts 2 tiles plugin and generate the manifest for both
>> automatically.
>
> Sorry for the dumb question, but does "bundling" mean "decompress and
> recompress together"? IMHO it's easier to add a bunch of lines in the
> manifest of Tiles jars than decompressing and recompressing jars.
> I suppose it's not difficult, so probably it could be added in Tiles
> 2.0.7 (the latest version is 2.0.6).
>
> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org