-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tom Jordahl wrote: >> Well the best thing, IMO, is to ship the current http transport >> with the release, by default and let users download others if >> they want to use. > > +1 - The best thing for Axis2 is for the Axis users, not for Synapse. > The fewer jar files the better as well. The core of Axis2 should have > the 'standard' HTTP transport - anything else is just noise to 90+% of > users.
Adding a bit more to this. Recently I tried to write my own service and get it up and running in my IDE with our embedded Axis2 server. I had hard time figuring out which jars to include. This is the same if you try to write a client for Axis2. We have number of modules and we do not know what to use when (at least I do not know) One would suggest me to download an Axis2 release and include *ALL* the jars in that release. Or I can include jars as and when I hit a compile error or runtime ClassnotFoundException. I feel we have too many jars now. I have no problem in maintaining multiple modules, but how about merging proper modules to few jars when we release? What I'd like to see is axis2-server.jar and axis2-client.jar. Then we just have to add other third party jars like commons-etc., and we are good to go. Just my 2 cents. Chinthaka -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHDYIkjON2uBzUhh8RAq2LAJoCyGE3ttul9tVjcKozY0wBnwX+/ACfZSzc quj8AhbMYmZ8hkkU6SSexxE= =9hLp -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
