there is now a new effort, called axis2, to redesign and totally reimplement both axis/java and axis/c++ on a new architecture. evolving from the now standard "handler chain" model that axis1 pioneered, axis2 is developing a more flexible pipeline architecture that can be managed and packaged in a more organized manner. this new design acknowledges the maturing of the web services space ? in terms of new protocols such as ws-reliablemessaging, ws-security, and ws-addressing that are built on top of the base soap system. at the time axis1 was designed, while it was fully expected that other protocols such as ws-reliablemessaging would be built on top of it, there was no proper extension architecture defined to enable clean composition of such layers. thus, one of the key motivations for axis2 is to provide a clean and simple environment like apache sandesha and apache wss4j to layer on top of.
another driving force for axis2 is the move away from rpc-oriented web services towards more ... 下一页