Hi, My project requirement is to use a Java Soap Engine with Java & C++ client side for web services. The Java part is relatively easy: we'll use AXIS. However, since AXIS C++ is not mature yet, we are looking at WASP C++ client side.
It seems that for stateful service, AXIS and WASP have defined different header schema for session handling and each of them has its own header processor.. Here is the header for AXIS: <soapenv:Header> <ns1:sessionID soapenv:mustUnderstand="0" xsi:type="xsd:long" xmlns:ns1="http://xml.apache.org/axis/session";>-1380096502541275209</ns1:sessionID> </soapenv:Header> And this is the header for WASP: <e:Header> <ns1:instance xmlns:ns1="http://idoox.com/interface";> <setId>promethius:2003.11.14 07:51:58 GMT:1E43C0F479E2A7E6:2</setId> </ns1:instance> </e:Header> This really makes it difficult when I tried to use stateful services between a AXIS server and WASP C++ client. Should there be a common schema for session handling, since it's so largely used? Before there is a common schema, does anyone know how to handle this from AXIS side? Thanks! Gloria __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
