Will the kernel every be used separately from the server and client? If 
not, how about rolling that into these two artifacts and reducing the 
count one more to four?

1. Axis2 Server
2. Axis2 Client
3. Tools
4. Optional

Lawrence




"Amila Suriarachchi" <[EMAIL PROTECTED]> 
10/29/2007 01:20 AM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: [Axis2] Axis2 Release Restructuring






hi,

As I understood we are going to shift the Axis2 as five sperate artifacts.

1. Kernal
2. Axis2 Server
3. Axis2 Client
4. Tools
5. Optional

what are the things we going to shift on each module? to which modules we 
are going to put other jars? 
(i.e axiom, neethi, common jars)

Does Axis2 server and Axis2 Client supposed to have only the Runtime jars? 
In user list I saw lot of people ask 
this question. What is the minimal set of jars needed at runtime? 

adb-codegen and codegen modules are not used in runtime. I think they 
should also goes to the 
tools package. And also java2wsdl is only used in Serverside I think. 

why you have put the samples to the kernal distribution? 

what about the jaxws, fastinfoset. mex etc are we going to put them all to 
optional package?

Actually how are we going to define the content of Axis2 server and 
client? if I say the content of the 
1. Axis2 Server as 
the minal set of jars needed to deploy a service written using the 
RawXmlMessageReceiver

and the Axis2 client as 
the minmal set of jars needed to invoke that service using Service Client 
interface?

Thanks, 
Amila.

On 10/29/07, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Along with the discussion on various mail threads to restructure Axis2
distributables, I looked at the modules and this is what I came up with.
Axis2 gurus and experts please comment on the modules as you know better 
than me.

Both Axis2 Server and Client distributions will have the following
modules included. We can name this as Axis2-Kernel distribution and make
it one distro. (do not get confuse this with kernel module) 

- adb
- adb-Codegen
- addressing
- codegen
- java2wsdl
- kernel
- samples

We will have a tools and optional package distributions separately or we
will have them as one single distribution. 
What I am really interested in is the kernel distribution and a
distribution which has all the modules.

I purposely didn't consider other databinding frameworks. Let the user
get them if he wants or get the full distro. 

Please add your comments and thoughts here.

Thanks,
Chinthaka


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHJVmvjON2uBzUhh8RAjwfAJ4iZg798WyCFcP2Ucc+5GTNMTRiLQCfXlmt
4Pmg8OBMSLrBU9bniuEgJw0=
=bnB0
-----END PGP SIGNATURE-----

--------------------------------------------------------------------- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED] 




-- 
Amila Suriarachchi,
WSO2 Inc. 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to