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 Susantha Kumara <su...@opensource.lk> on 2004/03/19 15:52:01 UTC
Work items for the Release
Hi Team,
As the current Axis C++ codebase has some major features added, its
suggested that we have a quick release in 1-2 weeks. When considered the
work that the team is working on I found we can finish following work for
the release.
The aim of this release is to provide users of Axis C++ a stable release
(rather than new features) with latest code which include following major
diffrences from Release 1.0.
- Document / literal support.
- Complete C web service and clients (compiler independant way).
- Use of Expat parser for performance.
- New Handler writing API
After this release I expect to come up with a plan to add the new features.
1).Source Restructuring
- Include files should be restructured in the CVS folder hiarachy to keep
include files that goes with binary distribution seperately. Then CVS
folder /c/include will contain only the include files that goes with binary
distribution and all other include files are moved to the respective /c/src
folder.
2) Writing critical failures to error logs.
3). Build environments.
- Distribution build files for windows/linux. Rather than building each
project and manually copying the files to prepare the distribution we need
to have build files (Makefiles, Visual C++ build files, other) to automate
this process.
- Borland C projects and/or build files
- Visual studio 7.0 projects.
4).Client Engine
- Implementation of client Side handler processing
- Making a single client side static library
5).Serialization / Deserialization
- Current Axis code does not support parsers other than Expat. We need to
write wrappers for using xerces.
- Adding Base64binary/HexBinary encode/decode functions to
BasicTypeSerializer (This is find out a good existing encode/decode
functions and add them).
6).WSDD processing
- Axis source code at CVS uses only Expat parser to parse WSDD file.We have
to define Interfaces and wrappers for supporting other parsers (xerces)
- Implementation of serialize methods to every WSDD class for writing WSDD
file from the memory representation (this feature is required for dynamic
deployment/undeployment).
7). Handlers
All handlers have to be modified/tested with new API.
8).New featurs to Add
AdminClient
9). WSDL2WS code generation
Generation of deploy.wsdd and undeploy.wsdd
10).Documentation
Update Existing Documentation to reflect all recent changes.
Please let me know your ideas/feedback so that I can come up with a Release
plan.
Thanks,
Susantha.
Re: Work items for the Release
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Hi Susantha,
Pls send this to the -user list too - someone there was asking about
upcoming releases.
Sanjiva.
----- Original Message -----
From: "Susantha Kumara" <su...@opensource.lk>
To: "axis-c-dev" <ax...@ws.apache.org>
Sent: Friday, March 19, 2004 8:52 PM
Subject: Work items for the Release
> Hi Team,
>
> As the current Axis C++ codebase has some major features added, its
> suggested that we have a quick release in 1-2 weeks. When considered the
> work that the team is working on I found we can finish following work for
> the release.
> The aim of this release is to provide users of Axis C++ a stable release
> (rather than new features) with latest code which include following major
> diffrences from Release 1.0.
>
> - Document / literal support.
> - Complete C web service and clients (compiler independant way).
> - Use of Expat parser for performance.
> - New Handler writing API
>
> After this release I expect to come up with a plan to add the new
features.
>
> 1).Source Restructuring
> - Include files should be restructured in the CVS folder hiarachy to keep
> include files that goes with binary distribution seperately. Then CVS
> folder /c/include will contain only the include files that goes with
binary
> distribution and all other include files are moved to the respective
/c/src
> folder.
>
> 2) Writing critical failures to error logs.
>
> 3). Build environments.
> - Distribution build files for windows/linux. Rather than building each
> project and manually copying the files to prepare the distribution we
need
> to have build files (Makefiles, Visual C++ build files, other) to automate
> this process.
> - Borland C projects and/or build files
> - Visual studio 7.0 projects.
>
> 4).Client Engine
> - Implementation of client Side handler processing
> - Making a single client side static library
>
> 5).Serialization / Deserialization
> - Current Axis code does not support parsers other than Expat. We need to
> write wrappers for using xerces.
> - Adding Base64binary/HexBinary encode/decode functions to
> BasicTypeSerializer (This is find out a good existing encode/decode
> functions and add them).
>
> 6).WSDD processing
> - Axis source code at CVS uses only Expat parser to parse WSDD file.We
have
> to define Interfaces and wrappers for supporting other parsers (xerces)
> - Implementation of serialize methods to every WSDD class for writing WSDD
> file from the memory representation (this feature is required for dynamic
> deployment/undeployment).
>
> 7). Handlers
> All handlers have to be modified/tested with new API.
>
> 8).New featurs to Add
> AdminClient
>
> 9). WSDL2WS code generation
> Generation of deploy.wsdd and undeploy.wsdd
>
> 10).Documentation
> Update Existing Documentation to reflect all recent changes.
>
>
> Please let me know your ideas/feedback so that I can come up with a
Release
> plan.
>
> Thanks,
>
> Susantha.
>
>
Re: Work items for the Release
Posted by da...@opensource.lk.
Hi Team,
I'd like to add the following item.
We have a ssl patch applied, sent by Mark Lrod for the axisc++ client.
We need to add this feature to the release.
To do this
We need to install apache with ssl enabled and make it listen to https
requests.
We need to make some changes in the code so that client can send https.
damitha
> Hi Team,
>
> As the current Axis C++ codebase has some major features added, its
> suggested that we have a quick release in 1-2 weeks. When considered the
> work that the team is working on I found we can finish following work for
> the release.
> The aim of this release is to provide users of Axis C++ a stable release
> (rather than new features) with latest code which include following major
> diffrences from Release 1.0.
>
> - Document / literal support.
> - Complete C web service and clients (compiler independant way).
> - Use of Expat parser for performance.
> - New Handler writing API
>
> After this release I expect to come up with a plan to add the new
> features.
>
> 1).Source Restructuring
> - Include files should be restructured in the CVS folder hiarachy to keep
> include files that goes with binary distribution seperately. Then CVS
> folder /c/include will contain only the include files that goes with
> binary
> distribution and all other include files are moved to the respective
> /c/src
> folder.
>
> 2) Writing critical failures to error logs.
>
> 3). Build environments.
> - Distribution build files for windows/linux. Rather than building each
> project and manually copying the files to prepare the distribution we
> need
> to have build files (Makefiles, Visual C++ build files, other) to automate
> this process.
> - Borland C projects and/or build files
> - Visual studio 7.0 projects.
>
> 4).Client Engine
> - Implementation of client Side handler processing
> - Making a single client side static library
>
> 5).Serialization / Deserialization
> - Current Axis code does not support parsers other than Expat. We need to
> write wrappers for using xerces.
> - Adding Base64binary/HexBinary encode/decode functions to
> BasicTypeSerializer (This is find out a good existing encode/decode
> functions and add them).
>
> 6).WSDD processing
> - Axis source code at CVS uses only Expat parser to parse WSDD file.We
> have
> to define Interfaces and wrappers for supporting other parsers (xerces)
> - Implementation of serialize methods to every WSDD class for writing WSDD
> file from the memory representation (this feature is required for dynamic
> deployment/undeployment).
>
> 7). Handlers
> All handlers have to be modified/tested with new API.
>
> 8).New featurs to Add
> AdminClient
>
> 9). WSDL2WS code generation
> Generation of deploy.wsdd and undeploy.wsdd
>
> 10).Documentation
> Update Existing Documentation to reflect all recent changes.
>
>
> Please let me know your ideas/feedback so that I can come up with a
> Release
> plan.
>
> Thanks,
>
> Susantha.
>
>
>
Re: Work items for the Release
Posted by da...@opensource.lk.
Hi Team,
I'd like to add the following item.
We have a ssl patch applied, sent by Mark Lrod for the axisc++ client.
We need to add this feature to the release.
To do this
We need to install apache with ssl enabled and make it listen to https
requests.
We need to make some changes in the code so that client can send https.
damitha
> Hi Team,
>
> As the current Axis C++ codebase has some major features added, its
> suggested that we have a quick release in 1-2 weeks. When considered the
> work that the team is working on I found we can finish following work for
> the release.
> The aim of this release is to provide users of Axis C++ a stable release
> (rather than new features) with latest code which include following major
> diffrences from Release 1.0.
>
> - Document / literal support.
> - Complete C web service and clients (compiler independant way).
> - Use of Expat parser for performance.
> - New Handler writing API
>
> After this release I expect to come up with a plan to add the new
> features.
>
> 1).Source Restructuring
> - Include files should be restructured in the CVS folder hiarachy to keep
> include files that goes with binary distribution seperately. Then CVS
> folder /c/include will contain only the include files that goes with
> binary
> distribution and all other include files are moved to the respective
> /c/src
> folder.
>
> 2) Writing critical failures to error logs.
>
> 3). Build environments.
> - Distribution build files for windows/linux. Rather than building each
> project and manually copying the files to prepare the distribution we
> need
> to have build files (Makefiles, Visual C++ build files, other) to automate
> this process.
> - Borland C projects and/or build files
> - Visual studio 7.0 projects.
>
> 4).Client Engine
> - Implementation of client Side handler processing
> - Making a single client side static library
>
> 5).Serialization / Deserialization
> - Current Axis code does not support parsers other than Expat. We need to
> write wrappers for using xerces.
> - Adding Base64binary/HexBinary encode/decode functions to
> BasicTypeSerializer (This is find out a good existing encode/decode
> functions and add them).
>
> 6).WSDD processing
> - Axis source code at CVS uses only Expat parser to parse WSDD file.We
> have
> to define Interfaces and wrappers for supporting other parsers (xerces)
> - Implementation of serialize methods to every WSDD class for writing WSDD
> file from the memory representation (this feature is required for dynamic
> deployment/undeployment).
>
> 7). Handlers
> All handlers have to be modified/tested with new API.
>
> 8).New featurs to Add
> AdminClient
>
> 9). WSDL2WS code generation
> Generation of deploy.wsdd and undeploy.wsdd
>
> 10).Documentation
> Update Existing Documentation to reflect all recent changes.
>
>
> Please let me know your ideas/feedback so that I can come up with a
> Release
> plan.
>
> Thanks,
>
> Susantha.
>
>
>
Re: Work items for the Release
Posted by ka...@opensource.lk.
Hi Susantha;
Axis C++ has following bug list which are Unscheduled and unassinged.
http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10461
& in detail here
http://nagoya.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10461&statusIds=1
Do the Team members suppose to work on bug fixing in this Release or do we
suppose to fix some critical buges out of these?What is the schedule in
fixing bugs?
Thanks
Kanchana
>Hi Team,
>
> As the current Axis C++ codebase has some major features added, its
> suggested that we have a quick release in 1-2 weeks. When considered the
> work that the team is working on I found we can finish following work for
> the release.
> The aim of this release is to provide users of Axis C++ a stable release
> (rather than new features) with latest code which include following major
> diffrences from Release 1.0.
>
> - Document / literal support.
> - Complete C web service and clients (compiler independant way).
> - Use of Expat parser for performance.
> - New Handler writing API
>
> After this release I expect to come up with a plan to add the new
> features.
>
> 1).Source Restructuring
> - Include files should be restructured in the CVS folder hiarachy to keep
> include files that goes with binary distribution seperately. Then CVS
> folder /c/include will contain only the include files that goes with
> binary
> distribution and all other include files are moved to the respective
> /c/src
> folder.
>
> 2) Writing critical failures to error logs.
>
> 3). Build environments.
> - Distribution build files for windows/linux. Rather than building each
> project and manually copying the files to prepare the distribution we
> need
> to have build files (Makefiles, Visual C++ build files, other) to automate
> this process.
> - Borland C projects and/or build files
> - Visual studio 7.0 projects.
>
> 4).Client Engine
> - Implementation of client Side handler processing
> - Making a single client side static library
>
> 5).Serialization / Deserialization
> - Current Axis code does not support parsers other than Expat. We need to
> write wrappers for using xerces.
> - Adding Base64binary/HexBinary encode/decode functions to
> BasicTypeSerializer (This is find out a good existing encode/decode
> functions and add them).
>
> 6).WSDD processing
> - Axis source code at CVS uses only Expat parser to parse WSDD file.We
> have
> to define Interfaces and wrappers for supporting other parsers (xerces)
> - Implementation of serialize methods to every WSDD class for writing WSDD
> file from the memory representation (this feature is required for dynamic
> deployment/undeployment).
>
> 7). Handlers
> All handlers have to be modified/tested with new API.
>
> 8).New featurs to Add
> AdminClient
>
> 9). WSDL2WS code generation
> Generation of deploy.wsdd and undeploy.wsdd
>
> 10).Documentation
> Update Existing Documentation to reflect all recent changes.
>
>
> Please let me know your ideas/feedback so that I can come up with a
> Release
> plan.
>
> Thanks,
>
> Susantha.
>
>
>