I think this is a good idea. There can be a number of optional downloads available from the Axis2 downloads page. I think the two goals wrt restructuring the Axis2 jars should be:
1. Simplifying the install. There are too many jars and it is currently difficult to understand what is required for the client and server. 2. Reducing the size. This follows from the 1 as if I'm not interested in XmlBeans I shouldn't have to have the XmlBeans code installed. Of course in order to keep things simple with a number of optional downloads those downloads need to be clearly documented and marked on the page so users can easily pick what it is they want to download. Lawrence "keith chapman" <[EMAIL PROTECTED]> 10/14/2007 02:54 AM Please respond to [email protected] To [email protected] cc Subject Re: Getting axis2 transport out from the kernel Is there a need for axis2-optional.jar? I'm +1 for axis2-server.jar & axis2-client.jar. I guess keeping the optional jars seperate is better. For example if I want to use xmlBeans dataBinding I should add the axis2-xmlbeans.jar (Instead of having to add axis2-optional.jar). Thanks, Keith. On 10/13/07, Rajith Attapattu < [EMAIL PROTECTED]> wrote: 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/ -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
