You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by Amila Suriarachchi <am...@gmail.com> on 2007/10/29 06:20:24 UTC

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 <ch...@opensource.lk> 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: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>

-- 
Amila Suriarachchi,
WSO2 Inc.

Re: How control the service remotely

Posted by keith chapman <ke...@gmail.com>.

Why are you creating a new configuration context?. Thats the fault. Take a
look at org.wso2.wsas.admin.service.AxisConfigAdmin in the admin module. It
takes the configContext as
AxisConfiguration axisConfiguration =
                MessageContext.getCurrentMessageContext()
                        .getConfigurationContext().getAxisConfiguration();

Thanks,
Keith.

On 11/7/07, neo qing <ne...@msn.com> wrote:
>
>
> Hi Keith:
>             I read some sources of WSO2 WSAS and I find a class can help
> me,I write down like below:
>
> ConfigurationContext configContext=
> ConfigurationContextFactory.createConfigurationContextFromFileSystem
> ("C:\\wso2\\repository","C:\\wso2\\conf\\axis2.xml");
>   AxisService service=configContext.getAxisConfiguration
> ().getService("echo");
>   service.setActive(true);
>
> I run it with JUnit, the result is OK,but I return to the console,I find
> that the status of the service has not been changed!
> who can help me on this?
> thanks!
>
> ------------------------------
> Date: Tue, 6 Nov 2007 14:17:53 +0530
> From: keithgchapman@gmail.com
> To: axis-dev@ws.apache.org
> Subject: Re: How control the service remotely
>
> WSO2 WSAS manages services via deployed admin services. Its an open source
> project so you can take a dip and have a look at it. Please have a look at
> the admin module cause thats what will interest you.
>
> You can see details of the project here http://wso2.org/projects/wsas/java
>
> And also access the source code there.
>
> Thanks,
> Keith.
>
> On 11/6/07, *neo qing* <ne...@msn.com> wrote:
>
> Hi everyone:
>              I want to control the service that deployed in the servlet
> container with AXIS2, such as, list the services,stop,start the
> service,currently I take a unstable approache that I post a request like
> 'axis-admin/deactive' to the target server, mostly it is available but I do
> not think it is a good idea.
>              I have read the source of AXIS2, I find a class named "
> org.apache.axis2.transport.http.AdminAgent", it can manage the service,but
> it use a method like below
>
> ConfigurationContext  configContext =
> ConfigurationContextFactory.createConfigurationContext(new
> WarBasedAxisConfigurator(config));
>
> ………………
>
> AxisService service = configContext.getAxisConfiguration().getServiceForActivation(
> serviceName);
>                 service.setActive(true);
>
> the variable 'config' is a instance of ServeletConfig
>
> but I do not want to bind the function to the container because I want to
> expose the function as a web service.
>
> the question is :How can I get the AxisConfiguration instance and not
> depend on the ServerletConfig?
>
> or you can give me another good idea about how to control the services
> remotely?
> thanks !
>
> Any reply is appreciation!
>
>  neo
>
> ------------------------------
> Discover the new Windows Vista Learn more!<http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE>
>
>
>
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.
> http://wso2.org/
>
>
> ------------------------------
> Discover the new Windows Vista Learn more!<http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE>
>



-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

RE: How control the service remotely

Posted by neo qing <ne...@msn.com>.

Hi Keith:
            I read some sources of WSO2 WSAS and I find a class can help me,I write down like below:
ConfigurationContext configContext=ConfigurationContextFactory.createConfigurationContextFromFileSystem("C:\\wso2\\repository","C:\\wso2\\conf\\axis2.xml");  AxisService service=configContext.getAxisConfiguration().getService("echo");  service.setActive(true);
 
I run it with JUnit, the result is OK,but I return to the console,I find that the status of the service has not been changed!
who can help me on this?
thanks!


Date: Tue, 6 Nov 2007 14:17:53 +0530From: keithgchapman@gmail.comTo: axis-dev@ws.apache.orgSubject: Re: How control the service remotelyWSO2 WSAS manages services via deployed admin services. Its an open source project so you can take a dip and have a look at it. Please have a look at the admin module cause thats what will interest you.You can see details of the project here http://wso2.org/projects/wsas/javaAnd also access the source code there.Thanks,Keith.
On 11/6/07, neo qing <ne...@msn.com> wrote: 

Hi everyone:             I want to control the service that deployed in the servlet container with AXIS2, such as, list the services,stop,start the service,currently I take a unstable approache that I post a request like 'axis-admin/deactive' to the target server, mostly it is available but I do not think it is a good idea.              I have read the source of AXIS2, I find a class named "org.apache.axis2.transport.http.AdminAgent", it can manage the service,but it use a method like below ConfigurationContext  configContext = ConfigurationContextFactory.createConfigurationContext(new WarBasedAxisConfigurator(config)); ……………… AxisService service = configContext.getAxisConfiguration().getServiceForActivation(serviceName);                service.setActive(true); the variable 'config' is a instance of ServeletConfig but I do not want to bind the function to the container because I want to expose the function as a web service. the question is :How can I get the AxisConfigu
 ration instance and not depend on the ServerletConfig? or you can give me another good idea about how to control the services remotely?thanks ! Any reply is appreciation!  neo

Discover the new Windows Vista Learn more! -- Keith ChapmanWSO2 Inc.Oxygen for Web Services Developers.http://wso2.org/ 
_________________________________________________________________
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

Re: How control the service remotely

Posted by keith chapman <ke...@gmail.com>.

WSO2 WSAS manages services via deployed admin services. Its an open source
project so you can take a dip and have a look at it. Please have a look at
the admin module cause thats what will interest you.

You can see details of the project here http://wso2.org/projects/wsas/java

And also access the source code there.

Thanks,
Keith.

On 11/6/07, neo qing <ne...@msn.com> wrote:
>
>  Hi everyone:
>              I want to control the service that deployed in the servlet
> container with AXIS2, such as, list the services,stop,start the
> service,currently I take a unstable approache that I post a request like
> 'axis-admin/deactive' to the target server, mostly it is available but I do
> not think it is a good idea.
>              I have read the source of AXIS2, I find a class named "
> org.apache.axis2.transport.http.AdminAgent", it can manage the service,but
> it use a method like below
>
> ConfigurationContext  configContext =
> ConfigurationContextFactory.createConfigurationContext(new
> WarBasedAxisConfigurator(config));
>
> ………………
>
> AxisService service = configContext.getAxisConfiguration
> ().getServiceForActivation(serviceName);
>                 service.setActive(true);
>
> the variable 'config' is a instance of ServeletConfig
>
> but I do not want to bind the function to the container because I want to
> expose the function as a web service.
>
> the question is :How can I get the AxisConfiguration instance and not
> depend on the ServerletConfig?
>
> or you can give me another good idea about how to control the services
> remotely?
> thanks !
>
> Any reply is appreciation!
>
>  neo
>
> ------------------------------
> Discover the new Windows Vista Learn more!<http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE>
>



-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

How control the service remotely

Posted by neo qing <ne...@msn.com>.

Hi everyone:
             I want to control the service that deployed in the servlet container with AXIS2, such as, list the services,stop,start the service,currently I take a unstable approache that I post a request like 'axis-admin/deactive' to the target server, mostly it is available but I do not think it is a good idea.
             I have read the source of AXIS2, I find a class named "org.apache.axis2.transport.http.AdminAgent", it can manage the service,but it use a method like below
 
ConfigurationContext  configContext = ConfigurationContextFactory.createConfigurationContext(new WarBasedAxisConfigurator(config));
 
………………
 
AxisService service = configContext.getAxisConfiguration().getServiceForActivation(serviceName);                service.setActive(true);
 
the variable 'config' is a instance of ServeletConfig
 
but I do not want to bind the function to the container because I want to expose the function as a web service.
 
the question is :How can I get the AxisConfiguration instance and not depend on the ServerletConfig?
 
or you can give me another good idea about how to control the services remotely?
thanks !
 
Any reply is appreciation!
 
 neo
_________________________________________________________________
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

Re: [Axis2] Axis2 Release Restructuring

Posted by Afkham Azeez <af...@gmail.com>.

On Oct 30, 2007 3:44 PM, Amila Suriarachchi <am...@gmail.com>
wrote:

>
> I have misunderstood the thing.
> you mean
> 1. minimal distribution with
>        server,client and kernal
> 2. full distribution with
>        minmal + optional
> 3. Tools distribution with
>        tools
>

Didn't we have something similar  earlier, before Axis2 1.0 I think. We
merged it into a single distribution later on since it is a big hassle to
manage many distros. I am not in favor of going for multiple distributions
since we've gone through the pain of managing them before.

>
>
> --
Thanks
Afkham Azeez

http://www.wso2.org
GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760

Re: [Axis2] Axis2 Release Restructuring

Posted by Lahiru Sandakith <sa...@gmail.com>.

Hi Amila,

please see my comment below,

On 11/2/07, Amila Suriarachchi <am...@gmail.com> wrote:
>
>
>
> On 11/1/07, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> >
> > Hi Amila,
> >
> > 1. From what I read I thought one of the issues (and an issue that I
> > raised) was the large number of Axis2 jars. I understood from the
> > conversation that's been taking place that the function in the many Axis
> >
> > jars would be rolled up into 3 (or 5) jars, not 3 zip (or tar, etc.)
> > distros containing many jar files.
>
>
> So you talking about the rolling axis2 jars into smaller number of jars.
> As chinthaka has told in here
> you want to roll all the axis2 jars into axis2-core.jar isn't it?
> And also rolled up all the axis2 jars into 3 jars like
> 1. axis2-core.jar
> 2. axis2-optional.jar
> 3. axis2-tools.jar
>

I clearly understand how axis2-core and axis2-optional fits together. I am
bit gray about how axis2-tools.jar add a value, because currently we have
several individual tools [command line tools , ide plugins , meven plugins
etc.] that has value individually and currently with the axis2 release, we
release them individually as Tools.
Thanks
Lahiru

I saw this entry in the kernal pom.xml file
> <dependency>
>             <groupId>org.apache.woden</groupId>
>             <artifactId>woden-impl-dom</artifactId>
>             <version>${woden.version}</version>
>             <exclusions>
>                 <exclusion>
>                     <groupId>xerces</groupId>
>                     <artifactId>xercesImpl</artifactId>
>                 </exclusion>
>                 <exclusion>
>                     <groupId>xml-apis</groupId>
>                     <artifactId>xml-apis</artifactId>
>                 </exclusion>
>             </exclusions>
>         </dependency>
>
> this means axis2 uses dom implementation.
>
>
> Thanks,
> >
> > Lawrence
> >
> >
> >
> >
> > "Amila Suriarachchi" <am...@gmail.com>
> > 11/01/2007 02:14 AM
> > Please respond to
> > axis-dev@ws.apache.org
> >
> >
> > To
> > axis-dev@ws.apache.org
> > cc
> >
> > Subject
> > Re: [Axis2] Axis2 Release Restructuring
> >
> >
> >
> >
> >
> >
> >
> >
> > On 11/1/07, Lawrence Mandel < lmandel@ca.ibm.com> wrote:
> > Hi Amila,
> >
> > Thanks for summarizing the conversation. I take it your summary is for
> > the
> > Axis2 server bundle that's been discussed. Two issues:
> >
> > 1. Will the 5 Axis2 jars be rolled up into a single Axis2-server jar as
> > has been requested and discussed?
> >
> > No. we are not going to shift as five modules.
> > It going to be only three.
> > 1. minimal distribution
> > 2. full distribution
> > 3. tools distribution
> >
> > the difference between minimal and full is that minimal distribution
> > contains jars required
> > for only basic set of use cases(as I have given earlier). It has both
> > client and server jars.
> >
> > 2. You listed
> > woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> > Woden has an Axiom based implementation that I thought was contributed
> > to
> > support Axis2.
> > So is this an optional jar?
> >
> > Is the Axiom implementation not in use in Axis2?
> >
> > Axis2 uses the axiom. What I asked is, whether it is necessary to shif
> > doom implementation as well.
> >
> > Amila.
> >
> > Thanks,
> >
> > Lawrence
> >
> >
> >
> >
> > "Amila Suriarachchi" < amilasuriarachchi@gmail.com>
> > 11/01/2007 12:16 AM
> > Please respond to
> > axis-dev@ws.apache.org
> >
> >
> > To
> > axis-dev@ws.apache.org
> > cc
> >
> > Subject
> > Re: [Axis2] Axis2 Release Restructuring
> >
> >
> >
> >
> >
> >
> > So shall we first conclue what should be included into the minimal
> > distribution?
> >
> > I would like to discribe the minimal distribution as follows,
> > It inclues the minimal set of jars which some one needs to creates a
> > webservice
> > using either
> > 1. Contract first approach
> >          here we going to provide only the default data binding support
> > 2. Code first approach
> >          POJO support
> >
> > and access them using the generated stub or
> > RPCService client. Here he can use addressing since it is a basic we
> > service spec and only with http transport.
> >
> > So the minimal distribution contains the following features
> > 1. Codegen support with adb
> > 2. POJO support
> > 3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
> > 4. Addressing
> > 5. Samples ( only for above features)
> >
> > is this enogh or is there any thing to add or remove?
> >
> > As I guess here are the jars we need for that,
> >
> > Axis2 jars
> > 1. axis2-adb-codegen-SNAPSHOT.jar
> > 2. axis2-adb-SNAPSHOT.jar
> > 3. axis2-codegen-SNAPSHOT.jar
> > 4. axis2-java2wsdl-SNAPSHOT.jar
> > 5. axis2-kernel-SNAPSHOT.jar
> >
> > ws  jars
> > 1. axiom-api-20071017.164440-781.jar
> > 2. axiom-impl-20071017.164440-780.jar (
> > (do we need axiom-dom-20071017.164440-780.jar?)
> > 3. neethi-20071017.164823-761.jar
> > 4. woden-api-1.0-incubating-20071018.161106-2.jar
> > 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> > 6. wsdl4j-1.6.2.jar
> > 7. XmlSchema-SNAPSHOT.jar
> >
> > other jars
> > 1. activation-1.1.jar
> > 2. annogen-0.1.0.jar
> > 3. backport-util-concurrent-2.2.jar
> > 4. commons-codec-1.3.jar
> > 5. commons-fileupload-1.1.1.jar
> > 6. commons-httpclient-3.0.1.jar
> > 7. commons-io-1.2.jar
> > 8. commons-logging-1.1.jar
> > 9. geronimo-annotation_1.0_spec-1.1.jar
> > 10. geronimo-stax-api_1.0_spec- 1.0.jar
> > 11. httpcore-4.0-alpha5.jar
> > 12. httpcore-nio-4.0-alpha5.jar
> > 13. httpcore-niossl-4.0-alpha5.jar
> > 14. jalopy-1.5rc3.jar
> > 15. jaxen-1.1.1.jar
> > 16. jettison-1.0-RC1.jar
> > 17. log4j-1.2.14.jar
> > 18. stax-api-1.0.1.jar
> > 19. wstx-asl-3.2.1.jar
> > 20. xalan-2.7.0.jar
> > 21. xercesImpl-2.8.1.jar
> > 22. xml-apis-1.3.03.jar
> >
> > Are there any thing to add or remove?
> > Here any way 34 jars are there. and we have left 24 jars.
> >
> > thanks,
> > Amila.
> >
> > On 10/30/07, Eran Chinthaka < chinthaka@opensource.lk> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Amila Suriarachchi wrote:
> >
> > >
> > > I have misunderstood the thing.
> > > you mean
> > > 1. minimal distribution with
> > >        server,client and kernal
> > > 2. full distribution with
> > >        minmal + optional
> > > 3. Tools distribution with
> > >        tools
> >
> > Exactly yes. I am not sure whether we need to expand full distro also in
> >
> > to two. Are we releasing all the modules with our current standard
> > distro.
> >
> >
> > > what I want to say is that we need a proper boundry definition about
> > > what should goes to minimal distribution.
> > > with some logical reasoning. Otherwise we have to discuss this again
> > > when implementing.
> >
> > Agreed. That is why I made this a proposal rather than a vote :). We
> > discussed this packaging issues couple of times and changed packaging
> > couple of time. When Axis2 evolves and we get more insight in to user
> > experience, we might want to change ourselves to cater for this
> > requirements. I myself found it bit difficult/confused to use Axis2 once
> > as a user. That is why I am proposing sth like this.
> >
> > Yes, let's discuss about this. And we might also want to revise this
> > once the next release manager (Amila will it be you ;) ) try to
> > implement this packaging proposal.
> >
> > So are we agreed to this three level distro?
> >
> > Thanks,
> > Chinthaka
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.6 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFHJ09HjON2uBzUhh8RAoDSAJ9DKYjtCRqEU/jiQnMnKm7oF0UzzQCgqd5z
> > 6SUmDsDsirjOF6j5WuAu9EA=
> > =ZWKs
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
> >
> >
> > --
> > Amila Suriarachchi,
> > WSO2 Inc.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
> >
> >
> > --
> > Amila Suriarachchi,
> > WSO2 Inc.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.




-- 
Thanks
Lahiru Sandakith

http://sandakith.wordpress.com/
GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC  1AB1 FE5E 7464 1F01 9A0F

Re: [Axis2] Axis2 Release Restructuring

Posted by Amila Suriarachchi <am...@gmail.com>.

On 11/1/07, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> Hi Amila,
>
> 1. From what I read I thought one of the issues (and an issue that I
> raised) was the large number of Axis2 jars. I understood from the
> conversation that's been taking place that the function in the many Axis
> jars would be rolled up into 3 (or 5) jars, not 3 zip (or tar, etc.)
> distros containing many jar files.


So you talking about the rolling axis2 jars into smaller number of jars. As
chinthaka has told in here
you want to roll all the axis2 jars into axis2-core.jar isn't it?
And also rolled up all the axis2 jars into 3 jars like
1. axis2-core.jar
2. axis2-optional.jar
3. axis2-tools.jar


2. There are two Woden implementations: DOM based and OM (Axiom) based.
> Previously these two distributions were packed together in one jar but
> they've recently been separated to reduce the number of dependencies when
> using one or the other. (Adopters will likely want to use either DOM or
> OM.) The DOM jar is required if you're using the Woden DOM implementation.
> Likewise, the OM jar is required when using the Axiom based
> implementation. I should have been clearer in my question, does Axis2 use
> the Woden Axiom based implementation or the Woden DOM based
> implementation?


I saw this entry in the kernal pom.xml file
<dependency>
            <groupId>org.apache.woden</groupId>
            <artifactId>woden-impl-dom</artifactId>
            <version>${woden.version}</version>
            <exclusions>
                <exclusion>
                    <groupId>xerces</groupId>
                    <artifactId>xercesImpl</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>xml-apis</groupId>
                    <artifactId>xml-apis</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

this means axis2 uses dom implementation.


Thanks,
>
> Lawrence
>
>
>
>
> "Amila Suriarachchi" <am...@gmail.com>
> 11/01/2007 02:14 AM
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
> axis-dev@ws.apache.org
> cc
>
> Subject
> Re: [Axis2] Axis2 Release Restructuring
>
>
>
>
>
>
>
>
> On 11/1/07, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> Hi Amila,
>
> Thanks for summarizing the conversation. I take it your summary is for the
> Axis2 server bundle that's been discussed. Two issues:
>
> 1. Will the 5 Axis2 jars be rolled up into a single Axis2-server jar as
> has been requested and discussed?
>
> No. we are not going to shift as five modules.
> It going to be only three.
> 1. minimal distribution
> 2. full distribution
> 3. tools distribution
>
> the difference between minimal and full is that minimal distribution
> contains jars required
> for only basic set of use cases(as I have given earlier). It has both
> client and server jars.
>
> 2. You listed
> woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> Woden has an Axiom based implementation that I thought was contributed to
> support Axis2.
> So is this an optional jar?
>
> Is the Axiom implementation not in use in Axis2?
>
> Axis2 uses the axiom. What I asked is, whether it is necessary to shif
> doom implementation as well.
>
> Amila.
>
> Thanks,
>
> Lawrence
>
>
>
>
> "Amila Suriarachchi" < amilasuriarachchi@gmail.com>
> 11/01/2007 12:16 AM
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
> axis-dev@ws.apache.org
> cc
>
> Subject
> Re: [Axis2] Axis2 Release Restructuring
>
>
>
>
>
>
> So shall we first conclue what should be included into the minimal
> distribution?
>
> I would like to discribe the minimal distribution as follows,
> It inclues the minimal set of jars which some one needs to creates a
> webservice
> using either
> 1. Contract first approach
>          here we going to provide only the default data binding support
> 2. Code first approach
>          POJO support
>
> and access them using the generated stub or
> RPCService client. Here he can use addressing since it is a basic we
> service spec and only with http transport.
>
> So the minimal distribution contains the following features
> 1. Codegen support with adb
> 2. POJO support
> 3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
> 4. Addressing
> 5. Samples ( only for above features)
>
> is this enogh or is there any thing to add or remove?
>
> As I guess here are the jars we need for that,
>
> Axis2 jars
> 1. axis2-adb-codegen-SNAPSHOT.jar
> 2. axis2-adb-SNAPSHOT.jar
> 3. axis2-codegen-SNAPSHOT.jar
> 4. axis2-java2wsdl-SNAPSHOT.jar
> 5. axis2-kernel-SNAPSHOT.jar
>
> ws  jars
> 1. axiom-api-20071017.164440-781.jar
> 2. axiom-impl-20071017.164440-780.jar (
> (do we need axiom-dom-20071017.164440-780.jar?)
> 3. neethi-20071017.164823-761.jar
> 4. woden-api-1.0-incubating-20071018.161106-2.jar
> 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> 6. wsdl4j-1.6.2.jar
> 7. XmlSchema-SNAPSHOT.jar
>
> other jars
> 1. activation-1.1.jar
> 2. annogen-0.1.0.jar
> 3. backport-util-concurrent-2.2.jar
> 4. commons-codec-1.3.jar
> 5. commons-fileupload-1.1.1.jar
> 6. commons-httpclient-3.0.1.jar
> 7. commons-io-1.2.jar
> 8. commons-logging-1.1.jar
> 9. geronimo-annotation_1.0_spec-1.1.jar
> 10. geronimo-stax-api_1.0_spec- 1.0.jar
> 11. httpcore-4.0-alpha5.jar
> 12. httpcore-nio-4.0-alpha5.jar
> 13. httpcore-niossl-4.0-alpha5.jar
> 14. jalopy-1.5rc3.jar
> 15. jaxen-1.1.1.jar
> 16. jettison-1.0-RC1.jar
> 17. log4j-1.2.14.jar
> 18. stax-api-1.0.1.jar
> 19. wstx-asl-3.2.1.jar
> 20. xalan-2.7.0.jar
> 21. xercesImpl-2.8.1.jar
> 22. xml-apis-1.3.03.jar
>
> Are there any thing to add or remove?
> Here any way 34 jars are there. and we have left 24 jars.
>
> thanks,
> Amila.
>
> On 10/30/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Amila Suriarachchi wrote:
>
> >
> > I have misunderstood the thing.
> > you mean
> > 1. minimal distribution with
> >        server,client and kernal
> > 2. full distribution with
> >        minmal + optional
> > 3. Tools distribution with
> >        tools
>
> Exactly yes. I am not sure whether we need to expand full distro also in
> to two. Are we releasing all the modules with our current standard distro.
>
>
> > what I want to say is that we need a proper boundry definition about
> > what should goes to minimal distribution.
> > with some logical reasoning. Otherwise we have to discuss this again
> > when implementing.
>
> Agreed. That is why I made this a proposal rather than a vote :). We
> discussed this packaging issues couple of times and changed packaging
> couple of time. When Axis2 evolves and we get more insight in to user
> experience, we might want to change ourselves to cater for this
> requirements. I myself found it bit difficult/confused to use Axis2 once
> as a user. That is why I am proposing sth like this.
>
> Yes, let's discuss about this. And we might also want to revise this
> once the next release manager (Amila will it be you ;) ) try to
> implement this packaging proposal.
>
> So are we agreed to this three level distro?
>
> Thanks,
> Chinthaka
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHJ09HjON2uBzUhh8RAoDSAJ9DKYjtCRqEU/jiQnMnKm7oF0UzzQCgqd5z
> 6SUmDsDsirjOF6j5WuAu9EA=
> =ZWKs
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Axis2 Release Restructuring

Posted by Lawrence Mandel <lm...@ca.ibm.com>.

Thanks for clearing up my confusion about the jars Chinthaka.

WRT Woden's Axiom implementation, I'm pretty sure John Kaputin has been 
keeping it in sync with the DOM implementation. With Woden's new 
modularized build, Axis2 should be able to pick up only the Axiom based 
implementation.

John - Can you confirm that the Woden Axiom implementation in sync with 
the DOM implementation?

Thanks,

Lawrence




Eran Chinthaka <ch...@opensource.lk> 
11/01/2007 10:22 PM
Please respond to
axis-dev@ws.apache.org


To
axis-dev@ws.apache.org
cc

Subject
Re: [Axis2] Axis2 Release Restructuring






-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There seems to be slight misunderstanding. What Lawrence as asking is
that will we generate just one jar out of the names modules and include
that in the minimal (I'd like to this to be called as core distro)
distribution.
I think we agreed to that. So as Amila mentioned there won't be 5 jars
(namely axis2-adb-codegen-SNAPSHOT.jar, axis2-adb-SNAPSHOT.jar,
axis2-codegen-SNAPSHOT.jar, axis2-java2wsdl-SNAPSHOT.jar,
axis2-kernel-SNAPSHOT.jar ) in the core distro. It will be just
axis2-core-<version>.jar.

About Woden axiom implementation. Yes I prefer to have that. But is it
maintained now. I know Oshani was working on that for her SoC, but can
we use it as it is now and ship only that. Aren't there any changes in
the DOMReader that should be implemented in the AxiomReader? If not then
I am +1 for using that.

Thanks,
Chinthaka

Lawrence Mandel wrote:
> Hi Amila,
> 
> 1. From what I read I thought one of the issues (and an issue that I 
> raised) was the large number of Axis2 jars. I understood from the 
> conversation that's been taking place that the function in the many Axis 

> jars would be rolled up into 3 (or 5) jars, not 3 zip (or tar, etc.) 
> distros containing many jar files.
> 
> 2. There are two Woden implementations: DOM based and OM (Axiom) based. 
> Previously these two distributions were packed together in one jar but 
> they've recently been separated to reduce the number of dependencies 
when 
> using one or the other. (Adopters will likely want to use either DOM or 
> OM.) The DOM jar is required if you're using the Woden DOM 
implementation. 
> Likewise, the OM jar is required when using the Axiom based 
> implementation. I should have been clearer in my question, does Axis2 
use 
> the Woden Axiom based implementation or the Woden DOM based 
> implementation?
> 
> Thanks,
> 
> Lawrence 
> 
> 
> 
> 
> "Amila Suriarachchi" <am...@gmail.com> 
> 11/01/2007 02:14 AM
> Please respond to
> axis-dev@ws.apache.org
> 
> 
> To
> axis-dev@ws.apache.org
> cc
> 
> Subject
> Re: [Axis2] Axis2 Release Restructuring
> 
> 
> 
> 
> 
> 
> 
> 
> On 11/1/07, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> Hi Amila,
> 
> Thanks for summarizing the conversation. I take it your summary is for 
the
> Axis2 server bundle that's been discussed. Two issues:
> 
> 1. Will the 5 Axis2 jars be rolled up into a single Axis2-server jar as 
> has been requested and discussed?
> 
> No. we are not going to shift as five modules.
> It going to be only three.
> 1. minimal distribution
> 2. full distribution
> 3. tools distribution
> 
> the difference between minimal and full is that minimal distribution 
> contains jars required 
> for only basic set of use cases(as I have given earlier). It has both 
> client and server jars.
> 
> 2. You listed
> woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> Woden has an Axiom based implementation that I thought was contributed 
to
> support Axis2. 
> So is this an optional jar? 
> 
> Is the Axiom implementation not in use in Axis2?
> 
> Axis2 uses the axiom. What I asked is, whether it is necessary to shif 
> doom implementation as well. 
> 
> Amila.
> 
> Thanks,
> 
> Lawrence
> 
> 
> 
> 
> "Amila Suriarachchi" < amilasuriarachchi@gmail.com>
> 11/01/2007 12:16 AM
> Please respond to
> axis-dev@ws.apache.org
> 
> 
> To
> axis-dev@ws.apache.org
> cc
> 
> Subject
> Re: [Axis2] Axis2 Release Restructuring
> 
> 
> 
> 
> 
> 
> So shall we first conclue what should be included into the minimal
> distribution?
> 
> I would like to discribe the minimal distribution as follows, 
> It inclues the minimal set of jars which some one needs to creates a
> webservice
> using either
> 1. Contract first approach
>          here we going to provide only the default data binding support
> 2. Code first approach 
>          POJO support
> 
> and access them using the generated stub or
> RPCService client. Here he can use addressing since it is a basic we
> service spec and only with http transport.
> 
> So the minimal distribution contains the following features 
> 1. Codegen support with adb
> 2. POJO support
> 3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
> 4. Addressing
> 5. Samples ( only for above features)
> 
> is this enogh or is there any thing to add or remove? 
> 
> As I guess here are the jars we need for that,
> 
> Axis2 jars
> 1. axis2-adb-codegen-SNAPSHOT.jar
> 2. axis2-adb-SNAPSHOT.jar
> 3. axis2-codegen-SNAPSHOT.jar
> 4. axis2-java2wsdl-SNAPSHOT.jar
> 5. axis2-kernel-SNAPSHOT.jar 
> 
> ws  jars
> 1. axiom-api-20071017.164440-781.jar
> 2. axiom-impl-20071017.164440-780.jar (
> (do we need axiom-dom-20071017.164440-780.jar?)
> 3. neethi-20071017.164823-761.jar
> 4. woden-api-1.0-incubating-20071018.161106-2.jar 
> 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> 6. wsdl4j-1.6.2.jar
> 7. XmlSchema-SNAPSHOT.jar
> 
> other jars
> 1. activation-1.1.jar
> 2. annogen-0.1.0.jar
> 3. backport-util-concurrent-2.2.jar
> 4. commons-codec-1.3.jar
> 5. commons-fileupload-1.1.1.jar
> 6. commons-httpclient-3.0.1.jar
> 7. commons-io-1.2.jar
> 8. commons-logging-1.1.jar
> 9. geronimo-annotation_1.0_spec-1.1.jar
> 10. geronimo-stax-api_1.0_spec- 1.0.jar
> 11. httpcore-4.0-alpha5.jar
> 12. httpcore-nio-4.0-alpha5.jar
> 13. httpcore-niossl-4.0-alpha5.jar
> 14. jalopy-1.5rc3.jar
> 15. jaxen-1.1.1.jar
> 16. jettison-1.0-RC1.jar
> 17. log4j-1.2.14.jar
> 18. stax-api-1.0.1.jar 
> 19. wstx-asl-3.2.1.jar
> 20. xalan-2.7.0.jar
> 21. xercesImpl-2.8.1.jar
> 22. xml-apis-1.3.03.jar
> 
> Are there any thing to add or remove?
> Here any way 34 jars are there. and we have left 24 jars.
> 
> thanks, 
> Amila.
> 
> On 10/30/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> Amila Suriarachchi wrote:
> 
>> I have misunderstood the thing.
>> you mean
>> 1. minimal distribution with
>>        server,client and kernal
>> 2. full distribution with
>>        minmal + optional
>> 3. Tools distribution with 
>>        tools
> 
> Exactly yes. I am not sure whether we need to expand full distro also in
> to two. Are we releasing all the modules with our current standard 
distro.
> 
> 
>> what I want to say is that we need a proper boundry definition about 
>> what should goes to minimal distribution.
>> with some logical reasoning. Otherwise we have to discuss this again
>> when implementing.
> 
> Agreed. That is why I made this a proposal rather than a vote :). We 
> discussed this packaging issues couple of times and changed packaging
> couple of time. When Axis2 evolves and we get more insight in to user
> experience, we might want to change ourselves to cater for this
> requirements. I myself found it bit difficult/confused to use Axis2 once 

> as a user. That is why I am proposing sth like this.
> 
> Yes, let's discuss about this. And we might also want to revise this
> once the next release manager (Amila will it be you ;) ) try to
> implement this packaging proposal. 
> 
> So are we agreed to this three level distro?
> 
> Thanks,
> Chinthaka

- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org




- --
Amila Suriarachchi,
WSO2 Inc.


- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org





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

iD8DBQFHKooDjON2uBzUhh8RAoP9AJwI47B7nTh4vsbbn1HqCC2zCm1oKQCgifAT
5XfLSKzmE77tE10nj0YDG/c=
=S7dY
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Axis2 Release Restructuring

Posted by Eran Chinthaka <ch...@opensource.lk>.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There seems to be slight misunderstanding. What Lawrence as asking is
that will we generate just one jar out of the names modules and include
that in the minimal (I'd like to this to be called as core distro)
distribution.
I think we agreed to that. So as Amila mentioned there won't be 5 jars
(namely axis2-adb-codegen-SNAPSHOT.jar, axis2-adb-SNAPSHOT.jar,
axis2-codegen-SNAPSHOT.jar, axis2-java2wsdl-SNAPSHOT.jar,
axis2-kernel-SNAPSHOT.jar ) in the core distro. It will be just
axis2-core-<version>.jar.

About Woden axiom implementation. Yes I prefer to have that. But is it
maintained now. I know Oshani was working on that for her SoC, but can
we use it as it is now and ship only that. Aren't there any changes in
the DOMReader that should be implemented in the AxiomReader? If not then
I am +1 for using that.

Thanks,
Chinthaka

Lawrence Mandel wrote:
> Hi Amila,
> 
> 1. From what I read I thought one of the issues (and an issue that I 
> raised) was the large number of Axis2 jars. I understood from the 
> conversation that's been taking place that the function in the many Axis 
> jars would be rolled up into 3 (or 5) jars, not 3 zip (or tar, etc.) 
> distros containing many jar files.
> 
> 2. There are two Woden implementations: DOM based and OM (Axiom) based. 
> Previously these two distributions were packed together in one jar but 
> they've recently been separated to reduce the number of dependencies when 
> using one or the other. (Adopters will likely want to use either DOM or 
> OM.) The DOM jar is required if you're using the Woden DOM implementation. 
> Likewise, the OM jar is required when using the Axiom based 
> implementation. I should have been clearer in my question, does Axis2 use 
> the Woden Axiom based implementation or the Woden DOM based 
> implementation?
> 
> Thanks,
> 
> Lawrence 
> 
> 
> 
> 
> "Amila Suriarachchi" <am...@gmail.com> 
> 11/01/2007 02:14 AM
> Please respond to
> axis-dev@ws.apache.org
> 
> 
> To
> axis-dev@ws.apache.org
> cc
> 
> Subject
> Re: [Axis2] Axis2 Release Restructuring
> 
> 
> 
> 
> 
> 
> 
> 
> On 11/1/07, Lawrence Mandel <lm...@ca.ibm.com> wrote:
> Hi Amila,
> 
> Thanks for summarizing the conversation. I take it your summary is for the
> Axis2 server bundle that's been discussed. Two issues:
> 
> 1. Will the 5 Axis2 jars be rolled up into a single Axis2-server jar as 
> has been requested and discussed?
> 
> No. we are not going to shift as five modules.
> It going to be only three.
> 1. minimal distribution
> 2. full distribution
> 3. tools distribution
> 
> the difference between minimal and full is that minimal distribution 
> contains jars required 
> for only basic set of use cases(as I have given earlier). It has both 
> client and server jars.
> 
> 2. You listed
> woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> Woden has an Axiom based implementation that I thought was contributed to
> support Axis2. 
> So is this an optional jar? 
> 
> Is the Axiom implementation not in use in Axis2?
> 
> Axis2 uses the axiom. What I asked is, whether it is necessary to shif 
> doom implementation as well. 
> 
> Amila.
> 
> Thanks,
> 
> Lawrence
> 
> 
> 
> 
> "Amila Suriarachchi" < amilasuriarachchi@gmail.com>
> 11/01/2007 12:16 AM
> Please respond to
> axis-dev@ws.apache.org
> 
> 
> To
> axis-dev@ws.apache.org
> cc
> 
> Subject
> Re: [Axis2] Axis2 Release Restructuring
> 
> 
> 
> 
> 
> 
> So shall we first conclue what should be included into the minimal
> distribution?
> 
> I would like to discribe the minimal distribution as follows, 
> It inclues the minimal set of jars which some one needs to creates a
> webservice
> using either
> 1. Contract first approach
>          here we going to provide only the default data binding support
> 2. Code first approach 
>          POJO support
> 
> and access them using the generated stub or
> RPCService client. Here he can use addressing since it is a basic we
> service spec and only with http transport.
> 
> So the minimal distribution contains the following features 
> 1. Codegen support with adb
> 2. POJO support
> 3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
> 4. Addressing
> 5. Samples ( only for above features)
> 
> is this enogh or is there any thing to add or remove? 
> 
> As I guess here are the jars we need for that,
> 
> Axis2 jars
> 1. axis2-adb-codegen-SNAPSHOT.jar
> 2. axis2-adb-SNAPSHOT.jar
> 3. axis2-codegen-SNAPSHOT.jar
> 4. axis2-java2wsdl-SNAPSHOT.jar
> 5. axis2-kernel-SNAPSHOT.jar 
> 
> ws  jars
> 1. axiom-api-20071017.164440-781.jar
> 2. axiom-impl-20071017.164440-780.jar (
> (do we need axiom-dom-20071017.164440-780.jar?)
> 3. neethi-20071017.164823-761.jar
> 4. woden-api-1.0-incubating-20071018.161106-2.jar 
> 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> 6. wsdl4j-1.6.2.jar
> 7. XmlSchema-SNAPSHOT.jar
> 
> other jars
> 1. activation-1.1.jar
> 2. annogen-0.1.0.jar
> 3. backport-util-concurrent-2.2.jar
> 4. commons-codec-1.3.jar
> 5. commons-fileupload-1.1.1.jar
> 6. commons-httpclient-3.0.1.jar
> 7. commons-io-1.2.jar
> 8. commons-logging-1.1.jar
> 9. geronimo-annotation_1.0_spec-1.1.jar
> 10. geronimo-stax-api_1.0_spec- 1.0.jar
> 11. httpcore-4.0-alpha5.jar
> 12. httpcore-nio-4.0-alpha5.jar
> 13. httpcore-niossl-4.0-alpha5.jar
> 14. jalopy-1.5rc3.jar
> 15. jaxen-1.1.1.jar
> 16. jettison-1.0-RC1.jar
> 17. log4j-1.2.14.jar
> 18. stax-api-1.0.1.jar 
> 19. wstx-asl-3.2.1.jar
> 20. xalan-2.7.0.jar
> 21. xercesImpl-2.8.1.jar
> 22. xml-apis-1.3.03.jar
> 
> Are there any thing to add or remove?
> Here any way 34 jars are there. and we have left 24 jars.
> 
> thanks, 
> Amila.
> 
> On 10/30/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> Amila Suriarachchi wrote:
> 
>> I have misunderstood the thing.
>> you mean
>> 1. minimal distribution with
>>        server,client and kernal
>> 2. full distribution with
>>        minmal + optional
>> 3. Tools distribution with 
>>        tools
> 
> Exactly yes. I am not sure whether we need to expand full distro also in
> to two. Are we releasing all the modules with our current standard distro.
> 
> 
>> what I want to say is that we need a proper boundry definition about 
>> what should goes to minimal distribution.
>> with some logical reasoning. Otherwise we have to discuss this again
>> when implementing.
> 
> Agreed. That is why I made this a proposal rather than a vote :). We 
> discussed this packaging issues couple of times and changed packaging
> couple of time. When Axis2 evolves and we get more insight in to user
> experience, we might want to change ourselves to cater for this
> requirements. I myself found it bit difficult/confused to use Axis2 once 
> as a user. That is why I am proposing sth like this.
> 
> Yes, let's discuss about this. And we might also want to revise this
> once the next release manager (Amila will it be you ;) ) try to
> implement this packaging proposal. 
> 
> So are we agreed to this three level distro?
> 
> Thanks,
> Chinthaka

- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org




- --
Amila Suriarachchi,
WSO2 Inc.


- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org





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

iD8DBQFHKooDjON2uBzUhh8RAoP9AJwI47B7nTh4vsbbn1HqCC2zCm1oKQCgifAT
5XfLSKzmE77tE10nj0YDG/c=
=S7dY
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Axis2 Release Restructuring

Posted by Lawrence Mandel <lm...@ca.ibm.com>.

Hi Amila,

1. From what I read I thought one of the issues (and an issue that I 
raised) was the large number of Axis2 jars. I understood from the 
conversation that's been taking place that the function in the many Axis 
jars would be rolled up into 3 (or 5) jars, not 3 zip (or tar, etc.) 
distros containing many jar files.

2. There are two Woden implementations: DOM based and OM (Axiom) based. 
Previously these two distributions were packed together in one jar but 
they've recently been separated to reduce the number of dependencies when 
using one or the other. (Adopters will likely want to use either DOM or 
OM.) The DOM jar is required if you're using the Woden DOM implementation. 
Likewise, the OM jar is required when using the Axiom based 
implementation. I should have been clearer in my question, does Axis2 use 
the Woden Axiom based implementation or the Woden DOM based 
implementation?

Thanks,

Lawrence 

"Amila Suriarachchi" <am...@gmail.com> 
11/01/2007 02:14 AM
Please respond to
axis-dev@ws.apache.org

To
axis-dev@ws.apache.org
cc

Subject
Re: [Axis2] Axis2 Release Restructuring

On 11/1/07, Lawrence Mandel <lm...@ca.ibm.com> wrote:
Hi Amila,

Thanks for summarizing the conversation. I take it your summary is for the
Axis2 server bundle that's been discussed. Two issues:

1. Will the 5 Axis2 jars be rolled up into a single Axis2-server jar as 
has been requested and discussed?

No. we are not going to shift as five modules.
It going to be only three.
1. minimal distribution
2. full distribution
3. tools distribution

the difference between minimal and full is that minimal distribution 
contains jars required 
for only basic set of use cases(as I have given earlier). It has both 
client and server jars.

2. You listed
woden-impl-dom-1.0-incubating-20071018.161106-2.jar
Woden has an Axiom based implementation that I thought was contributed to
support Axis2. 
So is this an optional jar? 

Is the Axiom implementation not in use in Axis2?

Axis2 uses the axiom. What I asked is, whether it is necessary to shif 
doom implementation as well. 

Amila.

Thanks,

Lawrence

"Amila Suriarachchi" < amilasuriarachchi@gmail.com>
11/01/2007 12:16 AM
Please respond to
axis-dev@ws.apache.org

To
axis-dev@ws.apache.org
cc

Subject
Re: [Axis2] Axis2 Release Restructuring

So shall we first conclue what should be included into the minimal
distribution?

I would like to discribe the minimal distribution as follows, 
It inclues the minimal set of jars which some one needs to creates a
webservice
using either
1. Contract first approach
         here we going to provide only the default data binding support
2. Code first approach 
         POJO support

and access them using the generated stub or
RPCService client. Here he can use addressing since it is a basic we
service spec and only with http transport.

So the minimal distribution contains the following features 
1. Codegen support with adb
2. POJO support
3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
4. Addressing
5. Samples ( only for above features)

is this enogh or is there any thing to add or remove? 

As I guess here are the jars we need for that,

Axis2 jars
1. axis2-adb-codegen-SNAPSHOT.jar
2. axis2-adb-SNAPSHOT.jar
3. axis2-codegen-SNAPSHOT.jar
4. axis2-java2wsdl-SNAPSHOT.jar
5. axis2-kernel-SNAPSHOT.jar 

ws  jars
1. axiom-api-20071017.164440-781.jar
2. axiom-impl-20071017.164440-780.jar (
(do we need axiom-dom-20071017.164440-780.jar?)
3. neethi-20071017.164823-761.jar
4. woden-api-1.0-incubating-20071018.161106-2.jar 
5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
6. wsdl4j-1.6.2.jar
7. XmlSchema-SNAPSHOT.jar

other jars
1. activation-1.1.jar
2. annogen-0.1.0.jar
3. backport-util-concurrent-2.2.jar
4. commons-codec-1.3.jar
5. commons-fileupload-1.1.1.jar
6. commons-httpclient-3.0.1.jar
7. commons-io-1.2.jar
8. commons-logging-1.1.jar
9. geronimo-annotation_1.0_spec-1.1.jar
10. geronimo-stax-api_1.0_spec- 1.0.jar
11. httpcore-4.0-alpha5.jar
12. httpcore-nio-4.0-alpha5.jar
13. httpcore-niossl-4.0-alpha5.jar
14. jalopy-1.5rc3.jar
15. jaxen-1.1.1.jar
16. jettison-1.0-RC1.jar
17. log4j-1.2.14.jar
18. stax-api-1.0.1.jar 
19. wstx-asl-3.2.1.jar
20. xalan-2.7.0.jar
21. xercesImpl-2.8.1.jar
22. xml-apis-1.3.03.jar

Are there any thing to add or remove?
Here any way 34 jars are there. and we have left 24 jars.

thanks, 
Amila.

On 10/30/07, Eran Chinthaka <ch...@opensource.lk> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Amila Suriarachchi wrote:

>
> I have misunderstood the thing.
> you mean
> 1. minimal distribution with
>        server,client and kernal
> 2. full distribution with
>        minmal + optional
> 3. Tools distribution with 
>        tools

Exactly yes. I am not sure whether we need to expand full distro also in
to two. Are we releasing all the modules with our current standard distro.

> what I want to say is that we need a proper boundry definition about 
> what should goes to minimal distribution.
> with some logical reasoning. Otherwise we have to discuss this again
> when implementing.

Agreed. That is why I made this a proposal rather than a vote :). We 
discussed this packaging issues couple of times and changed packaging
couple of time. When Axis2 evolves and we get more insight in to user
experience, we might want to change ourselves to cater for this
requirements. I myself found it bit difficult/confused to use Axis2 once 
as a user. That is why I am proposing sth like this.

Yes, let's discuss about this. And we might also want to revise this
once the next release manager (Amila will it be you ;) ) try to
implement this packaging proposal. 

So are we agreed to this three level distro?

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

iD8DBQFHJ09HjON2uBzUhh8RAoDSAJ9DKYjtCRqEU/jiQnMnKm7oF0UzzQCgqd5z
6SUmDsDsirjOF6j5WuAu9EA=
=ZWKs
-----END PGP SIGNATURE-----

--------------------------------------------------------------------- 
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org 

--
Amila Suriarachchi,
WSO2 Inc.

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

-- 
Amila Suriarachchi, 
WSO2 Inc. 

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Axis2 Release Restructuring

Posted by Amila Suriarachchi <am...@gmail.com>.

On 11/1/07, Lawrence Mandel <lm...@ca.ibm.com> wrote:
>
> Hi Amila,
>
> Thanks for summarizing the conversation. I take it your summary is for the
> Axis2 server bundle that's been discussed. Two issues:
>
> 1. Will the 5 Axis2 jars be rolled up into a single Axis2-server jar as
> has been requested and discussed?


No. we are not going to shift as five modules.
It going to be only three.
1. minimal distribution
2. full distribution
3. tools distribution

the difference between minimal and full is that minimal distribution
contains jars required
for only basic set of use cases(as I have given earlier). It has both client
and server jars.

2. You listed
> woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> Woden has an Axiom based implementation that I thought was contributed to
> support Axis2.

So is this an optional jar?

Is the Axiom implementation not in use in Axis2?


Axis2 uses the axiom. What I asked is, whether it is necessary to shif doom
implementation as well.

Amila.

Thanks,
>
> Lawrence
>
>
>
>
> "Amila Suriarachchi" <am...@gmail.com>
> 11/01/2007 12:16 AM
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
> axis-dev@ws.apache.org
> cc
>
> Subject
> Re: [Axis2] Axis2 Release Restructuring
>
>
>
>
>
>
> So shall we first conclue what should be included into the minimal
> distribution?
>
> I would like to discribe the minimal distribution as follows,
> It inclues the minimal set of jars which some one needs to creates a
> webservice
> using either
> 1. Contract first approach
>          here we going to provide only the default data binding support
> 2. Code first approach
>          POJO support
>
> and access them using the generated stub or
> RPCService client. Here he can use addressing since it is a basic we
> service spec and only with http transport.
>
> So the minimal distribution contains the following features
> 1. Codegen support with adb
> 2. POJO support
> 3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
> 4. Addressing
> 5. Samples ( only for above features)
>
> is this enogh or is there any thing to add or remove?
>
> As I guess here are the jars we need for that,
>
> Axis2 jars
> 1. axis2-adb-codegen-SNAPSHOT.jar
> 2. axis2-adb-SNAPSHOT.jar
> 3. axis2-codegen-SNAPSHOT.jar
> 4. axis2-java2wsdl-SNAPSHOT.jar
> 5. axis2-kernel-SNAPSHOT.jar
>
> ws  jars
> 1. axiom-api-20071017.164440-781.jar
> 2. axiom-impl-20071017.164440-780.jar (
> (do we need axiom-dom-20071017.164440-780.jar?)
> 3. neethi-20071017.164823-761.jar
> 4. woden-api-1.0-incubating-20071018.161106-2.jar
> 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> 6. wsdl4j-1.6.2.jar
> 7. XmlSchema-SNAPSHOT.jar
>
> other jars
> 1. activation-1.1.jar
> 2. annogen-0.1.0.jar
> 3. backport-util-concurrent-2.2.jar
> 4. commons-codec-1.3.jar
> 5. commons-fileupload-1.1.1.jar
> 6. commons-httpclient-3.0.1.jar
> 7. commons-io-1.2.jar
> 8. commons-logging-1.1.jar
> 9. geronimo-annotation_1.0_spec-1.1.jar
> 10. geronimo-stax-api_1.0_spec-1.0.jar
> 11. httpcore-4.0-alpha5.jar
> 12. httpcore-nio-4.0-alpha5.jar
> 13. httpcore-niossl-4.0-alpha5.jar
> 14. jalopy-1.5rc3.jar
> 15. jaxen-1.1.1.jar
> 16. jettison-1.0-RC1.jar
> 17. log4j-1.2.14.jar
> 18. stax-api-1.0.1.jar
> 19. wstx-asl-3.2.1.jar
> 20. xalan-2.7.0.jar
> 21. xercesImpl-2.8.1.jar
> 22. xml-apis-1.3.03.jar
>
> Are there any thing to add or remove?
> Here any way 34 jars are there. and we have left 24 jars.
>
> thanks,
> Amila.
>
> On 10/30/07, Eran Chinthaka <ch...@opensource.lk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Amila Suriarachchi wrote:
>
> >
> > I have misunderstood the thing.
> > you mean
> > 1. minimal distribution with
> >        server,client and kernal
> > 2. full distribution with
> >        minmal + optional
> > 3. Tools distribution with
> >        tools
>
> Exactly yes. I am not sure whether we need to expand full distro also in
> to two. Are we releasing all the modules with our current standard distro.
>
>
> > what I want to say is that we need a proper boundry definition about
> > what should goes to minimal distribution.
> > with some logical reasoning. Otherwise we have to discuss this again
> > when implementing.
>
> Agreed. That is why I made this a proposal rather than a vote :). We
> discussed this packaging issues couple of times and changed packaging
> couple of time. When Axis2 evolves and we get more insight in to user
> experience, we might want to change ourselves to cater for this
> requirements. I myself found it bit difficult/confused to use Axis2 once
> as a user. That is why I am proposing sth like this.
>
> Yes, let's discuss about this. And we might also want to revise this
> once the next release manager (Amila will it be you ;) ) try to
> implement this packaging proposal.
>
> So are we agreed to this three level distro?
>
> Thanks,
> Chinthaka
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHJ09HjON2uBzUhh8RAoDSAJ9DKYjtCRqEU/jiQnMnKm7oF0UzzQCgqd5z
> 6SUmDsDsirjOF6j5WuAu9EA=
> =ZWKs
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Axis2 Release Restructuring

Posted by David Illsley <da...@gmail.com>.

Could you re-state the proposal in a new thread...? I'm not sure I've
followed this one fully.
Thanks,
David

On 05/11/2007, Eran Chinthaka <ch...@opensource.lk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Can we assume people are happy with this? Do we need to call for a vote?
>
> Chinthaka
>
> Amila Suriarachchi wrote:
> > So here are the changes we going to do.
> >
> > On 11/2/07, *Eran Chinthaka* <chinthaka@opensource.lk
> > <ma...@opensource.lk>> wrote:
> >
> > Amila Suriarachchi wrote:
> >
> >> So the minimal distribution contains the following features
> >> 1. Codegen support with adb
> >> 2. POJO support
> >> 3. MTOM (when we includes the axiom and axis2 kernal anyway we get
> > this)
> >> 4. Addressing
> >> 5. Samples ( only for above features)
> >
> >> is this enogh or is there any thing to add or remove?
> >
> > This is what I thought also.
> >
> >
> >> As I guess here are the jars we need for that,
> >
> >> Axis2 jars
> >> 1. axis2-adb-codegen-SNAPSHOT.jar
> >> 2. axis2-adb-SNAPSHOT.jar
> >> 3. axis2-codegen-SNAPSHOT.jar
> >> 4. axis2-java2wsdl-SNAPSHOT.jar
> >> 5. axis2-kernel-SNAPSHOT.jar
> >
> > I think you will also include addressing mar, right? It should be
> > there.
> >
> >
> >> yes. I fogot to metion it. repository directory should have the
> >> addressing.mar
> >> and have to roll all the jars to axis2-core.jar.
> >
> >
> >> ws  jars
> >> 1. axiom-api-20071017.164440-781.jar
> >> 2. axiom-impl-20071017.164440-780.jar (
> >> (do we need axiom-dom-20071017.164440-780.jar?)
> >
> > Yes we do need it.
> >
> >
> >> ok so we add this.
> >
> >> 3. neethi-20071017.164823-761.jar
> >> 4. woden-api-1.0-incubating-20071018.161106-2.jar
> >> 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> >> 6. wsdl4j-1.6.2.jar
> >> 7. XmlSchema-SNAPSHOT.jar
> >
> >> other jars
> >> 1. activation-1.1.jar
> >> 2. annogen-0.1.0.jar
> >> 3. backport-util-concurrent-2.2.jar
> >> 4. commons-codec-1.3.jar
> >> 5. commons-fileupload-1.1.1.jar
> >> 6. commons-httpclient-3.0.1.jar
> >> 7. commons-io-1.2.jar
> >> 8. commons-logging-1.1.jar
> >
> > Grrrrr !!!!
> >
> >> 9. geronimo-annotation_1.0_spec-1.1.jar
> >
> > What is this for? If this is for annotations processing, IIRC annogen
> > does the same thing. Please correct me if I am wrong.
> >
> >
> >> I am also not sure. I put this to be in safe side.  I thought is may
> >> need when
> >> annotation processing with POJO. or is it something use with jax-ws?
> >
> >> 10. geronimo-stax-api_1.0_spec- 1.0.jar
> >> 11. httpcore-4.0-alpha5.jar
> >> 12. httpcore-nio-4.0-alpha5.jar
> >> 13. httpcore-niossl-4.0-alpha5.jar
> >> 14. jalopy-1.5rc3.jar
> >
> > Do we need this. IIRC, this is to pretty print generated code, right? I
> > prefer removing this.
> >
> >
> >> yes. we don't need this.
> >
> >> 15. jaxen-1.1.1.jar
> >> 16. jettison-1.0-RC1.jar
> >
> > Do we need JSON support by default? I think we don't. Since we are not
> > including json module, we can remove this.
> >
> >
> >> I thought  there may be a dependency for axiom. if axiom do not need this
> >> should remove.
> >
> > Thanks,
> > Chinthaka
>
> - ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> > --
> > Amila Suriarachchi,
> > WSO2 Inc.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHLoFejON2uBzUhh8RApmWAJsFoB1j3LREmMqAYGlx0zrssf9YXACgk7mL
> ZX2qSp7yp6tVJOXUCZJ1onk=
> =uEX2
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
David Illsley - IBM Web Services Development

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Axis2 Release Restructuring

Posted by Eran Chinthaka <ch...@opensource.lk>.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Can we assume people are happy with this? Do we need to call for a vote?

Chinthaka

Amila Suriarachchi wrote:
> So here are the changes we going to do.
> 
> On 11/2/07, *Eran Chinthaka* <chinthaka@opensource.lk
> <ma...@opensource.lk>> wrote:
> 
> Amila Suriarachchi wrote:
> 
>> So the minimal distribution contains the following features
>> 1. Codegen support with adb
>> 2. POJO support
>> 3. MTOM (when we includes the axiom and axis2 kernal anyway we get
> this)
>> 4. Addressing
>> 5. Samples ( only for above features)
> 
>> is this enogh or is there any thing to add or remove?
> 
> This is what I thought also.
> 
> 
>> As I guess here are the jars we need for that,
> 
>> Axis2 jars
>> 1. axis2-adb-codegen-SNAPSHOT.jar
>> 2. axis2-adb-SNAPSHOT.jar
>> 3. axis2-codegen-SNAPSHOT.jar
>> 4. axis2-java2wsdl-SNAPSHOT.jar
>> 5. axis2-kernel-SNAPSHOT.jar
> 
> I think you will also include addressing mar, right? It should be
> there. 
> 
> 
>> yes. I fogot to metion it. repository directory should have the
>> addressing.mar
>> and have to roll all the jars to axis2-core.jar.
> 
> 
>> ws  jars
>> 1. axiom-api-20071017.164440-781.jar
>> 2. axiom-impl-20071017.164440-780.jar (
>> (do we need axiom-dom-20071017.164440-780.jar?)
> 
> Yes we do need it.
> 
> 
>> ok so we add this.
> 
>> 3. neethi-20071017.164823-761.jar
>> 4. woden-api-1.0-incubating-20071018.161106-2.jar
>> 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
>> 6. wsdl4j-1.6.2.jar
>> 7. XmlSchema-SNAPSHOT.jar
> 
>> other jars
>> 1. activation-1.1.jar
>> 2. annogen-0.1.0.jar
>> 3. backport-util-concurrent-2.2.jar
>> 4. commons-codec-1.3.jar
>> 5. commons-fileupload-1.1.1.jar
>> 6. commons-httpclient-3.0.1.jar
>> 7. commons-io-1.2.jar
>> 8. commons-logging-1.1.jar
> 
> Grrrrr !!!!
> 
>> 9. geronimo-annotation_1.0_spec-1.1.jar
> 
> What is this for? If this is for annotations processing, IIRC annogen
> does the same thing. Please correct me if I am wrong.
> 
> 
>> I am also not sure. I put this to be in safe side.  I thought is may
>> need when
>> annotation processing with POJO. or is it something use with jax-ws?
> 
>> 10. geronimo-stax-api_1.0_spec- 1.0.jar
>> 11. httpcore-4.0-alpha5.jar
>> 12. httpcore-nio-4.0-alpha5.jar
>> 13. httpcore-niossl-4.0-alpha5.jar
>> 14. jalopy-1.5rc3.jar
> 
> Do we need this. IIRC, this is to pretty print generated code, right? I
> prefer removing this.
> 
> 
>> yes. we don't need this.
> 
>> 15. jaxen-1.1.1.jar
>> 16. jettison-1.0-RC1.jar
> 
> Do we need JSON support by default? I think we don't. Since we are not
> including json module, we can remove this.
> 
> 
>> I thought  there may be a dependency for axiom. if axiom do not need this
>> should remove.
> 
> Thanks,
> Chinthaka

- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
<ma...@ws.apache.org>
For additional commands, e-mail: axis-dev-help@ws.apache.org
<ma...@ws.apache.org>




> -- 
> Amila Suriarachchi,
> WSO2 Inc.

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

iD8DBQFHLoFejON2uBzUhh8RApmWAJsFoB1j3LREmMqAYGlx0zrssf9YXACgk7mL
ZX2qSp7yp6tVJOXUCZJ1onk=
=uEX2
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Axis2 Release Restructuring

Posted by Amila Suriarachchi <am...@gmail.com>.

So here are the changes we going to do.

On 11/2/07, Eran Chinthaka <ch...@opensource.lk> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Amila Suriarachchi wrote:
>
> > So the minimal distribution contains the following features
> > 1. Codegen support with adb
> > 2. POJO support
> > 3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
> > 4. Addressing
> > 5. Samples ( only for above features)
> >
> > is this enogh or is there any thing to add or remove?
>
> This is what I thought also.
>
> >
> > As I guess here are the jars we need for that,
> >
> > Axis2 jars
> > 1. axis2-adb-codegen-SNAPSHOT.jar
> > 2. axis2-adb-SNAPSHOT.jar
> > 3. axis2-codegen-SNAPSHOT.jar
> > 4. axis2-java2wsdl-SNAPSHOT.jar
> > 5. axis2-kernel-SNAPSHOT.jar
>
> I think you will also include addressing mar, right? It should be there.


yes. I fogot to metion it. repository directory should have the
addressing.mar
and have to roll all the jars to axis2-core.jar.

>
> > ws  jars
> > 1. axiom-api-20071017.164440-781.jar
> > 2. axiom-impl-20071017.164440-780.jar (
> > (do we need axiom-dom-20071017.164440-780.jar?)
>
> Yes we do need it.


ok so we add this.

> 3. neethi-20071017.164823-761.jar
> > 4. woden-api-1.0-incubating-20071018.161106-2.jar
> > 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> > 6. wsdl4j-1.6.2.jar
> > 7. XmlSchema-SNAPSHOT.jar
> >
> > other jars
> > 1. activation-1.1.jar
> > 2. annogen-0.1.0.jar
> > 3. backport-util-concurrent-2.2.jar
> > 4. commons-codec-1.3.jar
> > 5. commons-fileupload-1.1.1.jar
> > 6. commons-httpclient-3.0.1.jar
> > 7. commons-io-1.2.jar
> > 8. commons-logging-1.1.jar
>
> Grrrrr !!!!
>
> > 9. geronimo-annotation_1.0_spec-1.1.jar
>
> What is this for? If this is for annotations processing, IIRC annogen
> does the same thing. Please correct me if I am wrong.


I am also not sure. I put this to be in safe side.  I thought is may need
when
annotation processing with POJO. or is it something use with jax-ws?

> 10. geronimo-stax-api_1.0_spec-1.0.jar
> > 11. httpcore-4.0-alpha5.jar
> > 12. httpcore-nio-4.0-alpha5.jar
> > 13. httpcore-niossl-4.0-alpha5.jar
> > 14. jalopy-1.5rc3.jar
>
> Do we need this. IIRC, this is to pretty print generated code, right? I
> prefer removing this.


yes. we don't need this.

> 15. jaxen-1.1.1.jar
> > 16. jettison-1.0-RC1.jar
>
> Do we need JSON support by default? I think we don't. Since we are not
> including json module, we can remove this.


I thought  there may be a dependency for axiom. if axiom do not need this
should remove.

Thanks,
> Chinthaka
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHKov7jON2uBzUhh8RAjWfAKCVord/g/neqrbAmAXWUFWZOEY/VwCgrdUB
> lFooE+1VYke2p2YsEjw9thE=
> =wPWV
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Axis2 Release Restructuring

Posted by Eran Chinthaka <ch...@opensource.lk>.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Amila Suriarachchi wrote:

> So the minimal distribution contains the following features
> 1. Codegen support with adb
> 2. POJO support
> 3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
> 4. Addressing
> 5. Samples ( only for above features)
> 
> is this enogh or is there any thing to add or remove?

This is what I thought also.

> 
> As I guess here are the jars we need for that,
> 
> Axis2 jars
> 1. axis2-adb-codegen-SNAPSHOT.jar
> 2. axis2-adb-SNAPSHOT.jar
> 3. axis2-codegen-SNAPSHOT.jar
> 4. axis2-java2wsdl-SNAPSHOT.jar
> 5. axis2-kernel-SNAPSHOT.jar

I think you will also include addressing mar, right? It should be there.

> 
> ws  jars
> 1. axiom-api-20071017.164440-781.jar
> 2. axiom-impl-20071017.164440-780.jar (
> (do we need axiom-dom-20071017.164440-780.jar?)

Yes we do need it.

> 3. neethi-20071017.164823-761.jar
> 4. woden-api-1.0-incubating-20071018.161106-2.jar
> 5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
> 6. wsdl4j-1.6.2.jar
> 7. XmlSchema-SNAPSHOT.jar
> 
> other jars
> 1. activation-1.1.jar
> 2. annogen-0.1.0.jar
> 3. backport-util-concurrent-2.2.jar
> 4. commons-codec-1.3.jar
> 5. commons-fileupload-1.1.1.jar
> 6. commons-httpclient-3.0.1.jar
> 7. commons-io-1.2.jar
> 8. commons-logging-1.1.jar

Grrrrr !!!!

> 9. geronimo-annotation_1.0_spec-1.1.jar

What is this for? If this is for annotations processing, IIRC annogen
does the same thing. Please correct me if I am wrong.

> 10. geronimo-stax-api_1.0_spec-1.0.jar
> 11. httpcore-4.0-alpha5.jar
> 12. httpcore-nio-4.0-alpha5.jar
> 13. httpcore-niossl-4.0-alpha5.jar
> 14. jalopy-1.5rc3.jar

Do we need this. IIRC, this is to pretty print generated code, right? I
prefer removing this.

> 15. jaxen-1.1.1.jar
> 16. jettison-1.0-RC1.jar

Do we need JSON support by default? I think we don't. Since we are not
including json module, we can remove this.

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

iD8DBQFHKov7jON2uBzUhh8RAjWfAKCVord/g/neqrbAmAXWUFWZOEY/VwCgrdUB
lFooE+1VYke2p2YsEjw9thE=
=wPWV
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Axis2 Release Restructuring

Posted by Lawrence Mandel <lm...@ca.ibm.com>.

Hi Amila,

Thanks for summarizing the conversation. I take it your summary is for the 
Axis2 server bundle that's been discussed. Two issues:

1. Will the 5 Axis2 jars be rolled up into a single Axis2-server jar as 
has been requested and discussed?
2. You listed
woden-impl-dom-1.0-incubating-20071018.161106-2.jar 
Woden has an Axiom based implementation that I thought was contributed to 
support Axis2. Is the Axiom implementation not in use in Axis2?

Thanks,

Lawrence

"Amila Suriarachchi" <am...@gmail.com> 
11/01/2007 12:16 AM
Please respond to
axis-dev@ws.apache.org

To
axis-dev@ws.apache.org
cc

Subject
Re: [Axis2] Axis2 Release Restructuring

So shall we first conclue what should be included into the minimal 
distribution?

I would like to discribe the minimal distribution as follows,
It inclues the minimal set of jars which some one needs to creates a 
webservice 
using either 
1. Contract first approach
         here we going to provide only the default data binding support
2. Code first approach 
         POJO support

and access them using the generated stub or 
RPCService client. Here he can use addressing since it is a basic we
service spec and only with http transport.

So the minimal distribution contains the following features
1. Codegen support with adb
2. POJO support 
3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
4. Addressing
5. Samples ( only for above features)

is this enogh or is there any thing to add or remove?

As I guess here are the jars we need for that, 

Axis2 jars
1. axis2-adb-codegen-SNAPSHOT.jar
2. axis2-adb-SNAPSHOT.jar
3. axis2-codegen-SNAPSHOT.jar
4. axis2-java2wsdl-SNAPSHOT.jar
5. axis2-kernel-SNAPSHOT.jar

ws  jars
1. axiom-api-20071017.164440-781.jar 
2. axiom-impl-20071017.164440-780.jar (
(do we need axiom-dom-20071017.164440-780.jar?)
3. neethi-20071017.164823-761.jar
4. woden-api-1.0-incubating-20071018.161106-2.jar
5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar 
6. wsdl4j-1.6.2.jar
7. XmlSchema-SNAPSHOT.jar

other jars
1. activation-1.1.jar
2. annogen-0.1.0.jar
3. backport-util-concurrent-2.2.jar
4. commons-codec-1.3.jar
5. commons-fileupload-1.1.1.jar 
6. commons-httpclient-3.0.1.jar
7. commons-io-1.2.jar
8. commons-logging-1.1.jar
9. geronimo-annotation_1.0_spec-1.1.jar
10. geronimo-stax-api_1.0_spec-1.0.jar
11. httpcore-4.0-alpha5.jar
12. httpcore-nio-4.0-alpha5.jar 
13. httpcore-niossl-4.0-alpha5.jar
14. jalopy-1.5rc3.jar
15. jaxen-1.1.1.jar
16. jettison-1.0-RC1.jar
17. log4j-1.2.14.jar
18. stax-api-1.0.1.jar
19. wstx-asl-3.2.1.jar
20. xalan-2.7.0.jar
21. xercesImpl-2.8.1.jar
22. xml-apis-1.3.03.jar

Are there any thing to add or remove?
Here any way 34 jars are there. and we have left 24 jars.

thanks,
Amila.

On 10/30/07, Eran Chinthaka <ch...@opensource.lk> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Amila Suriarachchi wrote:

>
> I have misunderstood the thing.
> you mean
> 1. minimal distribution with
>        server,client and kernal 
> 2. full distribution with
>        minmal + optional
> 3. Tools distribution with
>        tools

Exactly yes. I am not sure whether we need to expand full distro also in
to two. Are we releasing all the modules with our current standard distro. 

> what I want to say is that we need a proper boundry definition about
> what should goes to minimal distribution.
> with some logical reasoning. Otherwise we have to discuss this again
> when implementing. 

Agreed. That is why I made this a proposal rather than a vote :). We
discussed this packaging issues couple of times and changed packaging
couple of time. When Axis2 evolves and we get more insight in to user 
experience, we might want to change ourselves to cater for this
requirements. I myself found it bit difficult/confused to use Axis2 once
as a user. That is why I am proposing sth like this.

Yes, let's discuss about this. And we might also want to revise this 
once the next release manager (Amila will it be you ;) ) try to
implement this packaging proposal.

So are we agreed to this three level distro?

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

iD8DBQFHJ09HjON2uBzUhh8RAoDSAJ9DKYjtCRqEU/jiQnMnKm7oF0UzzQCgqd5z
6SUmDsDsirjOF6j5WuAu9EA= 
=ZWKs
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org 
For additional commands, e-mail: axis-dev-help@ws.apache.org

-- 
Amila Suriarachchi,
WSO2 Inc. 

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Axis2 Release Restructuring

Posted by Amila Suriarachchi <am...@gmail.com>.

So shall we first conclue what should be included into the minimal
distribution?

I would like to discribe the minimal distribution as follows,
It inclues the minimal set of jars which some one needs to creates a
webservice
using either
1. Contract first approach
         here we going to provide only the default data binding support
2. Code first approach
         POJO support

and access them using the generated stub or
RPCService client. Here he can use addressing since it is a basic we
service spec and only with http transport.

So the minimal distribution contains the following features
1. Codegen support with adb
2. POJO support
3. MTOM (when we includes the axiom and axis2 kernal anyway we get this)
4. Addressing
5. Samples ( only for above features)

is this enogh or is there any thing to add or remove?

As I guess here are the jars we need for that,

Axis2 jars
1. axis2-adb-codegen-SNAPSHOT.jar
2. axis2-adb-SNAPSHOT.jar
3. axis2-codegen-SNAPSHOT.jar
4. axis2-java2wsdl-SNAPSHOT.jar
5. axis2-kernel-SNAPSHOT.jar

ws  jars
1. axiom-api-20071017.164440-781.jar
2. axiom-impl-20071017.164440-780.jar (
(do we need axiom-dom-20071017.164440-780.jar?)
3. neethi-20071017.164823-761.jar
4. woden-api-1.0-incubating-20071018.161106-2.jar
5. woden-impl-dom-1.0-incubating-20071018.161106-2.jar
6. wsdl4j-1.6.2.jar
7. XmlSchema-SNAPSHOT.jar

other jars
1. activation-1.1.jar
2. annogen-0.1.0.jar
3. backport-util-concurrent-2.2.jar
4. commons-codec-1.3.jar
5. commons-fileupload-1.1.1.jar
6. commons-httpclient-3.0.1.jar
7. commons-io-1.2.jar
8. commons-logging-1.1.jar
9. geronimo-annotation_1.0_spec-1.1.jar
10. geronimo-stax-api_1.0_spec-1.0.jar
11. httpcore-4.0-alpha5.jar
12. httpcore-nio-4.0-alpha5.jar
13. httpcore-niossl-4.0-alpha5.jar
14. jalopy-1.5rc3.jar
15. jaxen-1.1.1.jar
16. jettison-1.0-RC1.jar
17. log4j-1.2.14.jar
18. stax-api-1.0.1.jar
19. wstx-asl-3.2.1.jar
20. xalan-2.7.0.jar
21. xercesImpl-2.8.1.jar
22. xml-apis-1.3.03.jar

Are there any thing to add or remove?
Here any way 34 jars are there. and we have left 24 jars.

thanks,
Amila.

On 10/30/07, Eran Chinthaka <ch...@opensource.lk> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Amila Suriarachchi wrote:
>
> >
> > I have misunderstood the thing.
> > you mean
> > 1. minimal distribution with
> >        server,client and kernal
> > 2. full distribution with
> >        minmal + optional
> > 3. Tools distribution with
> >        tools
>
> Exactly yes. I am not sure whether we need to expand full distro also in
> to two. Are we releasing all the modules with our current standard distro.
>
> > what I want to say is that we need a proper boundry definition about
> > what should goes to minimal distribution.
> > with some logical reasoning. Otherwise we have to discuss this again
> > when implementing.
>
> Agreed. That is why I made this a proposal rather than a vote :). We
> discussed this packaging issues couple of times and changed packaging
> couple of time. When Axis2 evolves and we get more insight in to user
> experience, we might want to change ourselves to cater for this
> requirements. I myself found it bit difficult/confused to use Axis2 once
> as a user. That is why I am proposing sth like this.
>
> Yes, let's discuss about this. And we might also want to revise this
> once the next release manager (Amila will it be you ;) ) try to
> implement this packaging proposal.
>
> So are we agreed to this three level distro?
>
> Thanks,
> Chinthaka
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHJ09HjON2uBzUhh8RAoDSAJ9DKYjtCRqEU/jiQnMnKm7oF0UzzQCgqd5z
> 6SUmDsDsirjOF6j5WuAu9EA=
> =ZWKs
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Axis2 Release Restructuring

Posted by Eran Chinthaka <ch...@opensource.lk>.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Amila Suriarachchi wrote:

> 
> I have misunderstood the thing.
> you mean
> 1. minimal distribution with
>        server,client and kernal
> 2. full distribution with
>        minmal + optional
> 3. Tools distribution with
>        tools

Exactly yes. I am not sure whether we need to expand full distro also in
to two. Are we releasing all the modules with our current standard distro.

> what I want to say is that we need a proper boundry definition about
> what should goes to minimal distribution.
> with some logical reasoning. Otherwise we have to discuss this again
> when implementing.

Agreed. That is why I made this a proposal rather than a vote :). We
discussed this packaging issues couple of times and changed packaging
couple of time. When Axis2 evolves and we get more insight in to user
experience, we might want to change ourselves to cater for this
requirements. I myself found it bit difficult/confused to use Axis2 once
as a user. That is why I am proposing sth like this.

Yes, let's discuss about this. And we might also want to revise this
once the next release manager (Amila will it be you ;) ) try to
implement this packaging proposal.

So are we agreed to this three level distro?

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

iD8DBQFHJ09HjON2uBzUhh8RAoDSAJ9DKYjtCRqEU/jiQnMnKm7oF0UzzQCgqd5z
6SUmDsDsirjOF6j5WuAu9EA=
=ZWKs
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Axis2 Release Restructuring

Posted by Amila Suriarachchi <am...@gmail.com>.

On 10/30/07, Eran Chinthaka <ch...@chinthaka.org> wrote:
>
> Hi Amila,
>
> On 10/29/07, Amila Suriarachchi <am...@gmail.com> wrote:
> >
> > 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
>
>
> Why do we have Kernel,  Server and Client separate. I like to have minimal
> set of jars in one distro. That doesn't mean we will have server and client
> separate. Even if we have them separate they will have the same content. So
> as I proposed earlier, let's collapse kernel (whatever you meant to have in
> it), server and client in to one distro. But let's ask David to pick a name
> for that :D
>

I have misunderstood the thing.
you mean
1. minimal distribution with
       server,client and kernal
2. full distribution with
       minmal + optional
3. Tools distribution with
       tools


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)
>
>
> Well whatever required will be shipped in core and full distros. And tools
> distro will have only the deps that they need in addition to what core
> distro has.
>
> Does Axis2 server and Axis2 Client supposed to have only the Runtime jars?
>
>
> No.
>
> In user list I saw lot of people ask
> > this question. What is the minimal set of jars needed at runtime?
>
>
> I am talking about minimal set of jars to use Axis2. See the modules list
> I included in my earlier email.
>
> 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.
>
>
> You can put them inside tools. But IMO, they should also come one
> (get-name-from-David) release.
>
> why you have put the samples to the kernal distribution?
>
>
> I hope this is clarified from the above answers.
>
> what about the jaxws, fastinfoset. mex etc are we going to put them all to
> > optional package?
>
>
> Yes. And some of these will come in full distro which will be almost
> equivalent to what we are releasing as standard distro, right now.
>
> 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?
>
>
> Well, again see the modules that I have proposed. Whatever jars required
> for those modules will be shipped with them.
>

what I want to say is that we need a proper boundry definition about what
should goes to minimal distribution.
with some logical reasoning. Otherwise we have to discuss this again when
implementing.

Thanks,
Amila.

Thanks,
> Chinthaka
>
> ( I hope you will have less questions next time ;) )
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Re: [Axis2] Axis2 Release Restructuring

Posted by Eran Chinthaka <ch...@chinthaka.org>.

Hi Amila,

On 10/29/07, Amila Suriarachchi <am...@gmail.com> wrote:
>
> 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

Why do we have Kernel,  Server and Client separate. I like to have minimal
set of jars in one distro. That doesn't mean we will have server and client
separate. Even if we have them separate they will have the same content. So
as I proposed earlier, let's collapse kernel (whatever you meant to have in
it), server and client in to one distro. But let's ask David to pick a name
for that :D

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)

Well whatever required will be shipped in core and full distros. And tools
distro will have only the deps that they need in addition to what core
distro has.

Does Axis2 server and Axis2 Client supposed to have only the Runtime jars?

No.

In user list I saw lot of people ask
> this question. What is the minimal set of jars needed at runtime?

I am talking about minimal set of jars to use Axis2. See the modules list I
included in my earlier email.

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.

You can put them inside tools. But IMO, they should also come one
(get-name-from-David) release.

why you have put the samples to the kernal distribution?

I hope this is clarified from the above answers.

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

Yes. And some of these will come in full distro which will be almost
equivalent to what we are releasing as standard distro, right now.

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?

Well, again see the modules that I have proposed. Whatever jars required for
those modules will be shipped with them.

Thanks,
Chinthaka

( I hope you will have less questions next time ;) )

Re: [Axis2] Axis2 Release Restructuring

Posted by Lawrence Mandel <lm...@ca.ibm.com>.

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" <am...@gmail.com> 
10/29/2007 01:20 AM
Please respond to
axis-dev@ws.apache.org


To
axis-dev@ws.apache.org
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 <ch...@opensource.lk> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org 




-- 
Amila Suriarachchi,
WSO2 Inc. 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org