Looks good to me, +1 ...ant
On 10/19/06, Andrew Borley <[EMAIL PROTECTED]> wrote:
Tested on Fedora Core5 and WinXP +1 from me Andy On 10/19/06, Pete Robbins <[EMAIL PROTECTED]> wrote: > On 19/10/06, Andrew Borley <[EMAIL PROTECTED]> wrote: > > > > Hi everyone, > > > > I have posted an updated 3rd candidate for the milestone 2 C++ release > > here: > > http://people.apache.org/~ajborley/cpp-1.0-incubator-M2-RC3a/ > > > > This release candidate adds a missing build file in the Windows > > distros, fixes up the disabled Python and Ruby extension libraries on > > Linux so there are no "stat" messages and adds a few minor doc > > changes. > > > > Please vote to publish the Milestone 2 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 2 release. For your reference the Incubator release policy > > guidelines are available at > > http://incubator.apache.org/incubation/Incubation_Policy.html#Releases. > > > > > > About Tuscany SCA C++ > > ===================== > > > > Tuscany SCA C++ provides a runtime implementation for the for the Service > > Component Architecture 0.96 Assembly specification and the 0.95 C++ Client > > & Implementation Model specification, written in C++ and will currently > > support C++, Python and Ruby component implementation types. > > > > The specifications can be found at > > > > http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications > > > > It is possible to interoperate with Tuscany SCA Java via the Web > > Service bindings > > for services and references but restrictions apply. 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 the SCA C++ Client and > > Implementation Model specification. > > * Component implementations written in Python. See the > > doc/PythonExtension.html > > documentation. > > * Component implementations written in Python. See the > > doc/RubyExtension.html > > documentation. > > * Component interfaces described by C++ classes. See SCA Client and > > Implementation Model specification. > > > > Supported service and reference 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 > > * 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. > > > > > > > > About Tuscany SDO for C++ > > ========================= > > > > Tuscany SDO is an implementation of the Service Data Objects for C++ 2.01 > > specification found at > > http://www.osoa.org/display/Main/SDO+-+Previously+Published+Specifications > > > > Supported SDO features > > * All features are supported unless listed under the known restrictions. > > See the Service Data Objects for C++ 2.01 specification. > > > > New features in this release > > * Optional build on Windows with Apache STDCXX > > * Improved memory management > > * Multiple bug fixes and internal enhancements > > > > Many thanks > > > > Andrew > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > My issues with the previous candidate are resolved. > > Here's my +1 > Cheers, > -- > Pete > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
