QuoteBut I had to download different .jar than konakart jars in /lib, such as an older version of wss4j (1.5.1, instead of 1.6).
For others reading this I just want to point out that there should be no need to change the wsdl4j-1.5.1.jar (if this is the jar you mean) and no need for any additional jars in order to compile or run. The default installation will use the provided jars to create client stubs successfully from the WSDL. If you use the provided build.xml and follow the User Guide it should work fine.
Hence I don't know what you're referring to Cyril or what is different about your environment.
Perhaps you are referring to a different jar? You mention wss4j but we don't include that with KonaKart anyway.
Note again that the recommended approach is to use the KKWSEng engine rather than creating AXIS client stubs from the WSDL and writing your own AXIS client-side code because in a java environment it's significantly easier just to instantiate KKWSEng which implements KKEngIf (just like the KKEng POJO engine does) and takes care of all the SOAP plumbing for you automatically.
Indeed, the idea is that you write your client side code against the KKEngIf (the "storefront" engine interface) and then later you can decide which implementation to use with your client-side code (selecting from POJO, RMI, SOAP or JSON by name at runtime). If you write your own AXIS code you cannot benefit from this flexibility.