Well I went ahead and started a SOAP API for perforce. I've modified Michael Bishop's p4Java api
code to be multiple user/client and it call compiles.
I can't run it as I can't compile the DLL - I don't have the right C++ compiler :-(.
Ideally it would be a GCC compatible set of source and we'd use CygWin for portability.
You'll need Glue standard : http://www.themindelectric.com/products/download/download.html ( Take
the jars and place them in lib/ -> GLUE-STD.jar, ejb.jar, servlet.jar, jcert.jar, jnet.jar,
If you've installed Java and set JAVA_HOME and PATH appropriately you can invoke "build" to run
ant (contained in tools/) and do a compile (the default action).
Go here ( http://java.sun.com/j2se/1.3/install.html ) and follow the instructions for JAVA_HOME
Something like java -cp Perforce_P4Soap.jar com.perforce.client.Main OR "build run"
This will launch a webserver that you can test with a browser (
http://localhost:8004/perforce:p4soap ) to see the WSDL file.
To test from the client side :
Choose you language (Perl, Python, C, VB) get the soap API for it and generate it's stubs.
Or just read about the client side Java assitance glue can provide :
1) Inclusion of compiled native dlls etc - they are missing as I can;t compile them
2) Support for all features of Perforce (branching , changelists).
3) Separation of interface and implementation (internally in Michael's code).
4) Test, bugfix
Why do this ?
Perforce needs a first class API available to programmers in a variety of languages. P4FTP
P4WebDav are all very good as ideas, but they don't negate the need for a real API. It's so easy
with SOAP and Glue.
Yeah, so you think JAM is better that Ant. Trouble is Ant is defacto standard for building in the
Please email me Paul_Hammant@yahoo.com
First cut of P4 Soap API. Uses Glue, can't work yet as DLLs missing.