John,
>This is a good one about web services, FoxPro, and Apache/Java.
>
>I can connect to the web service to a method with no parameters.
>But, there is a method that I want to connect to but it won't accept the parameters. The problems is that its an Apache/Java server that is looking for signed variable, but I don't know how to create a signed variable parameter in FoxPro.

I've done a couple of those. Get a list of all the WS the project will probaby call or - even better - a HTTP (XML) trace of the messages actually sent across the wire. Most java tools thrive on complex web service parameters, which is the first strike for vfp soap toolkit. Decide if it is worth to manually parse and built your messages (I have done that as well where it made sense NOT to increase the install). It is even if you do it yourself - easy to do with some worker classes wich will take less than a week to create or build on the stuff Rick has already running. Client was happy not to mess with installation in gov'nt systems (most running still W2K) and the services (also gov'nt - really stable <g>) haven't changed.

Or decide to put a java or .net WS client as adapter between vfp and the WS. Makes sense if there is a lot of them or change rate is high. Today most of the time a .net adapter is my default proposition, and if there are reasons NOT to go that way, the second recommendation is to built yourself a small toolkit working on a library similar to Rick's. I did not use the webconnection stuff as back then local certificates were not supported, but looking over his patterns gave me those highlights I had to implement.

make sure over a couple of beers your friend has to pay he realizes the maintainance risk of doing it yourself.

my 0.02 EUR

thomas