+1 on breaking out the war and binary download and slimming down the kit. I would like to keep WS-Security support in the primary Axis2 distro. I think it is very valuable to have this support 'out of the box' as a selling point for Axis, similar to its support of WS-Addressing.
-- Tom Jordahl Macromedia Server Development > -----Original Message----- > From: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] > Sent: Friday, September 30, 2005 1:54 AM > To: [email protected] > Subject: Re: [jira] Updated: (AXIS2-249) Exessive number & size of > filesgenerated from WSDL > > On Thu, 2005-09-29 at 22:33 -0700, Simon Fell wrote: > > Other fun facts & figures, the axis binary download weights in at > > 33Mb, compared to 24Mb for the entire .NET 1.1 runtime installer. > > That's absolutely pathetic and unacceptable :(. > > So let's start pairing this down: > > - let's move the security module to WSS4J and release that separately? > Let folks download that separately (we can point to that too but its not > reasonable to include that in the base) > > - the way we're packaging now, there are 2+ copies of every jar file in > the binary dist: > - one copy in the lib/ directory > - another copy in the webapps/META-INF/lib directory > - for all the security stuff (I was going to say junk but I > restrained > myself ;-)) inside the mar file as well > > - we are also dist'ing 2 copies of all the mars > - one copy in the webapp > - one copy outside the webapp > > I'd like to separate the webapp into a separate download from the base > binary distribution. Can we think of a creative way to package the admin > war separately? > > We need to do some serious refactoring of the build and dist stuff. > > Sanjiva.
