You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Pete Robbins <ro...@googlemail.com> on 2006/07/12 18:25:01 UTC
[VOTE] Release Tuscany C++ Milestone 1
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
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Pete Robbins <ro...@googlemail.com>.
On 13/07/06, ant elder <an...@gmail.com> wrote:
>
> 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.
This is a mistake. The Calculator sample was built using Debug. It should be
Release version. Fix applied to svn.
--
Pete
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Andrew Borley <aj...@gmail.com>.
Worked fine for me with the latest libxml2 (version 2.6.24) from
http://www.zlatkovic.com/libxml.en.html
Cheers
Andy
On 7/13/06, Pete Robbins <ro...@googlemail.com> wrote:
>
> I think our bin release may be buillt against 2.6.19. In which case I need
> to re-build it. (teach me for having lots of different versions around)
>
> On 13/07/06, Andrew Borley <aj...@gmail.com> wrote:
> >
> > Hi Ant,
> >
> > Did you get the Axis2C samples working first? Your error is due either
> to
> > the wong version of libxml2 (2.6.20 is what axis specifies) or not being
> > able to find the libxml2 dll on the PATH. The Axis doc says:
> > Copy libxml2.dll, iconv.dll and zlib1.dll to C:\axis2c\lib
> > and
> > Set the varibale AXIS2C_HOME to the deploy folder (C:\axis2c)
> > Add the path to lib directory to PATH variable (%AXIS2C_HOME%\lib)
> >
> > Doing these steps should sort your problem.
> >
> > Cheers
> >
> > Andrew
> >
> >
> > On 7/13/06, ant elder <an...@gmail.com> wrote:
> > >
> > > I think i have the latest RC2 but i've still the older versions lying
> > > around
> > > so maybe something is getting confused. Started again with a clean
> > > download
> > > and followed all the instructions. Running Calculator with basic
> client
> > > step
> > > 4 gives "the procedure entry point xmltextReaderConstEncoding could
> not
> > be
> > > located in dynamic link library libxml2.dll". I've not set any
> > environment
> > > variable for libxml or added it to the classpath so I don't know what
> > > version thats using. Should i still need to add anything for libxml,
> > zlib
> > > or
> > > iconv?
> > >
> > > ...ant
> > >
> > > On 7/13/06, Andrew Borley <aj...@gmail.com> wrote:
> > > >
> > > > Ant,
> > > >
> > > > I think these are all issues with the older RC - are you sure you've
> > > > downloaded the latest RC2
> > > > See http://people.apache.org/~robbinspg/RC-2/
> > > >
> > > > Cheers
> > > > Andy
> > > >
> > > >
> > > >
> > > > On 7/13/06, ant elder <an...@gmail.com> wrote:
> > > > >
> > > > > 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 <ro...@googlemail.com> 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
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
> --
> Pete
>
>
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Pete Robbins <ro...@googlemail.com>.
I think our bin release may be buillt against 2.6.19. In which case I need
to re-build it. (teach me for having lots of different versions around)
On 13/07/06, Andrew Borley <aj...@gmail.com> wrote:
>
> Hi Ant,
>
> Did you get the Axis2C samples working first? Your error is due either to
> the wong version of libxml2 (2.6.20 is what axis specifies) or not being
> able to find the libxml2 dll on the PATH. The Axis doc says:
> Copy libxml2.dll, iconv.dll and zlib1.dll to C:\axis2c\lib
> and
> Set the varibale AXIS2C_HOME to the deploy folder (C:\axis2c)
> Add the path to lib directory to PATH variable (%AXIS2C_HOME%\lib)
>
> Doing these steps should sort your problem.
>
> Cheers
>
> Andrew
>
>
> On 7/13/06, ant elder <an...@gmail.com> wrote:
> >
> > I think i have the latest RC2 but i've still the older versions lying
> > around
> > so maybe something is getting confused. Started again with a clean
> > download
> > and followed all the instructions. Running Calculator with basic client
> > step
> > 4 gives "the procedure entry point xmltextReaderConstEncoding could not
> be
> > located in dynamic link library libxml2.dll". I've not set any
> environment
> > variable for libxml or added it to the classpath so I don't know what
> > version thats using. Should i still need to add anything for libxml,
> zlib
> > or
> > iconv?
> >
> > ...ant
> >
> > On 7/13/06, Andrew Borley <aj...@gmail.com> wrote:
> > >
> > > Ant,
> > >
> > > I think these are all issues with the older RC - are you sure you've
> > > downloaded the latest RC2
> > > See http://people.apache.org/~robbinspg/RC-2/
> > >
> > > Cheers
> > > Andy
> > >
> > >
> > >
> > > On 7/13/06, ant elder <an...@gmail.com> wrote:
> > > >
> > > > 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 <ro...@googlemail.com> 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
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
--
Pete
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Andrew Borley <aj...@gmail.com>.
Hi Ant,
Did you get the Axis2C samples working first? Your error is due either to
the wong version of libxml2 (2.6.20 is what axis specifies) or not being
able to find the libxml2 dll on the PATH. The Axis doc says:
Copy libxml2.dll, iconv.dll and zlib1.dll to C:\axis2c\lib
and
Set the varibale AXIS2C_HOME to the deploy folder (C:\axis2c)
Add the path to lib directory to PATH variable (%AXIS2C_HOME%\lib)
Doing these steps should sort your problem.
Cheers
Andrew
On 7/13/06, ant elder <an...@gmail.com> wrote:
>
> I think i have the latest RC2 but i've still the older versions lying
> around
> so maybe something is getting confused. Started again with a clean
> download
> and followed all the instructions. Running Calculator with basic client
> step
> 4 gives "the procedure entry point xmltextReaderConstEncoding could not be
> located in dynamic link library libxml2.dll". I've not set any environment
> variable for libxml or added it to the classpath so I don't know what
> version thats using. Should i still need to add anything for libxml, zlib
> or
> iconv?
>
> ...ant
>
> On 7/13/06, Andrew Borley <aj...@gmail.com> wrote:
> >
> > Ant,
> >
> > I think these are all issues with the older RC - are you sure you've
> > downloaded the latest RC2
> > See http://people.apache.org/~robbinspg/RC-2/
> >
> > Cheers
> > Andy
> >
> >
> >
> > On 7/13/06, ant elder <an...@gmail.com> wrote:
> > >
> > > 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 <ro...@googlemail.com> 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
> > > >
> > > >
> > >
> > >
> >
> >
>
>
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by ant elder <an...@gmail.com>.
I think i have the latest RC2 but i've still the older versions lying around
so maybe something is getting confused. Started again with a clean download
and followed all the instructions. Running Calculator with basic client step
4 gives "the procedure entry point xmltextReaderConstEncoding could not be
located in dynamic link library libxml2.dll". I've not set any environment
variable for libxml or added it to the classpath so I don't know what
version thats using. Should i still need to add anything for libxml, zlib or
iconv?
...ant
On 7/13/06, Andrew Borley <aj...@gmail.com> wrote:
>
> Ant,
>
> I think these are all issues with the older RC - are you sure you've
> downloaded the latest RC2
> See http://people.apache.org/~robbinspg/RC-2/
>
> Cheers
> Andy
>
>
>
> On 7/13/06, ant elder <an...@gmail.com> wrote:
> >
> > 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 <ro...@googlemail.com> 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
> > >
> > >
> >
> >
>
>
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Andrew Borley <aj...@gmail.com>.
Ant,
I think these are all issues with the older RC - are you sure you've
downloaded the latest RC2?
See http://people.apache.org/~robbinspg/RC-2/
Cheers
Andy
On 7/13/06, ant elder <an...@gmail.com> wrote:
>
> 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 <ro...@googlemail.com> 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
> >
> >
>
>
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by ant elder <an...@gmail.com>.
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 <ro...@googlemail.com> 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
>
>
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Pete Robbins <ro...@googlemail.com>.
On 13/07/06, cr22rc <cr...@gmail.com> wrote:
>
> Great, seems like you already have done the work, just need both
> packages to reflect your efforts; a build / packaging issue.
and doc! Also needs a bit of code restructure in svn and build/package for
linux distros.... but apart from all that ...
--
Pete
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by cr22rc <cr...@gmail.com>.
Great, seems like you already have done the work, just need both
packages to reflect your efforts; a build / packaging issue.
Pete Robbins wrote:
> hmm... and there is a samples project in the src release too but I
> think we
> need the samples in bin and src release.
>
> Cheers
>
>
> On 13/07/06, Pete Robbins <ro...@googlemail.com> wrote:
>>
>>
>>
>> On 13/07/06, Rick <cr...@gmail.com> wrote:
>>
>> > Yep - go for it. You have committer access? Make us some.
>> > Well I was asked to vote on this. And yes as committer I can vote if
>> > this is really is ready as a separate distro ? Hmm, a package
>> without a
>> > single sample, a single smoke test ? How do I or even you know if it
>> > even works?
>>
>>
>> There is an sdotest with the sdo src release.
>>
>> --
>> Pete
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Pete Robbins <ro...@googlemail.com>.
hmm... and there is a samples project in the src release too but I think we
need the samples in bin and src release.
Cheers
On 13/07/06, Pete Robbins <ro...@googlemail.com> wrote:
>
>
>
> On 13/07/06, Rick <cr...@gmail.com> wrote:
>
> > Yep - go for it. You have committer access? Make us some.
> > Well I was asked to vote on this. And yes as committer I can vote if
> > this is really is ready as a separate distro ? Hmm, a package without a
> > single sample, a single smoke test ? How do I or even you know if it
> > even works?
>
>
> There is an sdotest with the sdo src release.
>
> --
> Pete
>
--
Pete
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Pete Robbins <ro...@googlemail.com>.
On 13/07/06, Rick <cr...@gmail.com> wrote:
>
> Yep - go for it. You have committer access? Make us some.
> Well I was asked to vote on this. And yes as committer I can vote if
> this is really is ready as a separate distro ? Hmm, a package without a
> single sample, a single smoke test ? How do I or even you know if it
> even works?
There is an sdotest with the sdo src release.
--
Pete
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Pete Robbins <ro...@googlemail.com>.
Rick,
The reason SDO is in here is because it is required by the SCA runtime. We
split it out into separate packages as SDO could be used without SCA. The
Java release just bundled averything together I believe. I agree there
should be samples for SDO if it is in this separate package and we should
therefore NOT release this asis.
I think putting ALL the doc in the gettingStarted file is a good idea and we
just leave the README and INSTALL to a minimum (link to GettingStarted).
This would also make it simple to hang the doc off the project web site.
Cheers,
On 13/07/06, Rick <cr...@gmail.com> wrote:
>
> Andrew Borley wrote:
> > On 7/13/06, cr22rc <cr...@gmail.com> wrote:
> >>
> >> Here are some comments for the SDO windows cpp binary package:
> >> Why does the "binary" GettingStarted.html talk about "Building and"...
> >> binary should be built already.
> >
> > Unlike getting the Axis2c requirement that seemed pretty straight
> >> forward, the libxml2 pages to find the right version seemed a bit more
> >> painful. I finally ended up here:
> >>
> http://www.zlatkovic.com/pub/libxml/oldreleases/libxml2-2.6.20.win32.zip
> >> And still am not 100% sure if I have the right libxml2. Was there a
> >> particular reason this link can't also be added to the
> >> GettingStarted.html so I could just click on it?
> >> (I know this link could go bad in the future, but I'd gamble it would
> >> stay current long enough for M1 and make it easy for users to get.)
> >
> > The three separate files GettingStarted.html readme and INSTALL adds for
> >> me a whole lot of confusion. GettStarted.html tells you look at README
> >> and it almost
> >> immediately tells you go back to GettingStarted.html . If these files
> >> all need to be there take two simplify them and make them just
> pointers
> >> to the other.
> >> I don't see why most of the README couldn't be rolled up into a section
> >> in GettingStarted.html. Same for INSTALL... in fact INSTALL could be
> >> made a whole lot nicer cause you could either put the separate
> platforms
> >> in different html files linked or in separate sections that had anchors
> >> you could point to.
> >
> >
> > We use the same README, INSTALL and GettingStarted.html for all
> platforms
> > and all distros which makes managing our documentation easy..
> > README and INSTALL are standard C++ project documentation files which
> > veteran C++ developers will go to directly. Rolling this information
> into
> > GettingStarted.html as well would cause maintenance headaches, so, for
> > less
> > experienced C++ developers we included the GettingStarted.html and
> > linked to
> > these text files. I don't think there is any issue with cross linking
> > between these docs - README is a standard README, INSTALL tells you
> > how to
> > install and GettingStarted provides a nice documentation front page for
> > newbies.
> >
> Well IMO the ease of managing of documentation has caused the flow that
> a new user experience to suffer. I really don't even see what I
> suggested to be less manageable. For those that expect a particular
> file to be present let it be there. As I suggested and move the
> majority of the content to gettingStarted.html it means they only have
> to bring up that one document. The bouncing back and forth still is as
> I see it is unnecessary.
> >
> > Now that I have the SDO binary installed what next ? Samples?
> >
> >
> > Yep - go for it. You have committer access? Make us some.
> Well I was asked to vote on this. And yes as committer I can vote if
> this is really is ready as a separate distro ? Hmm, a package without a
> single sample, a single smoke test ? How do I or even you know if it
> even works?
> >
> >
> >
> > Pete Robbins wrote:
> >> > I have posted a 2nd candidate for the first C++ release here:
> >> >
> >> http://people.apache.org/~robbinspg/RC-2<
> http://people.apache.org/%7Erobbinspg/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,
> >> >
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Pete
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Rick <cr...@gmail.com>.
Andrew Borley wrote:
> On 7/13/06, cr22rc <cr...@gmail.com> wrote:
>>
>> Here are some comments for the SDO windows cpp binary package:
>> Why does the "binary" GettingStarted.html talk about "Building and"...
>> binary should be built already.
>
> Unlike getting the Axis2c requirement that seemed pretty straight
>> forward, the libxml2 pages to find the right version seemed a bit more
>> painful. I finally ended up here:
>> http://www.zlatkovic.com/pub/libxml/oldreleases/libxml2-2.6.20.win32.zip
>> And still am not 100% sure if I have the right libxml2. Was there a
>> particular reason this link can't also be added to the
>> GettingStarted.html so I could just click on it?
>> (I know this link could go bad in the future, but I'd gamble it would
>> stay current long enough for M1 and make it easy for users to get.)
>
> The three separate files GettingStarted.html readme and INSTALL adds for
>> me a whole lot of confusion. GettStarted.html tells you look at README
>> and it almost
>> immediately tells you go back to GettingStarted.html . If these files
>> all need to be there take two simplify them and make them just pointers
>> to the other.
>> I don't see why most of the README couldn't be rolled up into a section
>> in GettingStarted.html. Same for INSTALL... in fact INSTALL could be
>> made a whole lot nicer cause you could either put the separate platforms
>> in different html files linked or in separate sections that had anchors
>> you could point to.
>
>
> We use the same README, INSTALL and GettingStarted.html for all platforms
> and all distros which makes managing our documentation easy..
> README and INSTALL are standard C++ project documentation files which
> veteran C++ developers will go to directly. Rolling this information into
> GettingStarted.html as well would cause maintenance headaches, so, for
> less
> experienced C++ developers we included the GettingStarted.html and
> linked to
> these text files. I don't think there is any issue with cross linking
> between these docs - README is a standard README, INSTALL tells you
> how to
> install and GettingStarted provides a nice documentation front page for
> newbies.
>
Well IMO the ease of managing of documentation has caused the flow that
a new user experience to suffer. I really don't even see what I
suggested to be less manageable. For those that expect a particular
file to be present let it be there. As I suggested and move the
majority of the content to gettingStarted.html it means they only have
to bring up that one document. The bouncing back and forth still is as
I see it is unnecessary.
>
> Now that I have the SDO binary installed what next ? Samples?
>
>
> Yep - go for it. You have committer access? Make us some.
Well I was asked to vote on this. And yes as committer I can vote if
this is really is ready as a separate distro ? Hmm, a package without a
single sample, a single smoke test ? How do I or even you know if it
even works?
>
>
>
> Pete Robbins wrote:
>> > I have posted a 2nd candidate for the first C++ release here:
>> >
>> http://people.apache.org/~robbinspg/RC-2<http://people.apache.org/%7Erobbinspg/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,
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Andrew Borley <aj...@gmail.com>.
On 7/13/06, cr22rc <cr...@gmail.com> wrote:
>
> Here are some comments for the SDO windows cpp binary package:
> Why does the "binary" GettingStarted.html talk about "Building and"...
> binary should be built already.
Unlike getting the Axis2c requirement that seemed pretty straight
> forward, the libxml2 pages to find the right version seemed a bit more
> painful. I finally ended up here:
> http://www.zlatkovic.com/pub/libxml/oldreleases/libxml2-2.6.20.win32.zip
> And still am not 100% sure if I have the right libxml2. Was there a
> particular reason this link can't also be added to the
> GettingStarted.html so I could just click on it?
> (I know this link could go bad in the future, but I'd gamble it would
> stay current long enough for M1 and make it easy for users to get.)
The three separate files GettingStarted.html readme and INSTALL adds for
> me a whole lot of confusion. GettStarted.html tells you look at README
> and it almost
> immediately tells you go back to GettingStarted.html . If these files
> all need to be there take two simplify them and make them just pointers
> to the other.
> I don't see why most of the README couldn't be rolled up into a section
> in GettingStarted.html. Same for INSTALL... in fact INSTALL could be
> made a whole lot nicer cause you could either put the separate platforms
> in different html files linked or in separate sections that had anchors
> you could point to.
We use the same README, INSTALL and GettingStarted.html for all platforms
and all distros which makes managing our documentation easy..
README and INSTALL are standard C++ project documentation files which
veteran C++ developers will go to directly. Rolling this information into
GettingStarted.html as well would cause maintenance headaches, so, for less
experienced C++ developers we included the GettingStarted.html and linked to
these text files. I don't think there is any issue with cross linking
between these docs - README is a standard README, INSTALL tells you how to
install and GettingStarted provides a nice documentation front page for
newbies.
Now that I have the SDO binary installed what next ? Samples?
Yep - go for it. You have committer access? Make us some.
Pete Robbins wrote:
> > I have posted a 2nd candidate for the first C++ release here:
> > http://people.apache.org/~robbinspg/RC-2<http://people.apache.org/%7Erobbinspg/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,
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by cr22rc <cr...@gmail.com>.
Here are some comments for the SDO windows cpp binary package:
Why does the "binary" GettingStarted.html talk about "Building and"...
binary should be built already.
Unlike getting the Axis2c requirement that seemed pretty straight
forward, the libxml2 pages to find the right version seemed a bit more
painful. I finally ended up here:
http://www.zlatkovic.com/pub/libxml/oldreleases/libxml2-2.6.20.win32.zip
And still am not 100% sure if I have the right libxml2. Was there a
particular reason this link can't also be added to the
GettingStarted.html so I could just click on it?
(I know this link could go bad in the future, but I'd gamble it would
stay current long enough for M1 and make it easy for users to get.)
The three separate files GettingStarted.html readme and INSTALL adds for
me a whole lot of confusion. GettStarted.html tells you look at README
and it almost
immediately tells you go back to GettingStarted.html. If these files
all need to be there take two simplify them and make them just pointers
to the other.
I don't see why most of the README couldn't be rolled up into a section
in GettingStarted.html. Same for INSTALL... in fact INSTALL could be
made a whole lot nicer cause you could either put the separate platforms
in different html files linked or in separate sections that had anchors
you could point to.
Now that I have the SDO binary installed what next ? Samples?
Pete Robbins 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,
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Pete Robbins <ro...@googlemail.com>.
comments inline:
On 14/07/06, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
>
> I tried the RC2 binary distribution, and was able to run the Calculator
> samples including the Calculator Web Service.
>
> The binary distributions look pretty good to me, I just found a few
> minor issues that should be easy to fix or document.
>
> SDO binary install:
>
> In INSTALL, the Linux binary install section should describe steps to
> configure TUSCANY_SDOCPP and make LD_LIBRARY_PATH point to
> $TUSCANY_SDOCPP/lib. I'm actually not sure if TUSCANY_SDOCPP is
> required, but the doc asks to configure it on Windows, so I'm guessing
> that it should be the same on Linux...
>
> bin/test/tuscany_sdo_test fails to load some XSDs, I think it should be
> removed, or the missing XSDs added.
This test is really for verifying the source build. It was not intended to
be in ht bin distro.
It would be nice to have an SDO sample, or add the missing XSDs to get
> tuscany_sdo_test working.
Working on this now!
SCA binary install:
>
> In INSTALL, the Linux binary install section should describe steps to
> configure TUSCANY_SCACPP and make LD_LIBRARY_PATH point to
> $TUSCANY_SCACPP/lib. Note that if you don't set TUSCANY_SCACPP, client
> programs still work, but Web Services running in the Axis2 HTTP server
> fail with a "SystemConfigurationException has been caught:
> TUSCANY_SCACPP environment variable not set" error.
TUSCANY_SCACPP is required to be set for the process where the runtime is
running. So it must be set when using a client as the runtime will be in the
same process. Not sure how it managed to work without this! The WSClient
does not need this set as it is a simple Axis2C client. TUSCANY_SCACPP must
be set for the process that will host the sca runtime, in this instance that
will be the axis server. All these instructions are already in the
samples/INSTALL instructions.
bin/test/tuscany_sca_test fails complaining that
> TUSCANY_SCACPP_SYSTEM_ROOT is not set.
again this test program is not intended for bin release. for src release
there is a script to run it.
Just a suggestion, in
> samples/Calculator/CalculatorModule/Calculator.wsdl, the soap:address
> http://localhost/axis/CalculatorService does not match the actual
> address of the Calculator service
> http://localhost:9090/axis2/services/Calculator. This is not preventing
> the sample to run because the Calculator client overrides the endpoint,
> but I think that having the correct endpoint in the WSDL in the first
> place will avoid confusion when people use that WSDL with a Web Service
> test tool for example or build a variation of the Calculator sample.
Will fix this.
I'll try the source distributions as well tomorrow.
Many thanks!
--
Pete
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Pete Robbins 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,
I tried the RC2 binary distribution, and was able to run the Calculator
samples including the Calculator Web Service.
The binary distributions look pretty good to me, I just found a few
minor issues that should be easy to fix or document.
SDO binary install:
In INSTALL, the Linux binary install section should describe steps to
configure TUSCANY_SDOCPP and make LD_LIBRARY_PATH point to
$TUSCANY_SDOCPP/lib. I'm actually not sure if TUSCANY_SDOCPP is
required, but the doc asks to configure it on Windows, so I'm guessing
that it should be the same on Linux...
bin/test/tuscany_sdo_test fails to load some XSDs, I think it should be
removed, or the missing XSDs added.
It would be nice to have an SDO sample, or add the missing XSDs to get
tuscany_sdo_test working.
SCA binary install:
In INSTALL, the Linux binary install section should describe steps to
configure TUSCANY_SCACPP and make LD_LIBRARY_PATH point to
$TUSCANY_SCACPP/lib. Note that if you don't set TUSCANY_SCACPP, client
programs still work, but Web Services running in the Axis2 HTTP server
fail with a "SystemConfigurationException has been caught:
TUSCANY_SCACPP environment variable not set" error.
bin/test/tuscany_sca_test fails complaining that
TUSCANY_SCACPP_SYSTEM_ROOT is not set.
Just a suggestion, in
samples/Calculator/CalculatorModule/Calculator.wsdl, the soap:address
http://localhost/axis/CalculatorService does not match the actual
address of the Calculator service
http://localhost:9090/axis2/services/Calculator. This is not preventing
the sample to run because the Calculator client overrides the endpoint,
but I think that having the correct endpoint in the WSDL in the first
place will avoid confusion when people use that WSDL with a Web Service
test tool for example or build a variation of the Calculator sample.
I'll try the source distributions as well tomorrow.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Andrew Borley <aj...@gmail.com>.
+1 from me.
Have tested on Windows and my old Fedora Core1 box, all happy.
Cheers
Andy
On 7/12/06, Edward Slattery <ed...@googlemail.com> wrote:
>
> I should add that the problem only occurs in the release build of
> Calculator, not the Debug build, and is specific to VC6 , not VC7.
> probably
> worth documenting but not a showstopper.
>
> On 12/07/06, Edward Slattery <ed...@googlemail.com> wrote:
> >
> > And thatll teach me! The VC6 build of Calculator still has a couple of
> > problems - mainly the Input for libs and the include path are not right.
> Ive
> > put them right and checked in the changes. Hope that helps.
> >
> >
> > On 12/07/06, Edward Slattery <ed...@googlemail.com> wrote:
> > >
> > > I have tried the command line, windows vc6 and windows vc7 in both
> > > release and debug mode. This one works for me!
> > > +1
> > >
> > >
> > > On 12/07/06, Brent Daniel <brenthdaniel@gmail.com > wrote:
> > > >
> > > > FYI, I took a quick look at this today and was able to run through
> the
> > > > setup and samples for the windows binary distribution without any
> > > > problems.
> > > >
> > > > Brent
> > > >
> > > >
> > > > On 7/12/06, Pete Robbins <ro...@googlemail.com> 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
> > > > >
> > > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > > >
> > > >
> > >
> >
>
>
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Edward Slattery <ed...@googlemail.com>.
I should add that the problem only occurs in the release build of
Calculator, not the Debug build, and is specific to VC6 , not VC7. probably
worth documenting but not a showstopper.
On 12/07/06, Edward Slattery <ed...@googlemail.com> wrote:
>
> And thatll teach me! The VC6 build of Calculator still has a couple of
> problems - mainly the Input for libs and the include path are not right. Ive
> put them right and checked in the changes. Hope that helps.
>
>
> On 12/07/06, Edward Slattery <ed...@googlemail.com> wrote:
> >
> > I have tried the command line, windows vc6 and windows vc7 in both
> > release and debug mode. This one works for me!
> > +1
> >
> >
> > On 12/07/06, Brent Daniel <brenthdaniel@gmail.com > wrote:
> > >
> > > FYI, I took a quick look at this today and was able to run through the
> > > setup and samples for the windows binary distribution without any
> > > problems.
> > >
> > > Brent
> > >
> > >
> > > On 7/12/06, Pete Robbins <ro...@googlemail.com> 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
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > >
> > >
> >
>
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Edward Slattery <ed...@googlemail.com>.
And thatll teach me! The VC6 build of Calculator still has a couple of
problems - mainly the Input for libs and the include path are not right. Ive
put them right and checked in the changes. Hope that helps.
On 12/07/06, Edward Slattery <ed...@googlemail.com> wrote:
>
> I have tried the command line, windows vc6 and windows vc7 in both
> release and debug mode. This one works for me!
> +1
>
>
> On 12/07/06, Brent Daniel <br...@gmail.com> wrote:
> >
> > FYI, I took a quick look at this today and was able to run through the
> > setup and samples for the windows binary distribution without any
> > problems.
> >
> > Brent
> >
> >
> > On 7/12/06, Pete Robbins <ro...@googlemail.com> 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
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Edward Slattery <ed...@googlemail.com>.
I have tried the command line, windows vc6 and windows vc7 in both release
and debug mode. This one works for me!
+1
On 12/07/06, Brent Daniel <br...@gmail.com> wrote:
>
> FYI, I took a quick look at this today and was able to run through the
> setup and samples for the windows binary distribution without any
> problems.
>
> Brent
>
>
> On 7/12/06, Pete Robbins <ro...@googlemail.com> 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
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
Re: [VOTE] Release Tuscany C++ Milestone 1
Posted by Brent Daniel <br...@gmail.com>.
FYI, I took a quick look at this today and was able to run through the
setup and samples for the windows binary distribution without any
problems.
Brent
On 7/12/06, Pete Robbins <ro...@googlemail.com> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org