Adrian Baker wrote:
Undersood : how about offering an option to build a jar version of the
ChibaServlet module, in addition to the default war output ?
why not - go ahead - make a suggestion. think you won't use ChibaServlet?
I could then simply include both chiba.jar & chiba-servlet.jar in my
application.
right.
-----Original Message-----
From: Joern Turner [mailto:joern.turner-S0/GAf8tV78@xxxxxxxxxxxxxxxx]
Sent: Friday, 18 March 2005 1:47 p.m.
To: Adrian Baker
Cc: chiba-developer
Subject: Re: [Chiba-developer] separating the core of Chiba
Adrian Baker wrote:
Good idea : as long as it remains easy to build a jar (not a war)
which has some/all of the web classes in it (perhaps by leaving a
build-jar option in the ChibaServlet package?).
there won't be so much options left for building the chiba.jar. by
default, it'll contain all core tools and connectors, so if you're
needing a special build you can download the core and build
it yourself.
chiba-servlet module won't contain the core sources any more but only
the 'web' package so (re-)packaging chiba.jar here seems misplaced.
Joern
Currently we create a jar using the build-chiba-jar, but because we
reuse the ServletAdapter rather than just the bean, we have tweaked
the excludes.properties to include it along with the non-web Chiba
core classes.
Adrian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
|
