Hi, first of all, i want to thank developpers of this project, which is great and will become a reference.
I'm too a developper, trying to replace a CORBA communication layer in a big application by WS (for interop purposes, particularly at compilation time, AIX is not well supported with may CORBA distributions). We decided to choose Axis as a webservices framework and provider, and started to work on a Solaris 8 system with Axis C++ 1.5 release. We dealed with a lot of problems ! We found syntax pb : - in HandlerChain.hpp, bug described in mailing list, resolved - in StubC.hpp : some static_cast are leading to compil. errors (we replaced them by dynamic ones) We found link pb (maybe it's only for us) : we had to add -lCrun and -lCstd to linker args to fit our needs. We managed to compile mod_axis for apache support, deployed it, and it seems ok. The problem here is that we have no way to verify it's deployed until we test it with a client. The second problem comes here : we generated stubs and skeletons for client and server parts, we compiled, seems ok. But we receive SIGABRT at runtime for the client. with a little debugging and tracing, we found that the exception is thrown at ClientAxisEngine::invoke(MessageData* pMsg). Maybe there are answers for all those problems. It also would be great to have feedback from other axis c++ users that tryied on a Solaris server. Thanks to all -- Antoine Galataud [EMAIL PROTECTED] Département Architecture des Systèmes d'Information INSA - Rouen
