On Thu, 19 Jul 2007 13:58:12 +0200,
wbsurfver@yahoo.com
<wbsurfver@gmail.comwrote:
Quote:
I have been trying to figure out apache/rampart soap security. We
have a soap server in java and the client is PHP. I just read this
article which concerns me because it seems to imply rampart/java won't
work with PHP.
Am I missing something here? The reason to work with SOAP connections is
so anything can communicate with anything, is it not? As long as client
and server follow protocol, communication should be OK.
Quote:
Are there any other good solutions, particularly simple
ones ? I have been trying to get rampart/java working for the past 3
days and haven't even gotten to the PHP client part as of yet, then it
occured to me to do a google search to see if the client being in PHP
might be an issue:
>
Kaushalye: Well...Rampart/ Java is our big brother. Just like Apache
Rampart/Java serves for Apache Axis2/Java, Apache Rampart/C serves for
Apache Axis2/C. We are trying our best to keep both implementations
similar, especially to keep the configurations similar. This is a bit
challenging due to the differences in the platforms. The C
implementation is not just for C developers. Our aim is to let PHP, C+
+, and Perl developers use Apache Rampart/C. So we have to make the
Apache Rampart/C implementation more flexible. We also need to provide
easy-to-use APIs for all these platforms.
Well, AFAIK it just states that a module for PHP has yet to be written,
including an API. That doesn't mean you cannot write it in PHP itself,
just means more work. I don't know anything about java/rampart, but as
long as it works with SOAP, you should be able to get it working using the
SOAP extention.
--
Rik Wasmus
