Feature list for future WSO2 WSAS releases
Please list down the features which you'd like to see in the future releases:
| Version |
Date |
Features
|
| 2.0 |
June 2007
|
- Clustering
- NodeManagement
- NodeManager service - DONE
- Reload Configuration - DONE
- Load Service Group
- Unload Service Group - DONE
- Apply Policy
- Admin Client scripts which call NodeManager - DONE
- Full WSDL 2.0 support - ?
- Support URL service & module repo - DONE
- Migrate from Jetty to Tomcat servlet container (for stand-alone edition) - DONE
- Handle SOAP & REST using the same endpoint - DONE
- Automatically discover context root without having to specify it in the axis2.xml, JS files etc. - Deepal
- Have a switch in the WSAS server.xml to turn the AdminServices & Management Console ON/OFF - DONE
- Improved AJAX client - Sanka
- Moving Maven2 build - DONE
- EJB Support - In Progress (Sumedha)
- Hyperic Agent for WSAS - http://www.hyperic.com/ - On hold
- Configure the client to use rampart/sandesha in the admin console
- IDE Integration - Part of WSF SDK - In Progress (Sandakith & Amila)
- IDE client generation + configuration of rampart/sandesha using the available wizard
- Dump Service Archive - Change some service configurations, such as policies, engaged modules etc, test the service, and dump it into a self contained AAR which contains all the new configuration - DONE
- Dump WAR Containing the Service Archive - On hold
- Configuration versioning - This will be used in the clustered scenario, a node having a different config version will not be able to join the cluster - Deepal
- Service versioning - Deepal
- Ubuntu/Debian apt repo integration - Chintana/Deep
- Data Services - In Progress (Chamil)
- XKMS service - Saminda/Azeez
- POX security - Azeez/Saminda
- Tracer
- Trace into Log files## Filter trace messages based on several criteria## Pretty print the trace messages on the front end - Saminda - Low priority
- Trace to logfile - DONE
- Filter messages based on simple string matching - DONE
|
| |
|
|
| |
|
|
Features need to be discussed :
- Moving the "www" related entities out of WSAS to commons project.
- Should admin-ui related entities move to a commons project ?
