Just to recap the conversation so far, there seems to be about 3 approaches.
Option1 ----------- axis2-server.jar & axis2-client.jar Option2 ----------- axis2-core.jar & axis2-optional.jar Option3 sort of a hybrid ------------ axis2-server.jar & axis2-client.jar and axis2-optional.jar. We could also have slipt the optional jar into sever and client, but I think we could get away without doing that. Did I miss anything else? Regards, Rajith On 10/12/07, Tom Jordahl <[EMAIL PROTECTED]> wrote: > > 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:[EMAIL PROTECTED] > Sent: Friday, October 12, 2007 1:07 AM > To: [email protected] > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Rajith Attapattu Red Hat Blog http://mutlix.blogspot.com/
