I've just tried the Windows binary distribution: In the SDO INSTALL document step (1) Prereqs it says get libxml2 but doesn't say which version and doesn't say to set any environment variable to where i'd installed it
Step 4 says "Set the environment variable TUSCANY_SDOCPP to the 'deploy' directory" but there is no directory named deploy. In the samples INSTALL doc it doesn't say anything about zlib, libxml, or iconv but it doesn't work without these. I used the versions from the RC1 install doc, set environment variables for each and added them to the PATH Now "runclient add 5 6" says can't find MSVCP60D.dll. Googling that I found a free download and added that to the PATH. Now it can't find MSVCRTD.dll, found another free download for that and added to the PATH. And now runclient works! CalculatorImpl::add 5.000000 + 6.000000 = 11.000000 Calculator: add(5,6) = 11 Now trying the WS sample and it complains that the procedure entrypoint xmltextReaderConstEncoding can't be found in libxml2.dll. I was using version 2.6.20, tried version 2.6.19 and that seems to work and outputs: Started Simple Axis2 HTTP Server ... Now the client. The instructions in step 3 are a bit brief, I also had to add axis and libxml2 to the PATH. Now running runwsclient gives: using Axis2C: \SCA\Cpp\RC2\axis2c-bin-0.92-win32" Using endpoint : http://localhost:9090/axis2/services/Calculator Invoking operation add with params 40 and 8 Calculator stub invoke FAILED! Any hints on how to debug this? I've entered that endpoint URL in a browser and it lists out all the operations so it looks like the axis2 service may be ok. ...ant On 7/12/06, Pete Robbins <[EMAIL PROTECTED]> wrote:
I have posted a 2nd candidate for the first C++ release here: http://people.apache.org/~robbinspg/RC-2 Please vote to publish the Milestone 1 release distributions. Please take some time to download the distributions, review them and test them in your environment before voting. The vote is open for at least the next 72 hours. At least three +1 votes are required, and only the votes from Tuscany committers are binding. If the majority of all votes is positive, I will send a summary of that vote to the Incubator's general list to formally request the Incubator PMC to approve the Tuscany C++ Milestone 1 release. For your reference the Incubator release policy guidelines are available at http://incubator.apache.org/incubation/Incubation_Policy.html#Releases. Release Summary ============= Tuscany SCA C++ provides a runtime implementation for the Service Component Architecture 0.9 specification, written in C++ and will currently support C++ component implementation types. This is not yet a complete implementation and known restrictions are described below. Supported SCA Assembly Model features * All features are supported unless listed under the known restrictions below. See SCA Assembly Model specification. Supported language bindings * Component implementations written in C++. See SCA Client and Implementation Model specification. * Component interfaces described by C++ classes. See SCA Client and Implementation Model specification. Supported external service and entry point bindings * The web service binding is supported. This implementation will support web services which using document literal SOAP bindings conforming to the WS-I basic profile (rpc/encoded is not yet supported). Known restrictions * Subsystem: wiring, entry points and external services are not supported. * Local service interfaces cannot use overloaded operations (the SCA specification limits remote service interfaces to not using overloaded operations). * Each WSDL definition for a web service binding must be in a single WSDL document. * No load time validation of the deployed SCA application (run time validation only). * No metadata API. A sample is included which demonstrates deploying an SCA module, component wiring, locating and invoking C++ service from C++ component, invoking from a C++ client, and exposing a service as a web service using ws binding. Cheers, -- Pete
