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/11/01 05:16:21 UTC

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.

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