Call for Community Testing: 3.9.5 Java WS Core
- What is a "Call for Community Testing"?
- Participating in the Java WS Core testing call
- About Java WS Core
- Reasons for testing Java WS Core
- Technology dependencies
- Environment/build parameters and other special conditions to test
- Release notes
What is a "Call for Community Testing"?
A Call for Community Testing is a mechanism to notify our users that new Globus code is available for testing in the field. Through these calls, the Globus Alliance hopes to expose its code to a wide variety of usage scenarios early in its development process. The ultimate goals are to catch bugs that have historically been found only after final releases, and to elicit feedback from the community on ways our software can be improved.
Participating in the Java WS Core Testing Call is easy!
- Optional: Consider sending mail to testing@globus.org to let us know that you're helping out and describing what you intend to test.
- Install the software in a non-production environment. Use the 3.9.5 distribution
from http://www-unix.globus.org/toolkit/downloads/development/;
the code can also be retrieved directly from CVS using the tag
globus_3_9_5. - Exercise the software.
- Log your experiences in http://bugzilla.globus.org/globus/ under the "WS Core" product ("globus_wsrf_core" component). Please mention 3.9.5 explicitly in the body of the report.
- Optional: Consider sending descriptions of your tests to testing@globus.org so that we might use them to build standard tests in the future.
- If you have any questions or comments about the process, send an email to testing@globus.org.
- If you have any questions or comments regarding this component, join the gt4-friends list to participate in discussions with other testers. (To subscribe, send an email to majordomo@globus.org containing the words "subscribe gt4-friends" in the message body.)
Testing period
The testing period for this call is February 24 - April 29 2005.
About Java WS Core
The Java WS Core is an implementation of the Web Services Resource Framework (WSRF) and the Web Service Notification (WSN) family of standards. It provides API and tools for building stateful Web services.
Reasons for testing Java WS Core
- We need volunteers to exercise Java WS Core to discover performance and scalability problems. Since Java WS Core is a critical piece to any service built on top of it, its performance and scalability directly affects the service. Therefore, improving the Java WS Core performance most likely will improve the service performance.
- We need volunteers for Java WS Core to discover functionality and usability problems. Improving usability and functionality will make the software easier to use and develop.
Technology dependencies
Java WS Core depends on the following GT components:
Java WS Core depends on the following 3rd party software:
- Apache Xerces
- Apache XML Security
- Apache Axis
- Apache Xalan
- Apache Addressing
- Apache Commons BeanUtils
- Apache Commons CLI
- Apache Commons Collections
- Apache Commons Digester
- Concurrent Library
- Apache Tomcat JNDI
Please see the Technology Dependencies Details page for details.
Environment/build parameters and other special conditions to test
- Testing on a platform that is not listed in tested platforms.
- Stability tests: making thousands of requests to the container for a long period of time without restarting the container
- Concurrency tests: making hundreds of concurrent requests to the container