Re: C++ M1 Release Candidate
Hi Luciano, Thanks for taking a look. Comments inline: Cheers, On 07/07/06, Luciano Resende [EMAIL PROTECTED] wrote: Hi Pete I took sometime to look at the C++ M1 Release candidate and I have the following feedback... Please keep in mind that my C++ skills is not one of my biggest strengths as of today, so, some feedback might be due to lack of involvement with C++ for couple of years... Also note that I didn't have a C++ DEV environment, so I was just running things from the binaries you posted. - In Tuscany Java, we have some sample script files to boot the Tuscany environment ( http://incubator.apache.org/tuscany/projectjava.html#Enviroment%20scripts). Should we have something similar for C++ environment ? I have created a sample one just to using for C++ M1 and could be used as a sample if people think this is a good idea. I'm not particularly keen on scripts which have hard-coded paths in (to whoevers machine they were written on). I think a parameterised script could be useful though. - Instructions on how to install Tuscany SCA CPP posted here ( http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/INSTALL) says: - 5.a. Unzip the supplied zip file. set the TUSCANY_SCACPP variable to point to the 'deploy' directory in the unzipped directory tree. I can find the deploy directory in the c++ svn repository, but it's not available in the M1 release candidate. Is this just the directory the files were extracted ? If so, documentation needs clarification, otherwise M1 zip need to be checked. Trying to go a step ahead, I set this to the place i unzipped the files and looks like it accepted that :) That is a mistake in the INSTALL doc it should say: 5.a. Unzip the supplied zip file. set the TUSCANY_SCACPP variable to point to the unzipped directory tree. - In order to start getting better results from the SCA Calculator sample program, I had to figure out the following items that were not mentioned in the INSTALL instructions - Need to add axis2c\lib directory to path as well... instructions only mention bin directory This is a mistake too. it is axis2c\lib that should be added to the path. I'll fix he doc. - Need the following runtime env dlls : msvcp60d.dll, msvcrtd.dll(my system only had the regular ones without the d) This is an interesting one. The Windows distribution build is actually a debug build. It probably should be a release build. - After fixing the DLL issues, i found that the calculator sample app was expecting the following environment variable to be set : SystemConfigurationException TUSCANY_SCACPP_SYSTEM_ROOT environment variable not set I set that to the same value of TUSCANY_SCACPP Do we need these 2 env variables ? What is the difference between TUSCANY_SCACPP and TUSCANY_SCACPP_SYSTEM_ROOT - Now I'm at the point I'm getting the following exception SystemConfigurationException Duplicate wire for reference: CalculatorDivideService Any workaround here ? The variables are different. TUSCANY_SCACPP points to the installed root for the runtime to locate its model schemas etc. TUSCANY_SCACPP_SYSTEM_ROOT is used to point to the deployed SCA System... i.e. the folder that contains the modules and subsystems of the sca application. The samples INSTALL says: 1. The following environment variables are required: ... snip ... set TUSCANY_SCACPP_SYSTEM_ROOT=samples_install_dir/Calculator/deploy By setting this to the same as TUSCANY_SCACPP the runtime is finding all the sca.module files in the tree. There is a copy in the samples folder and one is deployed to the Calculator/deploy folder so everything is defined twice...hence the duplicate wire exception. Other minor things - Couple files like : LICENSE, NOTICE, README all have no extensions, are these the way they are supposed to be ? The Java M1 had some of these files with the txt extension... - The SDO package have two readme with different contents on it (README and README.txt) It seems standard practice in C/C++ projects using Automake that thes files do not have extensions. -- Luciano *Pete Robbins [EMAIL PROTECTED]* 07/05/2006 08:02 PM Please respond to tuscany-dev@ws.apache.org To tuscany-dev@ws.apache.org cc Subject C++ M1 Release Candidate I have posted a candidate for the first C++ release here. http://people.apache.org/~robbinspg/RC1 Would all interested parties take some time to review this so that we can either re-spin the release or vote on it asap. The website documentation is out of date and will be re-written to sync with what is in the release. Hopefully this will be done tomorrow. A Calculator 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
Re: C++ M1 Release Candidate
Hi Pete, I found one issue. I used VC6 to attempt to build SDO and I get some problems during the copyout. I'll raise a JIRA for this. Linking... Creating library ..\..\..\runtime\core\Release/tuscany_sdo.lib and object ..\..\..\runtime\core\Release/tuscany_sdo.exp copyout 1 file(s) copied. 1 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. Error executing c:\windows\system32\cmd.exe. tuscany_sdo.dll - 1 error(s), 0 warning(s) Regards, Geoff.
Re: C++ M1 Release Candidate
That looks like output from the visual studio build. Did you try the command line? Cheers, On 07/07/06, Geoffrey Winn [EMAIL PROTECTED] wrote: Hi Pete, I found one issue. I used VC6 to attempt to build SDO and I get some problems during the copyout. I'll raise a JIRA for this. Linking... Creating library ..\..\..\runtime\core\Release/tuscany_sdo.lib and object ..\..\..\runtime\core\Release/tuscany_sdo.exp copyout 1 file(s) copied. 1 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. The system cannot find the path specified. 0 file(s) copied. Error executing c:\windows\system32\cmd.exe. tuscany_sdo.dll - 1 error(s), 0 warning(s) Regards, Geoff. -- Pete
Re: C++ M1 Release Candidate
Not yet, but I will do. I managed to build successfully in VC6 by leaving sdo_test and Win32 Debug as the active configuration and doing rebuild all. After that I tried to run the tests by just pressing the F5 button and although the tests do run successfully I had to step through a mass of break points that, I assume, were checked in with the project file. I'll raise a JIRA for that too. Regards, Geoff. On 07/07/06, Pete Robbins [EMAIL PROTECTED] wrote: That looks like output from the visual studio build. Did you try the command line? Cheers, -- Pete
Re: C++ M1 Release Candidate
I built the SDO release from the command line using build.cmd as it says in the INSTALL file and that worked without apparent error. At this point I would like to run the same set of tests that I would normally run from the Visual Studio build ie the sdo_test project, but I can't see how to do that. Does the test program get built from the command line? Thanks, Geoff.
Re: C++ M1 Release Candidate
Good point, you should raise a JIRA that the build.cmd doesnt run it automatically. The test program is runtime/core/test/Debug/sdo_test.exe, and needs to be run from the runtime/core/test directory: cd runtime/core/test Debug\sdo_test There are currently only 108 tests running, although the doc says 111. You are supposed to get a few messages about files not found, followed by 108 tests passed. Cheers, Ed. On 07/07/06, Geoffrey Winn [EMAIL PROTECTED] wrote: I built the SDO release from the command line using build.cmd as it says in the INSTALL file and that worked without apparent error. At this point I would like to run the same set of tests that I would normally run from the Visual Studio build ie the sdo_test project, but I can't see how to do that. Does the test program get built from the command line? Thanks, Geoff.
Re: C++ M1 Release Candidate
From the source distro on linux you should be able to just run ./sdotest.sh from the top level folder. We should write a sdotest.cmd to do the same on win. On 07/07/06, Edward Slattery [EMAIL PROTECTED] wrote: Good point, you should raise a JIRA that the build.cmd doesnt run it automatically. ... and I don't think it should IMO. The test program is runtime/core/test/Debug/sdo_test.exe, and needs to be run from the runtime/core/test directory: cd runtime/core/test Debug\sdo_test There are currently only 108 tests running, although the doc says 111. You are supposed to get a few messages about files not found, followed by 108 tests passed. Cheers, Ed. On 07/07/06, Geoffrey Winn [EMAIL PROTECTED] wrote: I built the SDO release from the command line using build.cmd as it says in the INSTALL file and that worked without apparent error. At this point I would like to run the same set of tests that I would normally run from the Visual Studio build ie the sdo_test project, but I can't see how to do that. Does the test program get built from the command line? Thanks, Geoff. -- Pete
Re: C++ M1 Release Candidate
There is a problem with the Windows src zip for sca to do with filename lengths. I will fix it and re-post a new zip. On 06/07/06, Pete Robbins [EMAIL PROTECTED] wrote: I have posted a candidate for the first C++ release here. http://people.apache.org/~robbinspg/RC1 Would all interested parties take some time to review this so that we can either re-spin the release or vote on it asap. The website documentation is out of date and will be re-written to sync with what is in the release. Hopefully this will be done tomorrow. A Calculator 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. 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. -- Pete -- Pete
Re: C++ M1 Release Candidate
The problem appears to be that WinXP expanding of a compressed folder can not expand the tuscany_sca_cpp-0.1.incubating-M1-src.zip (despite the fact that it was used to create the zip in the first place!). This zip can be successfully extracted using WinZip or even jar -xf so I am not going to update the zip. Any ideas on why WinXP zip expand has a problem?? I'm fairly sure that it is to do with a long path name. Cheers, On 06/07/06, Pete Robbins [EMAIL PROTECTED] wrote: There is a problem with the Windows src zip for sca to do with filename lengths. I will fix it and re-post a new zip. On 06/07/06, Pete Robbins [EMAIL PROTECTED] wrote: I have posted a candidate for the first C++ release here. http://people.apache.org/~robbinspg/RC1 Would all interested parties take some time to review this so that we can either re-spin the release or vote on it asap. The website documentation is out of date and will be re-written to sync with what is in the release. Hopefully this will be done tomorrow. A Calculator 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. 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. -- Pete -- Pete -- Pete
Re: C++ M1 Release Candidate
Ive downloaded and built the src distro on Windows using the command line, devstudio6 and devstudio7. The builds all work fine, but the calculator sample on studio7 only half works as the project descriptions are missing some of the proxies/wrappers. Add works but Div doesnt. Im just going to fix that Ed. On 06/07/06, Pete Robbins [EMAIL PROTECTED] wrote: The problem appears to be that WinXP expanding of a compressed folder can not expand the tuscany_sca_cpp-0.1.incubating-M1-src.zip (despite the fact that it was used to create the zip in the first place!). This zip can be successfully extracted using WinZip or even jar -xf so I am not going to update the zip. Any ideas on why WinXP zip expand has a problem?? I'm fairly sure that it is to do with a long path name. Cheers, On 06/07/06, Pete Robbins [EMAIL PROTECTED] wrote: There is a problem with the Windows src zip for sca to do with filename lengths. I will fix it and re-post a new zip. On 06/07/06, Pete Robbins [EMAIL PROTECTED] wrote: I have posted a candidate for the first C++ release here. http://people.apache.org/~robbinspg/RC1 Would all interested parties take some time to review this so that we can either re-spin the release or vote on it asap. The website documentation is out of date and will be re-written to sync with what is in the release. Hopefully this will be done tomorrow. A Calculator 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. 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. -- Pete -- Pete -- Pete
Re: C++ M1 Release Candidate
OK... there are a couple of fixes for VC7 compilation plus some copyright/licence issues that will be resolved. I will respin the distro in the next few hours and put up the candidate for a vote. On 06/07/06, Edward Slattery [EMAIL PROTECTED] wrote: Ive downloaded and built the src distro on Windows using the command line, devstudio6 and devstudio7. The builds all work fine, but the calculator sample on studio7 only half works as the project descriptions are missing some of the proxies/wrappers. Add works but Div doesnt. Im just going to fix that Ed. On 06/07/06, Pete Robbins [EMAIL PROTECTED] wrote: The problem appears to be that WinXP expanding of a compressed folder can not expand the tuscany_sca_cpp-0.1.incubating-M1-src.zip (despite the fact that it was used to create the zip in the first place!). This zip can be successfully extracted using WinZip or even jar -xf so I am not going to update the zip. Any ideas on why WinXP zip expand has a problem?? I'm fairly sure that it is to do with a long path name. Cheers, On 06/07/06, Pete Robbins [EMAIL PROTECTED] wrote: There is a problem with the Windows src zip for sca to do with filename lengths. I will fix it and re-post a new zip. On 06/07/06, Pete Robbins [EMAIL PROTECTED] wrote: I have posted a candidate for the first C++ release here. http://people.apache.org/~robbinspg/RC1 Would all interested parties take some time to review this so that we can either re-spin the release or vote on it asap. The website documentation is out of date and will be re-written to sync with what is in the release. Hopefully this will be done tomorrow. A Calculator 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. 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. -- Pete -- Pete -- Pete -- Pete
Re: C++ M1 Release Candidate
Hi Pete I took sometime to look at the C++ M1 Release candidate and I have the following feedback... Please keep in mind that my C++ skills is not one of my biggest strengths as of today, so, some feedback might be due to lack of involvement with C++ for couple of years... Also note that I didn't have a C++ DEV environment, so I was just running things from the binaries you posted. - In Tuscany Java, we have some sample script files to boot the Tuscany environment (http://incubator.apache.org/tuscany/projectjava.html#Enviroment%20scripts). Should we have something similar for C++ environment ? I have created a sample one just to using for C++ M1 and could be used as a sample if people think this is a good idea. - Instructions on how to install Tuscany SCA CPP posted here (http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/INSTALL) says: - 5.a. Unzip the supplied zip file. set the TUSCANY_SCACPP variable to point to the 'deploy' directory in the unzipped directory tree. I can find the deploy directory in the c++ svn repository, but it's not available in the M1 release candidate. Is this just the directory the files were extracted ? If so, documentation needs clarification, otherwise M1 zip need to be checked. Trying to go a step ahead, I set this to the place i unzipped the files and looks like it accepted that :) - In order to start getting better results from the SCA Calculator sample program, I had to figure out the following items that were not mentioned in the INSTALL instructions - Need to add axis2c\lib directory to path as well... instructions only mention bin directory - Need the following runtime env dlls : msvcp60d.dll, msvcrtd.dll (my system only had the regular ones without the d) - After fixing the DLL issues, i found that the calculator sample app was expecting the following environment variable to be set : SystemConfigurationException TUSCANY_SCACPP_SYSTEM_ROOT environment variable not set I set that to the same value of TUSCANY_SCACPP Do we need these 2 env variables ? What is the difference between TUSCANY_SCACPP and TUSCANY_SCACPP_SYSTEM_ROOT - Now I'm at the point I'm getting the following exception SystemConfigurationException Duplicate wire for reference: CalculatorDivideService Any workaround here ? Other minor things - Couple files like : LICENSE, NOTICE, README all have no extensions, are these the way they are supposed to be ? The Java M1 had some of these files with the txt extension... - The SDO package have two readme with different contents on it (README and README.txt) -- Luciano Pete Robbins [EMAIL PROTECTED] 07/05/2006 08:02 PM Please respond to tuscany-dev@ws.apache.org To tuscany-dev@ws.apache.org cc Subject C++ M1 Release Candidate I have posted a candidate for the first C++ release here. http://people.apache.org/~robbinspg/RC1 Would all interested parties take some time to review this so that we can either re-spin the release or vote on it asap. The website documentation is out of date and will be re-written to sync with what is in the release. Hopefully this will be done tomorrow. A Calculator 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. 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. -- Pete - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
C++ M1 Release Candidate
I have posted a candidate for the first C++ release here. http://people.apache.org/~robbinspg/RC1 Would all interested parties take some time to review this so that we can either re-spin the release or vote on it asap. The website documentation is out of date and will be re-written to sync with what is in the release. Hopefully this will be done tomorrow. A Calculator 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. 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. -- Pete
