2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP
If you were registered and logged in, you could join this project.
The cmdproc library provides a framework for automated
command processing in Java.
A command processor manages a set of commands and their individual
parameters like environment, arguments and return values. It ensures
that each command is executed with a proper environment and argument
list and validates its return values.
The cmdproc API indends to take care of all the unpleasant things
developers usually have to worry about:
- Easy and precise specification of mandatory and optional
environment, argument and result parameters with unrestricted
- Automated validation of the specified parameters in structure
and type belonging.
- Automated command and argument parsing.
The cmdproc API is currently developed for Java 2 version 1.4.2. A
modified API optimized for Java 5 may be designed when the basic API is
- 0.1 Running demo application
- 0.2 XML input format and matching builders
- 0.3 API for default parameter values. [skipped]
- 0.4 API for parameter conditions.
- 0.5 API cleanup and improvements. [skipped]
Cleanup is included in version 0.6. Further improvements are
expected after version 0.7.
- 0.6 Reflection support for parameter
- 0.7 Support for dependent conditions.
Conditions may relate to the values of other parameters
- 0.8 Command groups and default values.
- 0.9 XML input format improvements
- 1.0 Cleanup, API improvements and complete
2005-11-15 Switched to SVN repository.
2005-03-23 Version 0.8 is released. This is an
important release because the library finally includes all the feature I
intended to implement. It includes a simple demo application to give you
an impression how it can be used. Take a look!
2005-02-12 Version 0.7 released. The parameter
values of each level are added to a condition context. Through this
context a condition can refer to the values of all parameter from a
lower level. This works with OGNL expressions, too!
2005-02-08 Version 0.6 released. Conditions can be
defined through an OGNL expression (which evaluates to a boolean value).
See the OGNL website for details on
the OGNL language.
2005-02-01 An API for default parameters was
skipped, because is is actually not necessary at the moment and can be