axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Jordahl" <tjord...@adobe.com>
Subject RE: Getting axis2 transport out from the kernel
Date Fri, 12 Oct 2007 19:46:53 GMT
So I think we have swung around to the topic: "Reduce the number of
axis2 jars to 2".

I am firmly in favor of that.  The HTTP transport should be in core, all
the others should be in optional.  

I would be even happier if we had the axis2-client.jar and
axis2-server.jar setup.  This would make it crystal clear to users what
is what.  Perhaps axis2-client-full.jar and axis2-client-slim.jar.

But in any case, 19 jars is way too many so moving the transports out to
create another one seems out of the question given the direction this
discussion is moving.

--
Tom Jordahl

-----Original Message-----
From: Lawrence Mandel [mailto:lmandel@ca.ibm.com] 
Sent: Friday, October 12, 2007 1:07 AM
To: axis-dev@ws.apache.org
Subject: Re: Getting axis2 transport out from the kernel

+1

I actually posted a question about all of the jars included in the Axis2

distribution on the users list today. (See 
http://marc.info/?l=axis-user&m=119214746432551&w=2) I counted 19 Axis2 
jars and 39 third party jars included in the 1.3 distribution. This
seems 
like an incredible number of jars for users (like me) to make sense of.

Lawrence 




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


Mime
View raw message