You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by da...@opensource.lk on 2004/03/25 09:41:18 UTC
Axis C++ version 1.1 Release Plan
Hi all,
I volunteer to be the release manager for the Axis C++ 1.1 release.
Following is the release plan.
Axis C++ 1.1 Release Plan
This is the release plan for Axis C++ version 1.1. This version will be a
snapshot of all the changes since 1.0, including critical bug fixes and
tests. The main goal is to provide a more stable release than version 1.0.
Changes from 1.0 to 1.1:
- XML parser abstraction layer
Support for Expat (1.95.7) Xerces (2.2.5)
- SSL transport support
- Admin Client to support dynamic deployment and undepolyment of services
- Document Literal and RPC style support
- Stub/Skeleton genearation both in C and C++
- Many critical bug fixes
- Updated documentation
Release Criteria:
- Functional tests pass
- Test on installation procedures
- Test on different versions of Apache web server(1.3.xx, 2.0.xx)
- Test samples on different platforms (Linux, Microsoft Windows)
- Fix pending bugs to-date
Dates:
The following dates are proposed:
Code freeze March 30, 2004
Release alpha version March 31, 2004
Release beta version April 05, 2004
Release 1.1 April 10, 2004
damitha
Re: Axis C++ version 1.1 Release Plan
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+1!
Sanjiva.
----- Original Message -----
From: <da...@opensource.lk>
To: <ax...@ws.apache.org>; <ax...@ws.apache.org>;
<ax...@ws.apache.org>; <ax...@ws.apache.org>
Sent: Thursday, March 25, 2004 2:41 PM
Subject: Axis C++ version 1.1 Release Plan
> Hi all,
> I volunteer to be the release manager for the Axis C++ 1.1 release.
> Following is the release plan.
>
> Axis C++ 1.1 Release Plan
>
> This is the release plan for Axis C++ version 1.1. This version will be a
> snapshot of all the changes since 1.0, including critical bug fixes and
> tests. The main goal is to provide a more stable release than version 1.0.
>
> Changes from 1.0 to 1.1:
> - XML parser abstraction layer
> Support for Expat (1.95.7) Xerces (2.2.5)
> - SSL transport support
> - Admin Client to support dynamic deployment and undepolyment of
services
> - Document Literal and RPC style support
> - Stub/Skeleton genearation both in C and C++
> - Many critical bug fixes
> - Updated documentation
>
>
> Release Criteria:
>
> - Functional tests pass
> - Test on installation procedures
> - Test on different versions of Apache web server(1.3.xx, 2.0.xx)
> - Test samples on different platforms (Linux, Microsoft Windows)
> - Fix pending bugs to-date
>
> Dates:
>
> The following dates are proposed:
> Code freeze March 30, 2004
> Release alpha version March 31, 2004
> Release beta version April 05, 2004
> Release 1.1 April 10, 2004
>
> damitha
>
Re: Axis C++ version 1.1 Release Plan
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+1!
Sanjiva.
----- Original Message -----
From: <da...@opensource.lk>
To: <ax...@ws.apache.org>; <ax...@ws.apache.org>;
<ax...@ws.apache.org>; <ax...@ws.apache.org>
Sent: Thursday, March 25, 2004 2:41 PM
Subject: Axis C++ version 1.1 Release Plan
> Hi all,
> I volunteer to be the release manager for the Axis C++ 1.1 release.
> Following is the release plan.
>
> Axis C++ 1.1 Release Plan
>
> This is the release plan for Axis C++ version 1.1. This version will be a
> snapshot of all the changes since 1.0, including critical bug fixes and
> tests. The main goal is to provide a more stable release than version 1.0.
>
> Changes from 1.0 to 1.1:
> - XML parser abstraction layer
> Support for Expat (1.95.7) Xerces (2.2.5)
> - SSL transport support
> - Admin Client to support dynamic deployment and undepolyment of
services
> - Document Literal and RPC style support
> - Stub/Skeleton genearation both in C and C++
> - Many critical bug fixes
> - Updated documentation
>
>
> Release Criteria:
>
> - Functional tests pass
> - Test on installation procedures
> - Test on different versions of Apache web server(1.3.xx, 2.0.xx)
> - Test samples on different platforms (Linux, Microsoft Windows)
> - Fix pending bugs to-date
>
> Dates:
>
> The following dates are proposed:
> Code freeze March 30, 2004
> Release alpha version March 31, 2004
> Release beta version April 05, 2004
> Release 1.1 April 10, 2004
>
> damitha
>
Re: Axis C++ version 1.1 Release Plan
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+1!
Sanjiva.
----- Original Message -----
From: <da...@opensource.lk>
To: <ax...@ws.apache.org>; <ax...@ws.apache.org>;
<ax...@ws.apache.org>; <ax...@ws.apache.org>
Sent: Thursday, March 25, 2004 2:41 PM
Subject: Axis C++ version 1.1 Release Plan
> Hi all,
> I volunteer to be the release manager for the Axis C++ 1.1 release.
> Following is the release plan.
>
> Axis C++ 1.1 Release Plan
>
> This is the release plan for Axis C++ version 1.1. This version will be a
> snapshot of all the changes since 1.0, including critical bug fixes and
> tests. The main goal is to provide a more stable release than version 1.0.
>
> Changes from 1.0 to 1.1:
> - XML parser abstraction layer
> Support for Expat (1.95.7) Xerces (2.2.5)
> - SSL transport support
> - Admin Client to support dynamic deployment and undepolyment of
services
> - Document Literal and RPC style support
> - Stub/Skeleton genearation both in C and C++
> - Many critical bug fixes
> - Updated documentation
>
>
> Release Criteria:
>
> - Functional tests pass
> - Test on installation procedures
> - Test on different versions of Apache web server(1.3.xx, 2.0.xx)
> - Test samples on different platforms (Linux, Microsoft Windows)
> - Fix pending bugs to-date
>
> Dates:
>
> The following dates are proposed:
> Code freeze March 30, 2004
> Release alpha version March 31, 2004
> Release beta version April 05, 2004
> Release 1.1 April 10, 2004
>
> damitha
>
Re: Samples fail when run severaltimes
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi All,
The problem remains. Once you build all from scratch and run the samples for the first time all
works fine.
But when samples are tried multiple times, they start working differently time to time.
Thanks,
Samisa...
--- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> Hi All,
> Looks like this was my mistake. I had mixed up some of the old code with new.
>
> The latest CVS code samples work fine.
>
> Sorry for the confusion caused.
> Thanks,
> Samisa...
>
>
> --- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> > Hi All,
> > I am using the latest CVS code on Linux with Xerces and Apache2
> > With the latest CVS code the samples behave differetly when they are run multiple times
> >
> > This happen for both rpc and doc style services.
> > When doclitgroupB was run several times in sequence, the result differes (see the output
> at
> > the bottom)
> > I got a similar situation when I ran cgroupB and groupB one after other several times.
> > cgroupB
> > always succeeds but groupB fails time to time.
> >
> > I doubt this to be due to a buffer clearing problem but not sure.
> >
> > Please help. (see the sample output below)
> > Thanks
> > Samisa...
> >
> > samisa@localhost
> > /home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
> > Usage :
> > ./doclitgroupB <server> <port>
> >
> > Sending Requests to Server http://localhost:80 ........
> >
> > invoking echoNestedArray...
> > failed
> > invoking echoNestedStruct...
> > failed
> > invoking echoSimpleTypesAsStruct...
> > successful
> > invoking echoStructAsSimpleTypes...
> > successful
> >
> > Segmentation fault
> > [samisa@localhost
> > /home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
> > Usage :
> > ./doclitgroupB <server> <port>
> >
> > Sending Requests to Server http://localhost:80 ........
> >
> > invoking echoNestedArray...
> > failed
> > invoking echoNestedStruct...
> > failed
> > invoking echoSimpleTypesAsStruct...
> > failed
> > invoking echoStructAsSimpleTypes...
> > failed
> >
> > Segmentation fault
> > [samisa@localhost
> > /home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
> > Usage :
> > ./doclitgroupB <server> <port>
> >
> > Sending Requests to Server http://localhost:80 ........
> >
> > invoking echoNestedArray...
> > successful
> > invoking echoNestedStruct...
> > successful
> > invoking echoSimpleTypesAsStruct...
> > failed
> > invoking echoStructAsSimpleTypes...
> > failed
> >
> > Segmentation fault
> > [samisa@localhost
> > /home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
> > Usage :
> > ./doclitgroupB <server> <port>
> >
> > Sending Requests to Server http://localhost:80 ........
> >
> > invoking echoNestedArray...
> > failed
> > invoking echoNestedStruct...
> > failed
> > invoking echoSimpleTypesAsStruct...
> > successful
> > invoking echoStructAsSimpleTypes...
> > successful
> >
> > Segmentation fault
> > [samisa@localhost
> > /home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
> > Usage :
> > ./doclitgroupB <server> <port>
> >
> > Sending Requests to Server http://localhost:80 ........
> >
> > invoking echoNestedArray...
> > failed
> > invoking echoNestedStruct...
> > failed
> > invoking echoSimpleTypesAsStruct...
> > failed
> > invoking echoStructAsSimpleTypes...
> > failed
> >
> > Segmentation fault
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Small Business $15K Web Design Giveaway
> > http://promotions.yahoo.com/design_giveaway/
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business $15K Web Design Giveaway
> http://promotions.yahoo.com/design_giveaway/
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
Re: Samples fail when run severaltimes
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi All,
Looks like this was my mistake. I had mixed up some of the old code with new.
The latest CVS code samples work fine.
Sorry for the confusion caused.
Thanks,
Samisa...
--- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> Hi All,
> I am using the latest CVS code on Linux with Xerces and Apache2
> With the latest CVS code the samples behave differetly when they are run multiple times
>
> This happen for both rpc and doc style services.
> When doclitgroupB was run several times in sequence, the result differes (see the output at
> the bottom)
> I got a similar situation when I ran cgroupB and groupB one after other several times.
> cgroupB
> always succeeds but groupB fails time to time.
>
> I doubt this to be due to a buffer clearing problem but not sure.
>
> Please help. (see the sample output below)
> Thanks
> Samisa...
>
> samisa@localhost
> /home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
> Usage :
> ./doclitgroupB <server> <port>
>
> Sending Requests to Server http://localhost:80 ........
>
> invoking echoNestedArray...
> failed
> invoking echoNestedStruct...
> failed
> invoking echoSimpleTypesAsStruct...
> successful
> invoking echoStructAsSimpleTypes...
> successful
>
> Segmentation fault
> [samisa@localhost
> /home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
> Usage :
> ./doclitgroupB <server> <port>
>
> Sending Requests to Server http://localhost:80 ........
>
> invoking echoNestedArray...
> failed
> invoking echoNestedStruct...
> failed
> invoking echoSimpleTypesAsStruct...
> failed
> invoking echoStructAsSimpleTypes...
> failed
>
> Segmentation fault
> [samisa@localhost
> /home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
> Usage :
> ./doclitgroupB <server> <port>
>
> Sending Requests to Server http://localhost:80 ........
>
> invoking echoNestedArray...
> successful
> invoking echoNestedStruct...
> successful
> invoking echoSimpleTypesAsStruct...
> failed
> invoking echoStructAsSimpleTypes...
> failed
>
> Segmentation fault
> [samisa@localhost
> /home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
> Usage :
> ./doclitgroupB <server> <port>
>
> Sending Requests to Server http://localhost:80 ........
>
> invoking echoNestedArray...
> failed
> invoking echoNestedStruct...
> failed
> invoking echoSimpleTypesAsStruct...
> successful
> invoking echoStructAsSimpleTypes...
> successful
>
> Segmentation fault
> [samisa@localhost
> /home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
> Usage :
> ./doclitgroupB <server> <port>
>
> Sending Requests to Server http://localhost:80 ........
>
> invoking echoNestedArray...
> failed
> invoking echoNestedStruct...
> failed
> invoking echoSimpleTypesAsStruct...
> failed
> invoking echoStructAsSimpleTypes...
> failed
>
> Segmentation fault
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business $15K Web Design Giveaway
> http://promotions.yahoo.com/design_giveaway/
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
Samples fail when run severaltimes
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi All,
I am using the latest CVS code on Linux with Xerces and Apache2
With the latest CVS code the samples behave differetly when they are run multiple times
This happen for both rpc and doc style services.
When doclitgroupB was run several times in sequence, the result differes (see the output at
the bottom)
I got a similar situation when I ran cgroupB and groupB one after other several times. cgroupB
always succeeds but groupB fails time to time.
I doubt this to be due to a buffer clearing problem but not sure.
Please help. (see the sample output below)
Thanks
Samisa...
samisa@localhost
/home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
Usage :
./doclitgroupB <server> <port>
Sending Requests to Server http://localhost:80 ........
invoking echoNestedArray...
failed
invoking echoNestedStruct...
failed
invoking echoSimpleTypesAsStruct...
successful
invoking echoStructAsSimpleTypes...
successful
Segmentation fault
[samisa@localhost
/home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
Usage :
./doclitgroupB <server> <port>
Sending Requests to Server http://localhost:80 ........
invoking echoNestedArray...
failed
invoking echoNestedStruct...
failed
invoking echoSimpleTypesAsStruct...
failed
invoking echoStructAsSimpleTypes...
failed
Segmentation fault
[samisa@localhost
/home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
Usage :
./doclitgroupB <server> <port>
Sending Requests to Server http://localhost:80 ........
invoking echoNestedArray...
successful
invoking echoNestedStruct...
successful
invoking echoSimpleTypesAsStruct...
failed
invoking echoStructAsSimpleTypes...
failed
Segmentation fault
[samisa@localhost
/home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
Usage :
./doclitgroupB <server> <port>
Sending Requests to Server http://localhost:80 ........
invoking echoNestedArray...
failed
invoking echoNestedStruct...
failed
invoking echoSimpleTypesAsStruct...
successful
invoking echoStructAsSimpleTypes...
successful
Segmentation fault
[samisa@localhost
/home/samisa/cpp/ws-axis/c/samples/client/interoptests/doclitgroupB]$./doclitgroupB
Usage :
./doclitgroupB <server> <port>
Sending Requests to Server http://localhost:80 ........
invoking echoNestedArray...
failed
invoking echoNestedStruct...
failed
invoking echoSimpleTypesAsStruct...
failed
invoking echoStructAsSimpleTypes...
failed
Segmentation fault
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
Re: Some comments on source distibution for R1.1
Posted by da...@opensource.lk.
Hi,
Following I've given some of my ideas of your attached file.
1. Please add to configure.ac the following to help Xerces parser users
#CPPFLAGS="-Wall -Wshadow -DUSE_XERCES_PARSER"
#LDFLAGS="-s -L$AXISCPP_HOME/lib/xercesc -lxerces-c -lstdc++"
---------------------
This is done. I've mentioned some of the problems related to LDFLAGS in a
seperate mail.
1. Update the INSTALL file in the root source distribution folder to
reflect the
latest simple set of install steps
---------------------
This need to be done
2. when ./autogen.sh is run
Makefile.am: required file `./NEWS' not found
Makefile.am: required file `./README' not found
Makefile.am: required file `./AUTHORS' not found
Makefile.am: required file `./ChangeLog' not found
Add (empty) files for them to eliminate warnings
Also meaningful content could be added to them as well
----------------------
+1
3. runconfig script does not have runnig permissions. chmod 755 runconfig
(for
the benefit of those who use ./runconfig)
build.sh does not have running permissions (for those who wish to use
./build.sh)
------------------------------------------
+1
4. There are many compiler warnings. Can we eliminate them.
--------------------------------------
+1
5. It is critical to mention that most of the build problems are related
to not
seeting AXISCPP_HOME. (we can set this in buld.sh if it is not set already)
------------------------------------------
I think it is not an over burden to set some environment varibles when
installing an application. For example xercesc, tomcat and several favmous
application use this approach
6. How do I instruct configure to use either Expat or Xerces?
7. Installation guide is missing in docs
8. Can we get rid of linux, windows directories in docs directory and include
platform options within a single document, with seperate sections
--------------------
I don't understand why this is important. However xercesc also have all in
single doc with links.
9. Lets make the default build to be Apache 2 in configure.ac (as most of the
OSes bundle apache 2)
------------------
this is done.
10. We need to have a #if you use apache1.3 comment in configure.ac
--------------
done
11. Add LDFLAGS and CPPFLAGS in configure.ac so that swithcing parsers
becomes simple.
------------------
done
12. Can we add the parser selection as a parameter to configure script? When
./configure --help is run, it does not show anything related to the parser
selection. I think it should.
----------------------
this is good. but I don't know how to do this
13. We have to document the Expat specific steps and Xerces related steps
sperately. (this is a critical requirement of parser abstraction layer)
-------------------------
this should be done. +1
14.Remove the 'xerces' folder in include (this confuces with xercesc)
------------------------
removed
15. In deploy/axiscpp.conf I had to change apache to apache2 (apache2 is the
default install folder) Either we have to document this change or have a
mechanism to autogenerate during configuration
----------------------------
We need to document this.
16. What about users that use apache that comes bundled with OS installation?
Its good to have documentation for them as well
---------------------------
I've tested in such an environment. Steps are intuitive.
17. deploy/conf/server.wsdd reffers to /usr/local/apache2 (unlike
deploy/axiscpp.conf). Have to consider documenting for users with bundled
apache
and apache 1.3
18. Can we make samples and simple axis sever tobe bulit during intial
builsstep?
Then we can eliminate many redundent steps.
-------------------
I thought that building samples seperately is better. But I've seen expat
do as you said.
19. In configure.ac include the settings for Xerces parser as well and
keep them
commented (because expat is the default)
----------------------
commented???
20. In include directory Xerces subfolder is xercesc and in lib directory
Xerces
subfolder is xerces-c.
This is inconsistant. Lets use xercesc for both as it is the one used by
Xerces itself.
(But the lib name is xerces-c)
----------------------
done
> Hi All,
> I was trying out the source from the CVS over the weekend and came up
> with few suggestions to
> make the source distibution more user friendly.
>
> Most of the suggestions are focused for the Linux platform.
>
> Please see the attached text file.
> Thanks,
> Samisa...
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business $15K Web Design Giveaway
> http://promotions.yahoo.com/design_giveaway/
Re: Some comments on source distibution for R1.1
Posted by da...@opensource.lk.
Hi,
Following I've given some of my ideas of your attached file.
1. Please add to configure.ac the following to help Xerces parser users
#CPPFLAGS="-Wall -Wshadow -DUSE_XERCES_PARSER"
#LDFLAGS="-s -L$AXISCPP_HOME/lib/xercesc -lxerces-c -lstdc++"
---------------------
This is done. I've mentioned some of the problems related to LDFLAGS in a
seperate mail.
1. Update the INSTALL file in the root source distribution folder to
reflect the
latest simple set of install steps
---------------------
This need to be done
2. when ./autogen.sh is run
Makefile.am: required file `./NEWS' not found
Makefile.am: required file `./README' not found
Makefile.am: required file `./AUTHORS' not found
Makefile.am: required file `./ChangeLog' not found
Add (empty) files for them to eliminate warnings
Also meaningful content could be added to them as well
----------------------
+1
3. runconfig script does not have runnig permissions. chmod 755 runconfig
(for
the benefit of those who use ./runconfig)
build.sh does not have running permissions (for those who wish to use
./build.sh)
------------------------------------------
+1
4. There are many compiler warnings. Can we eliminate them.
--------------------------------------
+1
5. It is critical to mention that most of the build problems are related
to not
seeting AXISCPP_HOME. (we can set this in buld.sh if it is not set already)
------------------------------------------
I think it is not an over burden to set some environment varibles when
installing an application. For example xercesc, tomcat and several favmous
application use this approach
6. How do I instruct configure to use either Expat or Xerces?
7. Installation guide is missing in docs
8. Can we get rid of linux, windows directories in docs directory and include
platform options within a single document, with seperate sections
--------------------
I don't understand why this is important. However xercesc also have all in
single doc with links.
9. Lets make the default build to be Apache 2 in configure.ac (as most of the
OSes bundle apache 2)
------------------
this is done.
10. We need to have a #if you use apache1.3 comment in configure.ac
--------------
done
11. Add LDFLAGS and CPPFLAGS in configure.ac so that swithcing parsers
becomes simple.
------------------
done
12. Can we add the parser selection as a parameter to configure script? When
./configure --help is run, it does not show anything related to the parser
selection. I think it should.
----------------------
this is good. but I don't know how to do this
13. We have to document the Expat specific steps and Xerces related steps
sperately. (this is a critical requirement of parser abstraction layer)
-------------------------
this should be done. +1
14.Remove the 'xerces' folder in include (this confuces with xercesc)
------------------------
removed
15. In deploy/axiscpp.conf I had to change apache to apache2 (apache2 is the
default install folder) Either we have to document this change or have a
mechanism to autogenerate during configuration
----------------------------
We need to document this.
16. What about users that use apache that comes bundled with OS installation?
Its good to have documentation for them as well
---------------------------
I've tested in such an environment. Steps are intuitive.
17. deploy/conf/server.wsdd reffers to /usr/local/apache2 (unlike
deploy/axiscpp.conf). Have to consider documenting for users with bundled
apache
and apache 1.3
18. Can we make samples and simple axis sever tobe bulit during intial
builsstep?
Then we can eliminate many redundent steps.
-------------------
I thought that building samples seperately is better. But I've seen expat
do as you said.
19. In configure.ac include the settings for Xerces parser as well and
keep them
commented (because expat is the default)
----------------------
commented???
20. In include directory Xerces subfolder is xercesc and in lib directory
Xerces
subfolder is xerces-c.
This is inconsistant. Lets use xercesc for both as it is the one used by
Xerces itself.
(But the lib name is xerces-c)
----------------------
done
> Hi All,
> I was trying out the source from the CVS over the weekend and came up
> with few suggestions to
> make the source distibution more user friendly.
>
> Most of the suggestions are focused for the Linux platform.
>
> Please see the attached text file.
> Thanks,
> Samisa...
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business $15K Web Design Giveaway
> http://promotions.yahoo.com/design_giveaway/
Getting current CVS code working with Xerces Parser
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi All,
I was trying to get the Axis C++ working with the Xerces XML Parser on Linux platform.
I had to do the following changes.
1. Add to configure.ac the following to use Xerces parser
CPPFLAGS="-Wall -Wshadow -DUSE_XERCES_PARSER"
LDFLAGS="-s -L$AXISCPP_HOME/lib/xercesc -lxerces-c -lstdc++"
2. Fix compiler error
in file src/soap/SoapParserXerces.h #include "../xml/Qname.h" to #include "../xml/QName.h"
(note n --> N; Linux is case sensitive)
3. In src/soap/Makefile.am
3.1 Replace SoapParserExpat.cpp with SoapParserXerces.cpp
3.2 Add XercesHandler.cpp on top of SoapParserXerces.cpp
3.3 Add SoapInputSource.cpp on top of XercesHandler.cpp
3.4 Add SoapBinInputStream.cpp on top of SoapInputSource.cpp
4. In src/wsdd/Makefile.am
4.1 Replace WSDDDocumentExpat.cpp with WSDDDocumentXerces.cpp
Plese fix the compiler error in CVS code.
Is it possible to automate steps 3 and 4 somehow so that users do not have to edit Makefile.am
files?
Thanks,
Samisa...
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
Some comments on source distibution for R1.1
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi All,
I was trying out the source from the CVS over the weekend and came up with few suggestions to
make the source distibution more user friendly.
Most of the suggestions are focused for the Linux platform.
Please see the attached text file.
Thanks,
Samisa...
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
Re: Axis C++ version 1.1 Release Plan
Posted by Davanum Srinivas <di...@yahoo.com>.
+1 from me.
--- damitha@opensource.lk wrote:
> Hi all,
> I volunteer to be the release manager for the Axis C++ 1.1 release.
> Following is the release plan.
>
> Axis C++ 1.1 Release Plan
>
> This is the release plan for Axis C++ version 1.1. This version will be a
> snapshot of all the changes since 1.0, including critical bug fixes and
> tests. The main goal is to provide a more stable release than version 1.0.
>
> Changes from 1.0 to 1.1:
> - XML parser abstraction layer
> Support for Expat (1.95.7) Xerces (2.2.5)
> - SSL transport support
> - Admin Client to support dynamic deployment and undepolyment of services
> - Document Literal and RPC style support
> - Stub/Skeleton genearation both in C and C++
> - Many critical bug fixes
> - Updated documentation
>
>
> Release Criteria:
>
> - Functional tests pass
> - Test on installation procedures
> - Test on different versions of Apache web server(1.3.xx, 2.0.xx)
> - Test samples on different platforms (Linux, Microsoft Windows)
> - Fix pending bugs to-date
>
> Dates:
>
> The following dates are proposed:
> Code freeze March 30, 2004
> Release alpha version March 31, 2004
> Release beta version April 05, 2004
> Release 1.1 April 10, 2004
>
> damitha
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Axis C++ version 1.1 Release Plan
Posted by Davanum Srinivas <di...@yahoo.com>.
+1 from me.
--- damitha@opensource.lk wrote:
> Hi all,
> I volunteer to be the release manager for the Axis C++ 1.1 release.
> Following is the release plan.
>
> Axis C++ 1.1 Release Plan
>
> This is the release plan for Axis C++ version 1.1. This version will be a
> snapshot of all the changes since 1.0, including critical bug fixes and
> tests. The main goal is to provide a more stable release than version 1.0.
>
> Changes from 1.0 to 1.1:
> - XML parser abstraction layer
> Support for Expat (1.95.7) Xerces (2.2.5)
> - SSL transport support
> - Admin Client to support dynamic deployment and undepolyment of services
> - Document Literal and RPC style support
> - Stub/Skeleton genearation both in C and C++
> - Many critical bug fixes
> - Updated documentation
>
>
> Release Criteria:
>
> - Functional tests pass
> - Test on installation procedures
> - Test on different versions of Apache web server(1.3.xx, 2.0.xx)
> - Test samples on different platforms (Linux, Microsoft Windows)
> - Fix pending bugs to-date
>
> Dates:
>
> The following dates are proposed:
> Code freeze March 30, 2004
> Release alpha version March 31, 2004
> Release beta version April 05, 2004
> Release 1.1 April 10, 2004
>
> damitha
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Axis C++ version 1.1 Release Plan
Posted by Davanum Srinivas <di...@yahoo.com>.
+1 from me.
--- damitha@opensource.lk wrote:
> Hi all,
> I volunteer to be the release manager for the Axis C++ 1.1 release.
> Following is the release plan.
>
> Axis C++ 1.1 Release Plan
>
> This is the release plan for Axis C++ version 1.1. This version will be a
> snapshot of all the changes since 1.0, including critical bug fixes and
> tests. The main goal is to provide a more stable release than version 1.0.
>
> Changes from 1.0 to 1.1:
> - XML parser abstraction layer
> Support for Expat (1.95.7) Xerces (2.2.5)
> - SSL transport support
> - Admin Client to support dynamic deployment and undepolyment of services
> - Document Literal and RPC style support
> - Stub/Skeleton genearation both in C and C++
> - Many critical bug fixes
> - Updated documentation
>
>
> Release Criteria:
>
> - Functional tests pass
> - Test on installation procedures
> - Test on different versions of Apache web server(1.3.xx, 2.0.xx)
> - Test samples on different platforms (Linux, Microsoft Windows)
> - Fix pending bugs to-date
>
> Dates:
>
> The following dates are proposed:
> Code freeze March 30, 2004
> Release alpha version March 31, 2004
> Release beta version April 05, 2004
> Release 1.1 April 10, 2004
>
> damitha
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
Some comments on source distibution for R1.1
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi All,
I was trying out the source from the CVS over the weekend and came up with few suggestions to
make the source distibution more user friendly.
Most of the suggestions are focused for the Linux platform.
Please see the attached text file.
Thanks,
Samisa...
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
Re: Axis C++ version 1.1 Release Plan
Posted by Davanum Srinivas <di...@yahoo.com>.
+1 from me.
--- damitha@opensource.lk wrote:
> Hi all,
> I volunteer to be the release manager for the Axis C++ 1.1 release.
> Following is the release plan.
>
> Axis C++ 1.1 Release Plan
>
> This is the release plan for Axis C++ version 1.1. This version will be a
> snapshot of all the changes since 1.0, including critical bug fixes and
> tests. The main goal is to provide a more stable release than version 1.0.
>
> Changes from 1.0 to 1.1:
> - XML parser abstraction layer
> Support for Expat (1.95.7) Xerces (2.2.5)
> - SSL transport support
> - Admin Client to support dynamic deployment and undepolyment of services
> - Document Literal and RPC style support
> - Stub/Skeleton genearation both in C and C++
> - Many critical bug fixes
> - Updated documentation
>
>
> Release Criteria:
>
> - Functional tests pass
> - Test on installation procedures
> - Test on different versions of Apache web server(1.3.xx, 2.0.xx)
> - Test samples on different platforms (Linux, Microsoft Windows)
> - Fix pending bugs to-date
>
> Dates:
>
> The following dates are proposed:
> Code freeze March 30, 2004
> Release alpha version March 31, 2004
> Release beta version April 05, 2004
> Release 1.1 April 10, 2004
>
> damitha
=====
Davanum Srinivas - http://webservices.apache.org/~dims/