The concepts behind the architecture of axis-cpp suggested modifications to axis-java with the objective of archieving performance improvement in order of magnitudes.
Changes are in two major areas;The deserialization of the soap message is done using xml pull. Deserialization of the soap body is performed by the application and not by the axis engine.
Just as in axis cpp there is a wrapper class for each web service class. This wrapper class is written with full awareness of the actual web service class. Axis engine would call the invoke( ) method of the wrapper class which in turn would call the correct method in the web service.
Web service application developers should be encouraged to use the top down approach rather than bottom up approach, i.e. they should be encouraged to begin by describing web service in wsdl, rather than taking any java/cpp class and publish it as a web service. The wrapper class, web service classes are auto generated using the WSDL2Ws tool
Since there are significant changes in xml parsing "deserialization part" of the axis had to be replaced. Minor modifications had to be done to axis architecture with the introduction of wrappers.