Hi,
My name is Johannes Klarenbeek. I'm working for the goverment in the netherlands (however this ends in december) on project basis, and start using the apachesoap project 2 years ago. In these years I used and tweaked this library to suit the projects needs. This was primarly to talk with an incompatible soap server (The AXL SOAP Server on the Cisco Callmanager, if that rings any bells), to comply with the HTTP 1.1 protocol which supports keep alive and gzip compression (for huge payload responses), and make it blazingly fast so quick updates could be done in short time intervals. Another requirement was that it ran on a JAVA 1 platform so I used the back then already absolete dist. without source code soap.jar which I decompiled to get a grip on the code. Some 2 months ago, when I checked out the website I found that the source for this distribution was available again. Thats cool, thank you for that! I also downloaded the last 2.3.1 dist, and found that the project now included some envelope editor classes aswell, which you need to talk to incompatible soap servers for example :) My question is this, can i contribute to the wssoap project? The knownledge I have of this project is huge. I think I could help this project with the subjects described above. However, maybe there are some rules (coding guidelines, release dates, etc) which I should be aware of, before I make this decision.
I would be glad to hear from you.
regards,
johannes klarenbeek
ps, why not the axis project? I followed the axis project as well, but my opinion about a soap package is that is should be flexible and small! Axis is not a small dist at all. wssoap also has its downsides, it depends on activation.jar and mail.jar which in my opinion is a lot of overhead for this little project to do just multipart/related message dispatching.
Hotmail en Messenger on the move click here
