axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srinath Perera" <hemap...@gmail.com>
Subject Re: Getting axis2 transport out from the kernel
Date Thu, 11 Oct 2007 13:39:31 GMT
Big big +1 ...

I strongly feel we need to reduce the number of Jars and actually
tried to voice it few times before.

To me, axis2-core.jar and axis2-optional.jar is enough for axis2 jars.
Of course we can keep the modules as it is and build two jars while
creating the distribution.  We can even build the old list of jars and
put them to maven repositories. But for releases two jars should be
enough.

I am pretty confident no user would going to figure out which jars
among our list of jars are needed for a given use case. It seems ..
even Axis2 developers are losing tack of them now.

My 2 cents
Srinath




On 10/10/07, Eran Chinthaka <chinthaka@opensource.lk> wrote:
> -----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: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
============================
Srinath Perera:
   Indiana University, Bloomington
   http://www.cs.indiana.edu/~hperera/
   http://www.bloglines.com/blog/hemapani

Beauty of style and harmony and grace and good rhythm depend on
simplicity -- Plato

---------------------------------------------------------------------
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