[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Condor C++ Web Services
- Date: Wed, 30 May 2007 00:15:59 +0200
- From: José Miguel Coro Riopedre <coro.riopedre.jm@xxxxxxxxx>
- Subject: Re: [Condor-users] Condor C++ Web Services
I am also using Condor Webservice API with a client written in C++, but
I use gSOAP as wsdl parser. I think your problem is that you are trying
to mix all the generated C++ into the same application. When you combine
the generated C++ code from collector.wsdl and schedd.wsdl, all the
routines used for web service access are duplicated.
I don't know if you can do this with your wsdl parser, but I resolved
this problem in gSOAP introducing collector and schedd generated code
into separated namespaces and all the common routines into a third file.
I hope you find this useful.
Am running into what is likely a problem with naivety rather than
Condor but here is my question:
Am trying to learn how to operate Condor as a web service from C++.
Used Systinet Server for C++ to convert wsdl to C++. (See
http://www.systinet.com/products/ssc/overview, free for development
and test.) We chose this tool because it is so well documented and
generates generic code that is not specific to a particular vendor.
We have used this tool successfully on a simpler interface.
Looking at the tutorial given at Condor World 2006,
annenba_APIs.ppt, Slide 23, I get the impression that wsdl files
should first be translated to C++. The resulting files should then be
compiled. Have completed these two steps successfully.
The problem comes during the link step. What happens is numerous
duplicate class definitions when a project is built that contains all
cpp files. Is that the expectation, that all cpp files should be
included in the same build? If not, how does one tell what files the
project should contain?
Many thanks for your guidance and patience.
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: