1. Fixed handling of -b parameter to set root binding definition file name.
2. Added support for using interfaces as equivalent to superclasses.
3. Implemented namespace and namespace-style customizations.
4. Fixed handling of arrays of primitives.
5. Changed code to read the generated binding definition files for validation,
so that meaningful line numbers are present when a problem occurs in the binding
generation.
6. Fixed problems with same class name being used in different packages.
7. Added customization file attribute validation checks.
8. Implement flag for class initialized to avoid duplicate processing.
9. Preserve order of child elements/attributes (based on supplied list, or on
order seen in source code, or order seen in binary)
10. Added support for initial style character flags on member names in <class>
include/optional/required lists ('@' for an attribute, '/' for an element), so
that the style can be set without using a separate customization element for the
member.
11. Automatically include all classes named by <class> specifications in the
generated binding (even if not otherwise referenced).
12. Handle references to classes with mapped superclasses or interfaces.
13. Changed default name style to camelcase, force lowercase for hyphenated,
dotted, or underscore-separated names.
14. Added wrap-collections attribute to nesting elements, with default value
'false'.
15. Changed namespace handling for services to append the service name to the
inherited namespace URI for the request/response elements.
16. Corrected a problem where the namespace definition for the request/response
elements namespace was not present in the binding, leading to a problem in the
Axis2 linkage code.
17. Changed examples to be compatible with Axis2 1.3 (global rename of
AddDuplicateFaultException to AddDuplicateFault).

In progress:

Right now exceptions shared between services are not handled properly. What is
the correct way of handling these? I suppose the best is to detect if the
exceptions are shared, and if so move the corresponding Fault details element
into a separate namespace. That means a pass through the service list before
assigning the Fault namespaces, but is probably the cleanest way to make this
work.
