Re: Native M3 Release

[Jean-Sebastien Delfino]

Pete Robbins wrote:

The IPMC has found an issue with a missing notice in the SDO C++ source
release being voted on. To fix this I can either remove the offending 
file
or update the Notice text. After re-building the distro to include 
this fix

do I need to hold another vote here for this release?

Cheers,



Pete,

I'm not sure if another vote is required here as the change is very 
minor and documented in [1]. Let's see what the IPMC folks say as you've 
asked the same question on the general-incubator list. I have checked 
the updated RC4 distros anyway (on Linux) and they look OK to me, so if 
there's another vote it gets my +1.


[1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg13663.html

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Native M3 Release

[Pete Robbins]

The IPMC has found an issue with a missing notice in the SDO C++ source
release being voted on. To fix this I can either remove the offending file
or update the Notice text. After re-building the distro to include this fix
do I need to hold another vote here for this release?

Cheers,

--
Pete

Re: Native M3 Release Candidate

[Pete Robbins]

On 16/03/07, Andrew Borley <[EMAIL PROTECTED]> wrote:


On 3/15/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
>
>
>
> On 3/15/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > On 3/15/07, Pete Robbins < [EMAIL PROTECTED]> wrote:
> > >
> > > Here is the latest candidate with fixes to the samples deploy
location
> > > on
> > > linux/mac
> > >
> > > http://people.apache.org/~robbinspg/M3-RC3/<
http://people.apache.org/%7Erobbinspg/M3-RC3/>
> > >
> > > If there are no major issues with this I will start a vote tomorrow.
> > >
> > > Cheers,
> > >
> > > --
> > > Pete
> > >
> >
> > I'm having trouble with RubyBigBank on Windows. It's crashing when it
> > tries to convert an SDO into a Rexml document  - anyone else see this
or is
> > it just my Ruby?
> > The line that's failing is 357 in RubyServiceProxy.cpp:
> >
> > value = rb_class_new_instance(1, vstr,
> > RubyImplementation::getXMLDocumentClass());
> >
> > This is trying to instantiate a new Document object from the
serialized
> > XML
> >
> > Cheers
> > Andy
> >
>
>
> The sample works fine on Linux BTW, it's just Windows that's failing.
>
> Andy
>

Ruby REXML problem found and fixed in r518904. A static method was being
called & returning variables that were only being initialized in the
constructor...

Cheers
Andy



Great. I have added the copyright to the Notice files and applied Caroline's
patch to SDO. I think we are at a point where I can generate a candidate to
vote on.

Cheers

--
Pete

Re: Native M3 Release Candidate

[Andrew Borley]

On 3/15/07, Andrew Borley <[EMAIL PROTECTED]> wrote:




On 3/15/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
>
>
>
> On 3/15/07, Pete Robbins < [EMAIL PROTECTED]> wrote:
> >
> > Here is the latest candidate with fixes to the samples deploy location
> > on
> > linux/mac
> >
> > 
http://people.apache.org/~robbinspg/M3-RC3/
> >
> > If there are no major issues with this I will start a vote tomorrow.
> >
> > Cheers,
> >
> > --
> > Pete
> >
>
> I'm having trouble with RubyBigBank on Windows. It's crashing when it
> tries to convert an SDO into a Rexml document  - anyone else see this or is
> it just my Ruby?
> The line that's failing is 357 in RubyServiceProxy.cpp:
>
> value = rb_class_new_instance(1, vstr,
> RubyImplementation::getXMLDocumentClass());
>
> This is trying to instantiate a new Document object from the serialized
> XML
>
> Cheers
> Andy
>


The sample works fine on Linux BTW, it's just Windows that's failing.

Andy



Ruby REXML problem found and fixed in r518904. A static method was being
called & returning variables that were only being initialized in the
constructor...

Cheers
Andy

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, Caroline Maynard <[EMAIL PROTECTED]> wrote:


Would you please include my patch for
https://issues.apache.org/jira/browse/TUSCANY-1166? AFAIK this is not
contentious.

--
Caroline




I'll apply that so it will be picked up in the next re-spin.

Cheers,

--
Pete

Re: Native M3 Release Candidate

[Caroline Maynard]

Would you please include my patch for
https://issues.apache.org/jira/browse/TUSCANY-1166? AFAIK this is not
contentious.

--
Caroline

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, Pete Robbins <[EMAIL PROTECTED]> wrote:




On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >
> > On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> > >
> > > On 3/15/07, Pete Robbins <[EMAIL PROTECTED] > wrote:
> > > >
> > > > On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > So that prompted me to check the licenses. Zlib and libxml2 look
>
> > fine
> > > i
> > > > > think though they do need to be added to the Tuscany LICENSE and
> > > NOTICE
> > > > > files if the Tuscany code is using those APIs whether or not
> Tuscany
> > > > > Native
> > > > > is distributing them. Looks like iconv is LGPL which isn't ASF
> > > friendly.
> > > > > Is
> > > > > the Tuscany Native code actually using the iconv APIs?
> > > > >
> > > > >   ...ant
> > > >
> > > >
> > > > we do not use iconv at all. It just has to be there for libxml2 to
> > work.
> > > >
> > > > The only APIs used are for libxml2. I did not think that use of an
> API
> > > > requires a mention in the NOTICE file as we are not including any
> > > libxml2
> > > > artifacts. If it does then do we need to add entries for:
> > > > Ruby
> > > > Python
> > > > Curl
> > > > Httpd
> > > > Axis2c
> > > > gcc
> > > > java
> > > > ant
> > > > automake
> > > > autoconf
> > > > .
> > > >
> > > > ?
> > >
> > >
> > > I can't find a web page to point to with a definitive answer right
> now,
> > > but
> > > this is how i thought this worked:
> > >
> > > If ASF code directly uses the APIs of a third party work then you
> need
> > > mention this in the LICENSE and NOTICE files (unless its another ASF
> > > project). Its not about whether or not we actually distribute the
> third
> > > party work, its if the third party code is required to make a
> > functioning
> > > build of our project.
> > >
> > > I could be wrong, does anyone else know?
> > >
> > >   ...ant
> > >
> >
> > All the NOTICE files I look at only mention included works. Can you
> check
> > this out?
>
>
> I can't find anything definitive. Browsing the download areas its easy
> to
> find artifacts that *do* have NOTICE files that mention dependent works
> that
> are not distributed.  I'll leave it to you to take further or ignore.
> The
> ASF copyright is missing from the NOTICE files though so I think you do
> need
> to fix that (sorry i missed that earlier). There's an eg NOTICE file at:
>
> http://www.apache.org/licenses/example-NOTICE.txt
>
>   ...ant
>

Thanks. I'll add the copyright. The RAT tool didn't pick this up.


--
Pete




I asked on [EMAIL PROTECTED] and it seems we do NOT need to list libxml etc
in the NOTICE file.

Cheers,
--
Pete

Re: Native M3 Release Candidate

[Pete Robbins]

That is correct. We can release sdo and sca separately too (they are
separate downloads) it's just that they are both ready for a new release.

So... keep DASing ;-)

Cheers,


On 15/03/07, Luciano Resende <[EMAIL PROTECTED]> wrote:


Quick question...I'm assuming the current C++ DAS is not being picked up
for
the current Native Release, so applying new patches to the C++ DAS will
not
affect the release... but I just want to double check if I have the right
understanding...

--
Luciano Resende
http://people.apache.org/~lresende

On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> On 15/03/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> > >
> > > On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > > >
> > > > On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> > > > >
> > > > > On 3/15/07, Pete Robbins <[EMAIL PROTECTED] > wrote:
> > > > > >
> > > > > > On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> > > > > > >
> > > > > > > So that prompted me to check the licenses. Zlib and libxml2
> look
> > >
> > > > fine
> > > > > i
> > > > > > > think though they do need to be added to the Tuscany LICENSE
> and
> > > > > NOTICE
> > > > > > > files if the Tuscany code is using those APIs whether or not
> > > Tuscany
> > > > > > > Native
> > > > > > > is distributing them. Looks like iconv is LGPL which isn't
ASF
> > > > > friendly.
> > > > > > > Is
> > > > > > > the Tuscany Native code actually using the iconv APIs?
> > > > > > >
> > > > > > >   ...ant
> > > > > >
> > > > > >
> > > > > > we do not use iconv at all. It just has to be there for
libxml2
> to
> > > > work.
> > > > > >
> > > > > > The only APIs used are for libxml2. I did not think that use
of
> an
> > > API
> > > > > > requires a mention in the NOTICE file as we are not including
> any
> > > > > libxml2
> > > > > > artifacts. If it does then do we need to add entries for:
> > > > > > Ruby
> > > > > > Python
> > > > > > Curl
> > > > > > Httpd
> > > > > > Axis2c
> > > > > > gcc
> > > > > > java
> > > > > > ant
> > > > > > automake
> > > > > > autoconf
> > > > > > .
> > > > > >
> > > > > > ?
> > > > >
> > > > >
> > > > > I can't find a web page to point to with a definitive answer
right
> > > now,
> > > > > but
> > > > > this is how i thought this worked:
> > > > >
> > > > > If ASF code directly uses the APIs of a third party work then
you
> > > need
> > > > > mention this in the LICENSE and NOTICE files (unless its another
> ASF
> > > > > project). Its not about whether or not we actually distribute
the
> > > third
> > > > > party work, its if the third party code is required to make a
> > > > functioning
> > > > > build of our project.
> > > > >
> > > > > I could be wrong, does anyone else know?
> > > > >
> > > > >   ...ant
> > > > >
> > > >
> > > > All the NOTICE files I look at only mention included works. Can
you
> > > check
> > > > this out?
> > >
> > >
> > > I can't find anything definitive. Browsing the download areas its
easy
> > > to
> > > find artifacts that *do* have NOTICE files that mention dependent
> works
> > > that
> > > are not distributed.  I'll leave it to you to take further or
ignore.
> > > The
> > > ASF copyright is missing from the NOTICE files though so I think you
> do
> > > need
> > > to fix that (sorry i missed that earlier). There's an eg NOTICE file
> at:
> > >
> > > http://www.apache.org/licenses/example-NOTICE.txt
> > >
> > >   ...ant
> > >
> >
> > Thanks. I'll add the copyright. The RAT tool didn't pick this up.
> >
> >
> > --
> > Pete
> >
>
>
> I asked on [EMAIL PROTECTED] and it seems we do NOT need to list libxml
> etc
> in the NOTICE file.
>
> Cheers,
> --
> Pete
>





--
Pete

Re: Native M3 Release Candidate

[Luciano Resende]

Quick question...I'm assuming the current C++ DAS is not being picked up for
the current Native Release, so applying new patches to the C++ DAS will not
affect the release... but I just want to double check if I have the right
understanding...

--
Luciano Resende
http://people.apache.org/~lresende

On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


On 15/03/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
>
>
> On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> >
> > On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > >
> > > On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> > > >
> > > > On 3/15/07, Pete Robbins <[EMAIL PROTECTED] > wrote:
> > > > >
> > > > > On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > > So that prompted me to check the licenses. Zlib and libxml2
look
> >
> > > fine
> > > > i
> > > > > > think though they do need to be added to the Tuscany LICENSE
and
> > > > NOTICE
> > > > > > files if the Tuscany code is using those APIs whether or not
> > Tuscany
> > > > > > Native
> > > > > > is distributing them. Looks like iconv is LGPL which isn't ASF
> > > > friendly.
> > > > > > Is
> > > > > > the Tuscany Native code actually using the iconv APIs?
> > > > > >
> > > > > >   ...ant
> > > > >
> > > > >
> > > > > we do not use iconv at all. It just has to be there for libxml2
to
> > > work.
> > > > >
> > > > > The only APIs used are for libxml2. I did not think that use of
an
> > API
> > > > > requires a mention in the NOTICE file as we are not including
any
> > > > libxml2
> > > > > artifacts. If it does then do we need to add entries for:
> > > > > Ruby
> > > > > Python
> > > > > Curl
> > > > > Httpd
> > > > > Axis2c
> > > > > gcc
> > > > > java
> > > > > ant
> > > > > automake
> > > > > autoconf
> > > > > .
> > > > >
> > > > > ?
> > > >
> > > >
> > > > I can't find a web page to point to with a definitive answer right
> > now,
> > > > but
> > > > this is how i thought this worked:
> > > >
> > > > If ASF code directly uses the APIs of a third party work then you
> > need
> > > > mention this in the LICENSE and NOTICE files (unless its another
ASF
> > > > project). Its not about whether or not we actually distribute the
> > third
> > > > party work, its if the third party code is required to make a
> > > functioning
> > > > build of our project.
> > > >
> > > > I could be wrong, does anyone else know?
> > > >
> > > >   ...ant
> > > >
> > >
> > > All the NOTICE files I look at only mention included works. Can you
> > check
> > > this out?
> >
> >
> > I can't find anything definitive. Browsing the download areas its easy
> > to
> > find artifacts that *do* have NOTICE files that mention dependent
works
> > that
> > are not distributed.  I'll leave it to you to take further or ignore.
> > The
> > ASF copyright is missing from the NOTICE files though so I think you
do
> > need
> > to fix that (sorry i missed that earlier). There's an eg NOTICE file
at:
> >
> > http://www.apache.org/licenses/example-NOTICE.txt
> >
> >   ...ant
> >
>
> Thanks. I'll add the copyright. The RAT tool didn't pick this up.
>
>
> --
> Pete
>


I asked on [EMAIL PROTECTED] and it seems we do NOT need to list libxml
etc
in the NOTICE file.

Cheers,
--
Pete

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:


On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> >
> > On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > >
> > > On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> > > >
> > > > So that prompted me to check the licenses. Zlib and libxml2 look
> fine
> > i
> > > > think though they do need to be added to the Tuscany LICENSE and
> > NOTICE
> > > > files if the Tuscany code is using those APIs whether or not
Tuscany
> > > > Native
> > > > is distributing them. Looks like iconv is LGPL which isn't ASF
> > friendly.
> > > > Is
> > > > the Tuscany Native code actually using the iconv APIs?
> > > >
> > > >   ...ant
> > >
> > >
> > > we do not use iconv at all. It just has to be there for libxml2 to
> work.
> > >
> > > The only APIs used are for libxml2. I did not think that use of an
API
> > > requires a mention in the NOTICE file as we are not including any
> > libxml2
> > > artifacts. If it does then do we need to add entries for:
> > > Ruby
> > > Python
> > > Curl
> > > Httpd
> > > Axis2c
> > > gcc
> > > java
> > > ant
> > > automake
> > > autoconf
> > > .
> > >
> > > ?
> >
> >
> > I can't find a web page to point to with a definitive answer right
now,
> > but
> > this is how i thought this worked:
> >
> > If ASF code directly uses the APIs of a third party work then you need
> > mention this in the LICENSE and NOTICE files (unless its another ASF
> > project). Its not about whether or not we actually distribute the
third
> > party work, its if the third party code is required to make a
> functioning
> > build of our project.
> >
> > I could be wrong, does anyone else know?
> >
> >   ...ant
> >
>
> All the NOTICE files I look at only mention included works. Can you
check
> this out?


I can't find anything definitive. Browsing the download areas its easy to
find artifacts that *do* have NOTICE files that mention dependent works
that
are not distributed.  I'll leave it to you to take further or ignore. The
ASF copyright is missing from the NOTICE files though so I think you do
need
to fix that (sorry i missed that earlier). There's an eg NOTICE file at:
http://www.apache.org/licenses/example-NOTICE.txt

  ...ant



Thanks. I'll add the copyright. The RAT tool didn't pick this up.


--
Pete

Re: Native M3 Release Candidate

[ant elder]

On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >
> > On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> > >
> > > So that prompted me to check the licenses. Zlib and libxml2 look
fine
> i
> > > think though they do need to be added to the Tuscany LICENSE and
> NOTICE
> > > files if the Tuscany code is using those APIs whether or not Tuscany
> > > Native
> > > is distributing them. Looks like iconv is LGPL which isn't ASF
> friendly.
> > > Is
> > > the Tuscany Native code actually using the iconv APIs?
> > >
> > >   ...ant
> >
> >
> > we do not use iconv at all. It just has to be there for libxml2 to
work.
> >
> > The only APIs used are for libxml2. I did not think that use of an API
> > requires a mention in the NOTICE file as we are not including any
> libxml2
> > artifacts. If it does then do we need to add entries for:
> > Ruby
> > Python
> > Curl
> > Httpd
> > Axis2c
> > gcc
> > java
> > ant
> > automake
> > autoconf
> > .
> >
> > ?
>
>
> I can't find a web page to point to with a definitive answer right now,
> but
> this is how i thought this worked:
>
> If ASF code directly uses the APIs of a third party work then you need
> mention this in the LICENSE and NOTICE files (unless its another ASF
> project). Its not about whether or not we actually distribute the third
> party work, its if the third party code is required to make a
functioning
> build of our project.
>
> I could be wrong, does anyone else know?
>
>   ...ant
>

All the NOTICE files I look at only mention included works. Can you check
this out?



I can't find anything definitive. Browsing the download areas its easy to
find artifacts that *do* have NOTICE files that mention dependent works that
are not distributed.  I'll leave it to you to take further or ignore. The
ASF copyright is missing from the NOTICE files though so I think you do need
to fix that (sorry i missed that earlier). There's an eg NOTICE file at:
http://www.apache.org/licenses/example-NOTICE.txt

  ...ant

Re: Native M3 Release Candidate

[Andrew Borley]

On 3/15/07, Andrew Borley <[EMAIL PROTECTED]> wrote:




On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> Here is the latest candidate with fixes to the samples deploy location
> on
> linux/mac
>
> 
http://people.apache.org/~robbinspg/M3-RC3/
>
> If there are no major issues with this I will start a vote tomorrow.
>
> Cheers,
>
> --
> Pete
>

I'm having trouble with RubyBigBank on Windows. It's crashing when it
tries to convert an SDO into a Rexml document  - anyone else see this or is
it just my Ruby?
The line that's failing is 357 in RubyServiceProxy.cpp:

value = rb_class_new_instance(1, vstr,
RubyImplementation::getXMLDocumentClass());

This is trying to instantiate a new Document object from the serialized
XML

Cheers
Andy




The sample works fine on Linux BTW, it's just Windows that's failing.

Andy

Re: Native M3 Release Candidate

[Andrew Borley]

On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


Here is the latest candidate with fixes to the samples deploy location on
linux/mac

http://people.apache.org/~robbinspg/M3-RC3/

If there are no major issues with this I will start a vote tomorrow.

Cheers,

--
Pete



I'm having trouble with RubyBigBank on Windows. It's crashing when it tries
to convert an SDO into a Rexml document  - anyone else see this or is it
just my Ruby?
The line that's failing is 357 in RubyServiceProxy.cpp:

value = rb_class_new_instance(1, vstr,
RubyImplementation::getXMLDocumentClass());

This is trying to instantiate a new Document object from the serialized XML

Cheers
Andy

Re: Native M3 Release Candidate

[Pete Robbins]

Here is the latest candidate with fixes to the samples deploy location on
linux/mac

http://people.apache.org/~robbinspg/M3-RC3/

If there are no major issues with this I will start a vote tomorrow.

Cheers,

--
Pete

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


A refresh of the release candidate is now available at:
http://people.apache.org/~robbinspg/M3-RC2/

Hopefully this addresses the issues raised above.

Cheers,
--
Pete




Oh well... I still haven't fixed the deployment of the samples on linux. So
I'll fix this up and re-build.

:-(
--
Pete

Re: Native M3 Release Candidate

[Andrew Borley]

On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


A refresh of the release candidate is now available at:
http://people.apache.org/~robbinspg/M3-RC2/

Hopefully this addresses the issues raised above.

Cheers,
--
Pete



RAT looks good for all packages. The SDO test xml files are showing, but I
remember this was OK'd by the incubator-general list in the last release as
these are for comparison against generated test files.

Cheers
Andy

Re: Native M3 Release Candidate

[Pete Robbins]

A refresh of the release candidate is now available at:
http://people.apache.org/~robbinspg/M3-RC2/

Hopefully this addresses the issues raised above.

Cheers,
--
Pete

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:


On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> >
> > So that prompted me to check the licenses. Zlib and libxml2 look fine
i
> > think though they do need to be added to the Tuscany LICENSE and
NOTICE
> > files if the Tuscany code is using those APIs whether or not Tuscany
> > Native
> > is distributing them. Looks like iconv is LGPL which isn't ASF
friendly.
> > Is
> > the Tuscany Native code actually using the iconv APIs?
> >
> >   ...ant
>
>
> we do not use iconv at all. It just has to be there for libxml2 to work.
>
> The only APIs used are for libxml2. I did not think that use of an API
> requires a mention in the NOTICE file as we are not including any
libxml2
> artifacts. If it does then do we need to add entries for:
> Ruby
> Python
> Curl
> Httpd
> Axis2c
> gcc
> java
> ant
> automake
> autoconf
> .
>
> ?


I can't find a web page to point to with a definitive answer right now,
but
this is how i thought this worked:

If ASF code directly uses the APIs of a third party work then you need
mention this in the LICENSE and NOTICE files (unless its another ASF
project). Its not about whether or not we actually distribute the third
party work, its if the third party code is required to make a functioning
build of our project.

I could be wrong, does anyone else know?

  ...ant



All the NOTICE files I look at only mention included works. Can you check
this out?

Cheers,

--
Pete

Re: Native M3 Release Candidate

[ant elder]

On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> So that prompted me to check the licenses. Zlib and libxml2 look fine i
> think though they do need to be added to the Tuscany LICENSE and NOTICE
> files if the Tuscany code is using those APIs whether or not Tuscany
> Native
> is distributing them. Looks like iconv is LGPL which isn't ASF friendly.
> Is
> the Tuscany Native code actually using the iconv APIs?
>
>   ...ant


we do not use iconv at all. It just has to be there for libxml2 to work.

The only APIs used are for libxml2. I did not think that use of an API
requires a mention in the NOTICE file as we are not including any libxml2
artifacts. If it does then do we need to add entries for:
Ruby
Python
Curl
Httpd
Axis2c
gcc
java
ant
automake
autoconf
.

?



I can't find a web page to point to with a definitive answer right now, but
this is how i thought this worked:

If ASF code directly uses the APIs of a third party work then you need
mention this in the LICENSE and NOTICE files (unless its another ASF
project). Its not about whether or not we actually distribute the third
party work, its if the third party code is required to make a functioning
build of our project.

I could be wrong, does anyone else know?

  ...ant

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:


So that prompted me to check the licenses. Zlib and libxml2 look fine i
think though they do need to be added to the Tuscany LICENSE and NOTICE
files if the Tuscany code is using those APIs whether or not Tuscany
Native
is distributing them. Looks like iconv is LGPL which isn't ASF friendly.
Is
the Tuscany Native code actually using the iconv APIs?

  ...ant



we do not use iconv at all. It just has to be there for libxml2 to work.

The only APIs used are for libxml2. I did not think that use of an API
requires a mention in the NOTICE file as we are not including any libxml2
artifacts. If it does then do we need to add entries for:
Ruby
Python
Curl
Httpd
Axis2c
gcc
java
ant
automake
autoconf
.

?

Cheers,

--
Pete

Re: Native M3 Release Candidate

[Simon Laws]

On 3/15/07, ant elder <[EMAIL PROTECTED]> wrote:


So that prompted me to check the licenses. Zlib and libxml2 look fine i
think though they do need to be added to the Tuscany LICENSE and NOTICE
files if the Tuscany code is using those APIs whether or not Tuscany
Native
is distributing them. Looks like iconv is LGPL which isn't ASF friendly.
Is
the Tuscany Native code actually using the iconv APIs?

   ...ant

On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
> >
> > On 3/15/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> > >
> > > ant elder wrote:
> > > > I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking
for
> > > that
> > > > but can't find a pre-compiled win32 version for that, so I tried
> > > > 2.6.23 and
> > > > using that the sample runs fine.
> > > >
> > > >   ...ant
> > > >
> > >
> > > Would it help to have on our Wiki a page with actual links to the
> > > (Windows) dependency downloads that people have been successful
with?
> > > This way users won't have to fish for distributions of libxml for
> > > example that work for us.
> > >
> > > What do you think?
> >
> >
> > Sure that would be useful but IMHO even better would be to just
> distribute
> > these dependencies with the binary distro. I know not everyone agrees
> with
> > that though.
> >
> >   ...ant
> >
>
> I really think that is a bad thing to do even considering the License
> issues
> of re-distributing some of them.
>
> --
> Pete
>



You might want to ignore this as I didn't strictly follow the
instructions

I installed IBM JDK 5 and dependencies on my Fedora Core 6 box (only becuase
that's what I have on my FC5 box which has worked fine with Tuscany Native
in the past). Am getting strange results from scagen. In the CppCalculator
test it generated, for example

...
float CalculatorImpl_CalculatorService_Proxy::add( float arg0,  float arg1)
{
   tuscany::sca::Operation operation("add");
   operation.addParameter("arg1", &arg0);
   operation.addParameter("arg2", &arg1);
   float ret;
   operation.setReturnValue(&ret);
   target->invoke(operation);
   return *(float*)operation.getReturnValue();
}
...

I.e. it seems to be URL encoding the generated code. I suspect this is some
setting somewhere as I've not had this before and Sebastien has just run
successfully.  I'll look at it a little closer later when I have more time.

Simon

Re: Native M3 Release Candidate

[ant elder]

So that prompted me to check the licenses. Zlib and libxml2 look fine i
think though they do need to be added to the Tuscany LICENSE and NOTICE
files if the Tuscany code is using those APIs whether or not Tuscany Native
is distributing them. Looks like iconv is LGPL which isn't ASF friendly. Is
the Tuscany Native code actually using the iconv APIs?

  ...ant

On 3/15/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> On 3/15/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> >
> > ant elder wrote:
> > > I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking for
> > that
> > > but can't find a pre-compiled win32 version for that, so I tried
> > > 2.6.23 and
> > > using that the sample runs fine.
> > >
> > >   ...ant
> > >
> >
> > Would it help to have on our Wiki a page with actual links to the
> > (Windows) dependency downloads that people have been successful with?
> > This way users won't have to fish for distributions of libxml for
> > example that work for us.
> >
> > What do you think?
>
>
> Sure that would be useful but IMHO even better would be to just
distribute
> these dependencies with the binary distro. I know not everyone agrees
with
> that though.
>
>   ...ant
>

I really think that is a bad thing to do even considering the License
issues
of re-distributing some of them.

--
Pete

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:


[snip]
Jean-Sebastien Delfino wrote:
>
> I just finished testing all the samples on RHEL4 and they all worked
> for me except AlertAggregator, which gives me this:
>
[snip]
> The HTTPD server log says this:
>
> Traceback (most recent call last):
>  File
>
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py",
> line 19, in 
>import feedparser, datetime, xml.etree.ElementTree, re
> ImportError: No module named feedparser

My mistake, I guess I forgot to read the doc... and install the
feedparser library :) All the docs and the samples are really really
nice BTW, I'm impressed!

I'll continue to test it tomorrow when I get a some time... after I
install the feedparser library...

--
Jean-Sebastien



Thanks everyone. This is all great feedback.

--
Pete

Re: Native M3 Release Candidate

[Jean-Sebastien Delfino]

[snip]
Jean-Sebastien Delfino wrote:


I just finished testing all the samples on RHEL4 and they all worked 
for me except AlertAggregator, which gives me this:



[snip]

The HTTPD server log says this:

Traceback (most recent call last):
 File 
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py", 
line 19, in 

   import feedparser, datetime, xml.etree.ElementTree, re
ImportError: No module named feedparser


My mistake, I guess I forgot to read the doc... and install the 
feedparser library :) All the docs and the samples are really really 
nice BTW, I'm impressed!


I'll continue to test it tomorrow when I get a some time... after I 
install the feedparser library...


--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, ant elder <[EMAIL PROTECTED]> wrote:


On 3/15/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> ant elder wrote:
> > I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking for
> that
> > but can't find a pre-compiled win32 version for that, so I tried
> > 2.6.23 and
> > using that the sample runs fine.
> >
> >   ...ant
> >
>
> Would it help to have on our Wiki a page with actual links to the
> (Windows) dependency downloads that people have been successful with?
> This way users won't have to fish for distributions of libxml for
> example that work for us.
>
> What do you think?


Sure that would be useful but IMHO even better would be to just distribute
these dependencies with the binary distro. I know not everyone agrees with
that though.

  ...ant



I really think that is a bad thing to do even considering the License issues
of re-distributing some of them.

--
Pete

Re: Native M3 Release Candidate

[ant elder]

On 3/15/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:


ant elder wrote:
> I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking for
that
> but can't find a pre-compiled win32 version for that, so I tried
> 2.6.23 and
> using that the sample runs fine.
>
>   ...ant
>

Would it help to have on our Wiki a page with actual links to the
(Windows) dependency downloads that people have been successful with?
This way users won't have to fish for distributions of libxml for
example that work for us.

What do you think?



Sure that would be useful but IMHO even better would be to just distribute
these dependencies with the binary distro. I know not everyone agrees with
that though.

  ...ant

Re: Native M3 Release Candidate

[Jean-Sebastien Delfino]

[snip]
Simon Laws wrote:

Just compiling up SCA (on a fresh Fedora Core 6 machine this time). A few
comments when following the instructions so far.

Builidng core SCA
 Without Ant and JDK on the path the tools build fails

Looking at the getting starter page. Not sure what to do once the core 
has
been built. I know from experience that I need to build a sample and, 
before

this, build the appropriate extensions. But it's not obvious from the SCA
getting started page. Would be good to give an example of the very first
thing someone might like to try after buidling the core, e.g. now go 
build
the C++ extensions and try the CPPCalculator sample. Or is there some 
other

test I should try to prove that the compile was successful?

Tuscany SCA Extensions

Links don't work as doc is missing.

Samples
Small point - Could you extend the link highlighting from "getting 
started"

to "samples getting started".

Tuscany Samples - Getting Started

Samples Dependencies table 1.
Doc appears to be missing from the doc directory so links at top of table
don;t work
HTTPDBigBang link doesn't work
AlertAggregator link doesn't work

Just downloading a JDK so will let you know how I get on once done.

Simon



I just finished testing all the samples on RHEL4 and they all worked for 
me except AlertAggregator, which gives me this:


Apache Tuscany Alert Aggregator Sample

Alert Sources:
Internal Server Error

The server encountered an internal error or misconfiguration and was 
unable to complete your request.


Please contact the server administrator, [no address given] and inform 
them of the time the error occurred, and anything you might have done 
that may have caused the error.


More information about this error may be available in the server error log.

Recent Alerts (Refresh):
Internal Server Error

The server encountered an internal error or misconfiguration and was 
unable to complete your request.


Please contact the server administrator, [no address given] and inform 
them of the time the error occurred, and anything you might have done 
that may have caused the error.


More information about this error may be available in the server error log.

The HTTPD server log says this:

Traceback (most recent call last):
 File 
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py", 
line 19, in 

   import feedparser, datetime, xml.etree.ElementTree, re
ImportError: No module named feedparser
Traceback (most recent call last):
 File 
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py", 
line 19, in 

   import feedparser, datetime, xml.etree.ElementTree, re
ImportError: No module named feedparser
Traceback (most recent call last):
 File 
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py", 
line 19, in 

   import feedparser, datetime, xml.etree.ElementTree, re
ImportError: No module named feedparser
Traceback (most recent call last):
 File 
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py", 
line 19, in 

   import feedparser, datetime, xml.etree.ElementTree, re
ImportError: No module named feedparser
Traceback (most recent call last):
 File 
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py", 
line 19, in 

   import feedparser, datetime, xml.etree.ElementTree, re
ImportError: No module named feedparser
Traceback (most recent call last):
 File 
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py", 
line 19, in 

   import feedparser, datetime, xml.etree.ElementTree, re
ImportError: No module named feedparser
Traceback (most recent call last):
 File 
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py", 
line 19, in 

   import feedparser, datetime, xml.etree.ElementTree, re
ImportError: No module named feedparser
Traceback (most recent call last):
 File 
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py", 
line 19, in 

   import feedparser, datetime, xml.etree.ElementTree, re
ImportError: No module named feedparser
Traceback (most recent call last):
 File 
"/home/delfinoj/Tuscany/apache-deploy/cpp/sca/samples/AlertAggregator/deploy/httpserver/..//sample.alerter/RSSCheckerImpl.py", 
line 19, in 

   import feedparser, datetime, xml.etree.ElementTree, re
ImportError: No module named feedparser

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 Release Candidate

[Jean-Sebastien Delfino]

Pete Robbins wrote:

On 15/03/07, Simon Laws <[EMAIL PROTECTED]> wrote:


On 3/15/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> ant elder wrote:
> > I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking for
> that
> > but can't find a pre-compiled win32 version for that, so I tried
> > 2.6.23 and
> > using that the sample runs fine.
> >
> >   ...ant
> >
>
> Would it help to have on our Wiki a page with actual links to the
> (Windows) dependency downloads that people have been successful with?
> This way users won't have to fish for distributions of libxml for
> example that work for us.
>
> What do you think?
>
> --
> Jean-Sebastien
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> The getting started pages in the release have got dependency lists 
with

quite an amount of detail in but I like the idea  of having somewhere
where
we can record the links to dependencies and update it with any funnies
that
people find.  This page was started a while back  (
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+CPP+Dependencies)
but
not finished. We could tidy that up and put more accurate links in.

Simon



A good idea but not essential for this release. The dependencies are 
spelt
out in the doc as some folk complained when I origianally just had 
links to

where to get the pre-reqs. Some seem unable to read the instructions for
those pre-reqs and want them repeated in our doc (which is daft as 
they can

get out of date quite easily).

Cheers,



Pete,

Agreed. I was just proposing to have a Wiki page maintained on the side, 
not essential for the release :) which could evolve over time. If I get 
to try the Windows binaries in the next few days, I'll add the links 
that work for me to the page that Simon mentioned.


--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, Simon Laws <[EMAIL PROTECTED]> wrote:


On 3/15/07, Simon Laws <[EMAIL PROTECTED]> wrote:
>
>
>
> On 3/15/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> >
> > ant elder wrote:
> > > I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking for
> > that
> > > but can't find a pre-compiled win32 version for that, so I tried
> > > 2.6.23 and
> > > using that the sample runs fine.
> > >
> > >   ...ant
> > >
> >
> > Would it help to have on our Wiki a page with actual links to the
> > (Windows) dependency downloads that people have been successful with?
> > This way users won't have to fish for distributions of libxml for
> > example that work for us.
> >
> > What do you think?
> >
> > --
> > Jean-Sebastien
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > The getting started pages in the release have got dependency lists
with
> quite an amount of detail in but I like the idea  of having somewhere
where
> we can record the links to dependencies and update it with any funnies
that
> people find.  This page was started a while back  (
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+CPP+Dependencies)
> but not finished. We could tidy that up and put more accurate links in.
>
> Simon
>
Just compiling up SCA (on a fresh Fedora Core 6 machine this time). A few
comments when following the instructions so far.

Builidng core SCA
Without Ant and JDK on the path the tools build fails



Yes. The scagen tool should really be part of the cpp extension and should
be moved in there after this release. I will change the build to only build
the tools is CPP extension is wanted.

Looking at the getting starter page. Not sure what to do once the core has

been built. I know from experience that I need to build a sample and,
before
this, build the appropriate extensions. But it's not obvious from the SCA
getting started page. Would be good to give an example of the very first
thing someone might like to try after buidling the core, e.g. now go build
the C++ extensions and try the CPPCalculator sample. Or is there some
other
test I should try to prove that the compile was successful?



Feel free to update the doc as you go along.

Tuscany SCA Extensions


Links don't work as doc is missing.



which links?

Samples

Small point - Could you extend the link highlighting from "getting
started"
to "samples getting started".



yes

Tuscany Samples - Getting Started


Samples Dependencies table 1.
Doc appears to be missing from the doc directory so links at top of table
don;t work
HTTPDBigBang link doesn't work
AlertAggregator link doesn't work

Just downloading a JDK so will let you know how I get on once done.

Simon





--
Pete

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:


Andrew Borley wrote:
> On 3/14/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>> I forgot to say what is new in this release!
>>
>> SDO C++ has a 30-40% performance improvement.
>> SCA Native has language support for C++, Python and Ruby, binding
>> support
>> for sca, webservices and rest plus samples to demonstrate these
>> bindings.
>>
>> Cheers,
>>
>>
>> On 14/03/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>> >
>> > I have posted a release candidate here:
>> > http://people.apache.org/~robbinspg/M3-RC1/
>> >
>> > Before starting a vote for this I would appreciate some folk trying
>> it out
>> > and reporting the silly errors that will require a vote to restart.
>> Please
>> > reply here with any problems (or success) you may have.
>> >
>> > Thank you.
>> >
>> > --
>> > Pete
>> >
>>
>
> I've just run RAT over the 6 packages and found & fixed a few files
> with missing Apache licenses (see r518120).
>
> I also found the following files that I'm not sure should be in the
> released packages:
> sdo/doc/CommittersGuide.txt
> sdo/doc/DesignNotes.htm
> sca/doc/CppGeneratorTool.txt
> These are all Tuscany developers documentation, not user docs.
>
> sdo/runtime/core/src/.cdtbuild
> sdo/runtime/core/src/.cdtproject
> sdo/runtime/core/src/.project
> These are Eclipse CDT project files - we don't have any docs to
> explain how to develop in or compile with EclipseCDT, so should these
> be in the SDO src package?
>
> Cheers
> Andy
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

The developer doc should be in the release IMO, the release is for users
and developers.

With respect to the CDT files under SDO, are they working? would they
help people if they wanted to load the SDO source in CDT? or would they
get in their way?

For SCA, I have been using CDT on Linux but have not checked the CDT
project files in SVN (I could do that if you wanted to have them in the
release).

Also, I've been following a slightly different scheme:
sca/.cdtproject
sca/samples/.cdtproject
as it allowed me to build from the top of the tree, but I can also
adjust to follow the SDO scheme if it makes it simpler for people to use
these files.

--
Jean-Sebastien



The CDT files are historical and should not have been checked in to SVN. We
shoudl remove them.


--
Pete

Re: Native M3 Release Candidate

[Jean-Sebastien Delfino]

Andrew Borley wrote:

On 3/14/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

I forgot to say what is new in this release!

SDO C++ has a 30-40% performance improvement.
SCA Native has language support for C++, Python and Ruby, binding 
support
for sca, webservices and rest plus samples to demonstrate these 
bindings.


Cheers,


On 14/03/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> I have posted a release candidate here:
> http://people.apache.org/~robbinspg/M3-RC1/
>
> Before starting a vote for this I would appreciate some folk trying 
it out
> and reporting the silly errors that will require a vote to restart. 
Please

> reply here with any problems (or success) you may have.
>
> Thank you.
>
> --
> Pete
>



I've just run RAT over the 6 packages and found & fixed a few files
with missing Apache licenses (see r518120).

I also found the following files that I'm not sure should be in the
released packages:
sdo/doc/CommittersGuide.txt
sdo/doc/DesignNotes.htm
sca/doc/CppGeneratorTool.txt
These are all Tuscany developers documentation, not user docs.

sdo/runtime/core/src/.cdtbuild
sdo/runtime/core/src/.cdtproject
sdo/runtime/core/src/.project
These are Eclipse CDT project files - we don't have any docs to
explain how to develop in or compile with EclipseCDT, so should these
be in the SDO src package?

Cheers
Andy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




The developer doc should be in the release IMO, the release is for users 
and developers.


With respect to the CDT files under SDO, are they working? would they 
help people if they wanted to load the SDO source in CDT? or would they 
get in their way?


For SCA, I have been using CDT on Linux but have not checked the CDT 
project files in SVN (I could do that if you wanted to have them in the 
release).


Also, I've been following a slightly different scheme:
sca/.cdtproject
sca/samples/.cdtproject
as it allowed me to build from the top of the tree, but I can also 
adjust to follow the SDO scheme if it makes it simpler for people to use 
these files.


--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 Release Candidate

[Simon Laws]

On 3/15/07, Simon Laws <[EMAIL PROTECTED]> wrote:




On 3/15/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> ant elder wrote:
> > I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking for
> that
> > but can't find a pre-compiled win32 version for that, so I tried
> > 2.6.23 and
> > using that the sample runs fine.
> >
> >   ...ant
> >
>
> Would it help to have on our Wiki a page with actual links to the
> (Windows) dependency downloads that people have been successful with?
> This way users won't have to fish for distributions of libxml for
> example that work for us.
>
> What do you think?
>
> --
> Jean-Sebastien
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> The getting started pages in the release have got dependency lists with
quite an amount of detail in but I like the idea  of having somewhere where
we can record the links to dependencies and update it with any funnies that
people find.  This page was started a while back  (
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+CPP+Dependencies)
but not finished. We could tidy that up and put more accurate links in.

Simon


Just compiling up SCA (on a fresh Fedora Core 6 machine this time). A few
comments when following the instructions so far.

Builidng core SCA
 Without Ant and JDK on the path the tools build fails

Looking at the getting starter page. Not sure what to do once the core has
been built. I know from experience that I need to build a sample and, before
this, build the appropriate extensions. But it's not obvious from the SCA
getting started page. Would be good to give an example of the very first
thing someone might like to try after buidling the core, e.g. now go build
the C++ extensions and try the CPPCalculator sample. Or is there some other
test I should try to prove that the compile was successful?

Tuscany SCA Extensions

Links don't work as doc is missing.

Samples
Small point - Could you extend the link highlighting from "getting started"
to "samples getting started".

Tuscany Samples - Getting Started

Samples Dependencies table 1.
Doc appears to be missing from the doc directory so links at top of table
don;t work
HTTPDBigBang link doesn't work
AlertAggregator link doesn't work

Just downloading a JDK so will let you know how I get on once done.

Simon

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, Simon Laws <[EMAIL PROTECTED]> wrote:


On 3/15/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> ant elder wrote:
> > I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking for
> that
> > but can't find a pre-compiled win32 version for that, so I tried
> > 2.6.23 and
> > using that the sample runs fine.
> >
> >   ...ant
> >
>
> Would it help to have on our Wiki a page with actual links to the
> (Windows) dependency downloads that people have been successful with?
> This way users won't have to fish for distributions of libxml for
> example that work for us.
>
> What do you think?
>
> --
> Jean-Sebastien
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> The getting started pages in the release have got dependency lists with
quite an amount of detail in but I like the idea  of having somewhere
where
we can record the links to dependencies and update it with any funnies
that
people find.  This page was started a while back  (
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+CPP+Dependencies)
but
not finished. We could tidy that up and put more accurate links in.

Simon



A good idea but not essential for this release. The dependencies are spelt
out in the doc as some folk complained when I origianally just had links to
where to get the pre-reqs. Some seem unable to read the instructions for
those pre-reqs and want them repeated in our doc (which is daft as they can
get out of date quite easily).

Cheers,

--
Pete

Re: Native M3 Release Candidate

[Simon Laws]

On 3/15/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:


ant elder wrote:
> I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking for
that
> but can't find a pre-compiled win32 version for that, so I tried
> 2.6.23 and
> using that the sample runs fine.
>
>   ...ant
>

Would it help to have on our Wiki a page with actual links to the
(Windows) dependency downloads that people have been successful with?
This way users won't have to fish for distributions of libxml for
example that work for us.

What do you think?

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

The getting started pages in the release have got dependency lists with

quite an amount of detail in but I like the idea  of having somewhere where
we can record the links to dependencies and update it with any funnies that
people find.  This page was started a while back  (
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+CPP+Dependencies) but
not finished. We could tidy that up and put more accurate links in.

Simon

Re: Native M3 Release Candidate

[Jean-Sebastien Delfino]

ant elder wrote:

I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking for that
but can't find a pre-compiled win32 version for that, so I tried 
2.6.23 and

using that the sample runs fine.

  ...ant



Would it help to have on our Wiki a page with actual links to the 
(Windows) dependency downloads that people have been successful with? 
This way users won't have to fish for distributions of libxml for 
example that work for us.


What do you think?

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 Release Candidate

[Pete Robbins]

On 15/03/07, haleh mahbod <[EMAIL PROTECTED]> wrote:


I noticed the following in the SDO getting started file:

1. Top of the file says: " If you haven't already done so, the first step
is
to download the SDO C++ Milestone release 2 of Apache Tuscany from our
download
page ."

2. The links for  FAQ and mailing list in the Getting help section are
pointing to the old site instead of Cwiki where everything is.  The same
links need to be fixed in the running samples file.

Thanks,
Haleh



Thanks for that. I'm fixing these.

Cheers,

On 3/14/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

>
> I've notice that building the samples on Mac installs them in
> sca/samples/samples. I'll look into this.
> --
> Pete
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>





--
Pete

Re: Native M3 Release Candidate

[haleh mahbod]

There are some good user guides/documents in the SCA  subproject. Can we
move these to the website? Is there a reason why these are not shared on the
website?

On 3/14/07, haleh mahbod <[EMAIL PROTECTED]> wrote:


I noticed the following in the SDO getting started file:

1. Top of the file says: " If you haven't already done so, the first step
is to download the SDO C++ Milestone release 2 of Apache Tuscany from our 
download
page ."

2. The links for  FAQ and mailing list in the Getting help section are
pointing to the old site instead of Cwiki where everything is.  The same
links need to be fixed in the running samples file.

Thanks,
Haleh


On 3/14/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> I've notice that building the samples on Mac installs them in
> sca/samples/samples. I'll look into this.
> --
> Pete
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Native M3 Release Candidate

[haleh mahbod]

I noticed the following in the SDO getting started file:

1. Top of the file says: " If you haven't already done so, the first step is
to download the SDO C++ Milestone release 2 of Apache Tuscany from our download
page ."

2. The links for  FAQ and mailing list in the Getting help section are
pointing to the old site instead of Cwiki where everything is.  The same
links need to be fixed in the running samples file.

Thanks,
Haleh


On 3/14/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


I've notice that building the samples on Mac installs them in
sca/samples/samples. I'll look into this.
--
Pete

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 Release Candidate

[Pete Robbins]

I've notice that building the samples on Mac installs them in
sca/samples/samples. I'll look into this.
--
Pete

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 Release Candidate

[Simon Laws]

On 3/14/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


On 14/03/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> I've just given this a try with the windows binary builds and following
> the
> getting started instructions to run the calculator sample.
>
> The first try failed as libxml2 and iconv are missing. I see now it does
> mention these in the SDO system prereqs section but a note pointing that
> out
> in the "Getting Tuscany SDO for C++ working with the binary release on
> Windows" would make this a bit clearer.


I've added some extra words for this.

Thanks for checking it out,

--
Pete



Pete

Have tried SDO on Fedora Core 5 and it compiled and ran according to the
GettingStarted instructions Have to go now but will try SCA also.

Simon

Re: Native M3 Release Candidate

[Pete Robbins]

On 14/03/07, ant elder <[EMAIL PROTECTED]> wrote:


I've just given this a try with the windows binary builds and following
the
getting started instructions to run the calculator sample.

The first try failed as libxml2 and iconv are missing. I see now it does
mention these in the SDO system prereqs section but a note pointing that
out
in the "Getting Tuscany SDO for C++ working with the binary release on
Windows" would make this a bit clearer.



I've added some extra words for this.

Thanks for checking it out,

--
Pete

Re: Native M3 Release Candidate

[ant elder]

I was using libxml2 2.6.27, seeing you had 2.6.24 i went looking for that
but can't find a pre-compiled win32 version for that, so I tried 2.6.23 and
using that the sample runs fine.

  ...ant

On 3/14/07, Andrew Borley <[EMAIL PROTECTED]> wrote:


Hi Ant,

This looks like it could be a libxml problem: do you have the libxml2,
iconv
and zlib libraries available on your path?
My path looks like the following:

/cygdrive/e/mingw/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:.:/cygdrive/d/tuscany/tuscany_sca_native-
1.0-incubator-M3-bin/bin:/cygdrive/d/tuscany/tuscany_sdo_cpp-
1.0-incubator-M3-bin/bin/:/cygdrive/d/libs/libxml2-2.6.24.win32
/bin/:/cygdrive/d/libs/zlib-1.2.3.win32/bin:/cygdrive/d/libs/iconv-
1.9.2.win32/bin

This is on cygwin, but you get the idea. With this path and TUSCANY_SCACPP
and TUSCANY_SDOCPP env variables set CppCalculator worked fine for me.

Let me know if that helps & I'll try to make the docs clearer.

Cheers
Andy



On 3/14/07, ant elder <[EMAIL PROTECTED]> wrote:
> I've just given this a try with the windows binary builds and following
the
> getting started instructions to run the calculator sample.
>
> The first try failed as libxml2 and iconv are missing. I see now it does
> mention these in the SDO system prereqs section but a note pointing that
out
> in the "Getting Tuscany SDO for C++ working with the binary release on
> Windows" would make this a bit clearer.
>
> Fixing that and now running the CppCalculator sample and it fails with
the
> error below. The sca.xsd does exist at that location but note in the
file
> path in the Description it uses some forward slashes which I'm guessing
is
> why it can't find the file on Windows.
>
>...ant
>
> C:\Tuscany\CPP\M3\tuscany_sca_native-
>
1.0-incubator-M3-bin\samples\CppCalculator\deploy\sample.calculator.client
>
> runclient.bat
> using SCA installed at \Tuscany\CPP\M3\tuscany_sca_native-
> 1.0-incubator-M3-bin
> using SDO installed at \Tuscany\CPP\M3\tuscany_sdo_cpp-
1.0-incubator-M3-bin
> calculator_client: exception caught: Exception
>  Class:   SDOFileNotFoundException
>  Description: \Tuscany\CPP\M3\tuscany_sca_native-
1.0-incubator-M3-bin
> /xsd/sca.xsd
>  Origin:
>File:
> ..\..\..\runtime\core\src\commonj\sdo\SDOSchemaSAX2Parser.cpp
>Line:551
>Function:"parseIfNot"
>  Path:
>File:
> ..\..\..\runtime\core\src\tuscany\sca\model\ModelLoader.cpp
>Line:  898
>Function:  tuscany::sca::model::ModelLoader::getXSDHelper
>File:
> ..\..\..\runtime\extensions\cpp\src\osoa\sca\CompositeContext.cpp
>Line:  101
>Function:  osoa::sca::CompositeContext::getCurrent
>
>...ant
>
> On 3/14/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >
> > I have posted a release candidate here:
> > http://people.apache.org/~robbinspg/M3-RC1/
> >
> > Before starting a vote for this I would appreciate some folk trying it
out
> > and reporting the silly errors that will require a vote to restart.
Please
> > reply here with any problems (or success) you may have.
> >
> > Thank you.
> >
> > --
> > Pete
> >
>

Re: Native M3 Release Candidate

[Andrew Borley]

Hi Ant,

This looks like it could be a libxml problem: do you have the libxml2, iconv
and zlib libraries available on your path?
My path looks like the following:
/cygdrive/e/mingw/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:.:/cygdrive/d/tuscany/tuscany_sca_native-
1.0-incubator-M3-bin/bin:/cygdrive/d/tuscany/tuscany_sdo_cpp-
1.0-incubator-M3-bin/bin/:/cygdrive/d/libs/libxml2-2.6.24.win32
/bin/:/cygdrive/d/libs/zlib-1.2.3.win32/bin:/cygdrive/d/libs/iconv-
1.9.2.win32/bin

This is on cygwin, but you get the idea. With this path and TUSCANY_SCACPP
and TUSCANY_SDOCPP env variables set CppCalculator worked fine for me.

Let me know if that helps & I'll try to make the docs clearer.

Cheers
Andy



On 3/14/07, ant elder <[EMAIL PROTECTED]> wrote:

I've just given this a try with the windows binary builds and following

the

getting started instructions to run the calculator sample.

The first try failed as libxml2 and iconv are missing. I see now it does
mention these in the SDO system prereqs section but a note pointing that

out

in the "Getting Tuscany SDO for C++ working with the binary release on
Windows" would make this a bit clearer.

Fixing that and now running the CppCalculator sample and it fails with the
error below. The sca.xsd does exist at that location but note in the file
path in the Description it uses some forward slashes which I'm guessing is
why it can't find the file on Windows.

   ...ant

C:\Tuscany\CPP\M3\tuscany_sca_native-
1.0-incubator-M3-bin\samples\CppCalculator\deploy\sample.calculator.client

runclient.bat
using SCA installed at \Tuscany\CPP\M3\tuscany_sca_native-
1.0-incubator-M3-bin
using SDO installed at \Tuscany\CPP\M3\tuscany_sdo_cpp-

1.0-incubator-M3-bin

calculator_client: exception caught: Exception
 Class:   SDOFileNotFoundException
 Description: \Tuscany\CPP\M3\tuscany_sca_native-1.0-incubator-M3-bin
/xsd/sca.xsd
 Origin:
   File:
..\..\..\runtime\core\src\commonj\sdo\SDOSchemaSAX2Parser.cpp
   Line:551
   Function:"parseIfNot"
 Path:
   File:
..\..\..\runtime\core\src\tuscany\sca\model\ModelLoader.cpp
   Line:  898
   Function:  tuscany::sca::model::ModelLoader::getXSDHelper
   File:
..\..\..\runtime\extensions\cpp\src\osoa\sca\CompositeContext.cpp
   Line:  101
   Function:  osoa::sca::CompositeContext::getCurrent

   ...ant

On 3/14/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> I have posted a release candidate here:
> http://people.apache.org/~robbinspg/M3-RC1/
>
> Before starting a vote for this I would appreciate some folk trying it

out

> and reporting the silly errors that will require a vote to restart.

Please

> reply here with any problems (or success) you may have.
>
> Thank you.
>
> --
> Pete
>

Re: Native M3 Release Candidate

[Andrew Borley]

On 3/14/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

I forgot to say what is new in this release!

SDO C++ has a 30-40% performance improvement.
SCA Native has language support for C++, Python and Ruby, binding support
for sca, webservices and rest plus samples to demonstrate these bindings.

Cheers,


On 14/03/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> I have posted a release candidate here:
> http://people.apache.org/~robbinspg/M3-RC1/
>
> Before starting a vote for this I would appreciate some folk trying it out
> and reporting the silly errors that will require a vote to restart. Please
> reply here with any problems (or success) you may have.
>
> Thank you.
>
> --
> Pete
>



I've just run RAT over the 6 packages and found & fixed a few files
with missing Apache licenses (see r518120).

I also found the following files that I'm not sure should be in the
released packages:
sdo/doc/CommittersGuide.txt
sdo/doc/DesignNotes.htm
sca/doc/CppGeneratorTool.txt
These are all Tuscany developers documentation, not user docs.

sdo/runtime/core/src/.cdtbuild
sdo/runtime/core/src/.cdtproject
sdo/runtime/core/src/.project
These are Eclipse CDT project files - we don't have any docs to
explain how to develop in or compile with EclipseCDT, so should these
be in the SDO src package?

Cheers
Andy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 Release Candidate

[ant elder]

I've just given this a try with the windows binary builds and following the
getting started instructions to run the calculator sample.

The first try failed as libxml2 and iconv are missing. I see now it does
mention these in the SDO system prereqs section but a note pointing that out
in the "Getting Tuscany SDO for C++ working with the binary release on
Windows" would make this a bit clearer.

Fixing that and now running the CppCalculator sample and it fails with the
error below. The sca.xsd does exist at that location but note in the file
path in the Description it uses some forward slashes which I'm guessing is
why it can't find the file on Windows.

  ...ant

C:\Tuscany\CPP\M3\tuscany_sca_native-
1.0-incubator-M3-bin\samples\CppCalculator\deploy\sample.calculator.client>
runclient.bat
using SCA installed at \Tuscany\CPP\M3\tuscany_sca_native-
1.0-incubator-M3-bin
using SDO installed at \Tuscany\CPP\M3\tuscany_sdo_cpp-1.0-incubator-M3-bin
calculator_client: exception caught: Exception
Class:   SDOFileNotFoundException
Description: \Tuscany\CPP\M3\tuscany_sca_native-1.0-incubator-M3-bin
/xsd/sca.xsd
Origin:
  File:
..\..\..\runtime\core\src\commonj\sdo\SDOSchemaSAX2Parser.cpp
  Line:551
  Function:"parseIfNot"
Path:
  File:
..\..\..\runtime\core\src\tuscany\sca\model\ModelLoader.cpp
  Line:  898
  Function:  tuscany::sca::model::ModelLoader::getXSDHelper
  File:
..\..\..\runtime\extensions\cpp\src\osoa\sca\CompositeContext.cpp
  Line:  101
  Function:  osoa::sca::CompositeContext::getCurrent

  ...ant

On 3/14/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


I have posted a release candidate here:
http://people.apache.org/~robbinspg/M3-RC1/

Before starting a vote for this I would appreciate some folk trying it out
and reporting the silly errors that will require a vote to restart. Please
reply here with any problems (or success) you may have.

Thank you.

--
Pete

Re: Native M3 Release Candidate

[Pete Robbins]

I forgot to say what is new in this release!

SDO C++ has a 30-40% performance improvement.
SCA Native has language support for C++, Python and Ruby, binding support
for sca, webservices and rest plus samples to demonstrate these bindings.

Cheers,


On 14/03/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


I have posted a release candidate here:
http://people.apache.org/~robbinspg/M3-RC1/

Before starting a vote for this I would appreciate some folk trying it out
and reporting the silly errors that will require a vote to restart. Please
reply here with any problems (or success) you may have.

Thank you.

--
Pete





--
Pete

Native M3 Release Candidate

[Pete Robbins]

I have posted a release candidate here:
http://people.apache.org/~robbinspg/M3-RC1/

Before starting a vote for this I would appreciate some folk trying it out
and reporting the silly errors that will require a vote to restart. Please
reply here with any problems (or success) you may have.

Thank you.

--
Pete

Re: Native M3 release status

[Pete Robbins]

On 13/03/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:


Pete Robbins wrote:
> Just a quick update.
>
> The doc is in order now (thanks Andy) and the distros are ok on
> Linux/Mac.
> I'm having to rework the source distro for Windows as there were some
> errors
> in the build settings. A few more minor changes to the build script to
> make
> the extensions optional and I'll be done.
>
> Cheers,
>

Cool. I just refreshed and it built OK on Linux, except that the PHP
extension was not built at all even after doing configure
--enable-all-extensions. It does not seem to be built by build.sh either
but I guess it's ok... I'm assuming that you're not going to include the
PHP extension in the release yet?

One minor thing, extensions/ws/service/deploy.sh didn't work for me, the
script looks for $APFULLDIR/modules/tuscany/module.xml which does not
exist.



This looks like I've made a typo in the Makefile.am. I have module_DATA
instead of modules_DATA.


I've tested the command line and REST samples and they worked.


I can help test your release candidate on Linux when it's ready.

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Pete

Re: Native M3 release status

[Pete Robbins]

On 13/03/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:


Pete Robbins wrote:
> Just a quick update.
>
> The doc is in order now (thanks Andy) and the distros are ok on
> Linux/Mac.
> I'm having to rework the source distro for Windows as there were some
> errors
> in the build settings. A few more minor changes to the build script to
> make
> the extensions optional and I'll be done.
>
> Cheers,
>

Cool. I just refreshed and it built OK on Linux, except that the PHP
extension was not built at all even after doing configure
--enable-all-extensions. It does not seem to be built by build.sh either
but I guess it's ok... I'm assuming that you're not going to include the
PHP extension in the release yet?

One minor thing, extensions/ws/service/deploy.sh didn't work for me, the
script looks for $APFULLDIR/modules/tuscany/module.xml which does not
exist.

I've tested the command line and REST samples and they worked.

I can help test your release candidate on Linux when it's ready.

--
Jean-Sebastien




PHP is not included in the main build anymore. To build it you go to
sca/runtime/extensions/php and run build.sh. It has it's own autoconf/make
so this does a configure/make/make install triple. It will get deployed into
wherever $TUSCANY_SCACPP is set to.

I'll look in to the ws deploy problem

Thanks for your help.


--
Pete

Re: Native M3 release status

[Jean-Sebastien Delfino]

Pete Robbins wrote:

Just a quick update.

The doc is in order now (thanks Andy) and the distros are ok on 
Linux/Mac.
I'm having to rework the source distro for Windows as there were some 
errors
in the build settings. A few more minor changes to the build script to 
make

the extensions optional and I'll be done.

Cheers,



Cool. I just refreshed and it built OK on Linux, except that the PHP 
extension was not built at all even after doing configure 
--enable-all-extensions. It does not seem to be built by build.sh either 
but I guess it's ok... I'm assuming that you're not going to include the 
PHP extension in the release yet?


One minor thing, extensions/ws/service/deploy.sh didn't work for me, the 
script looks for $APFULLDIR/modules/tuscany/module.xml which does not exist.


I've tested the command line and REST samples and they worked.

I can help test your release candidate on Linux when it's ready.

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Pete Robbins]

Just a quick update.

The doc is in order now (thanks Andy) and the distros are ok on Linux/Mac.
I'm having to rework the source distro for Windows as there were some errors
in the build settings. A few more minor changes to the build script to make
the extensions optional and I'll be done.

Cheers,

--
Pete

Re: Native M3 release status

[Pete Robbins]

On 06/03/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:


[snip]
Andrew Borley wrote:
> On 3/2/07, Pete Robbins < [EMAIL PROTECTED]> wrote:
>>
>>
>> I can now build the PHP extension and a distro of it's source/binaries
>> separate from the rest of the release (at leat on Linux for now). I
have
>> some other questions on how we should package the release.
>>
>> 1) Should we produce a source and binary download for core and each
>> extension? This would produce many download files but would improve the

>> modularity and flexibility of future releases. e.g. if the Ruby
>> extension
>> gets a major update there is no need to package, release and test the
>> other
>> extensions.
>
>
> I think this is the second time around this loop! I'm happy to go with
> the "separate artifacts" plan for the reasons you mention in 1) above,
> albeit with the reduced simplicity that you get with a single download
> package. Perhaps in the future an installer system could be used that
> allows users to get the kernel & the extensions they require.
>
>> 2) If we do 1) where should the samples go? I think the samples should
>> belong to the extension that they are demonstrating. This means the
>> language
>> samples xxxCalculator would be packaged with their extension. THe REST
>> samples would be in the REST extension (though they would pre-req a
>> language
>> binding e.g. Python). etc.. An alternative would be to package the
>> samples
>> separately.
>
> My feeling is that the samples should come with the appropriate
> extension. I'd propose:
> tuscany_sca_cpp - CppCalculator
> tuscany_sca_ruby - RubyCalculator
> tuscany_sca_python - PythonCalculator
> tuscany_sca_ws - CppBigBank, RubyBigBank, PythonWeatherForecast
> tuscany_sca_binding - HTTPDBigBank
> tuscany_sca_rest - RestCalculator, RestCustomer, RestYahoo,
> AlertAggregator
>
> Does that make sense? The WS, REST and SCA binding samples all require
> a language extension, but users will need at least one language
> extension anyway if they want to do any work with Tuscany!
>

SCA is mainly about assembly, so most useful samples will assemble
components with dependencies on different extensions (WS, REST,
different scripting languages) and it's going to be difficult to package
them with individual extensions, or if we really want to do that we'll
have to cut the samples in small chunks and IMO they won't be very
interesting anymore.

>
>> 3) Does anyone ever download the Linux binary release? In my
>> experience the
>> download source/build/install model is  used for the vast majority of
>> Linux
>> projects. We only produce a binary for a single Linux anyway so
>> unless you
>> are using RHEL3 you need to go via the source. It may make sense to
>> have a
>> Mac binary download but again this would be for Mac OS X Intel so of
>> no use
>> o the PPC Macs.
>
> This is a very valid point! I think we can drop the non-windows
binaries.

+1

>
>> I would like to implement 1) and have a 3 downloads per extension:
>> Linux/Mac
>> source, Windows source, Windows binary.
>> Samples would be included with the relevant extensions.
>> The extensions would be:
>>
>> tuscany_sca - the core
>> tuscany_sca_cpp - C++ language binding
>> tuscany_sca_ruby - Ruby language binding
>> tuscany_sca_python - Python language binding
>> tuscany_sca_ws - Axis2c webservices binding
>> tuscany_sca_binding - sca binding (based on ws binding)
>> tuscany_sca_rest - rest binding
>>
>> 3 download artifacts for each.
>
> +1 I think it makes it nice and obvious what technologies are supported.


If you do that, can we keep a single download as well? I'm concerned
about the complexity that we are introducing here by releasing many more
small packages and asking the user to put the puzzle together.

I like the user experience I get with PHP, Python, Ruby, Apache Httpd or
Spring for example. One download, unzip, build, run...
- on Linux, one source distribution, then the configure tool can be used
to build a subset or even better it only builds what can be built with
the dependencies available in your environment
- on Windows, one binary distribution, function gets activated or not
depending on the presence of the required dependencies (for example the
PHP support gets activated if you have a PHP runtime available)

>
> Cheers
> Andy
> In regards to 3
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



For this (eventual) release I will be leaving everything in one download. If
I can get the PHP extension working then that can be included as well. If I
don't get the PHP into an acceptable shape soon I  will release a package
that contains no PHP and that can be released at a later date. This separat

Re: Native M3 release status

[Jean-Sebastien Delfino]

[snip]
Andrew Borley wrote:

On 3/2/07, Pete Robbins <[EMAIL PROTECTED]> wrote:



I can now build the PHP extension and a distro of it's source/binaries
separate from the rest of the release (at leat on Linux for now). I have
some other questions on how we should package the release.

1) Should we produce a source and binary download for core and each
extension? This would produce many download files but would improve the
modularity and flexibility of future releases. e.g. if the Ruby 
extension
gets a major update there is no need to package, release and test the 
other

extensions.



I think this is the second time around this loop! I'm happy to go with
the "separate artifacts" plan for the reasons you mention in 1) above,
albeit with the reduced simplicity that you get with a single download
package. Perhaps in the future an installer system could be used that
allows users to get the kernel & the extensions they require.


2) If we do 1) where should the samples go? I think the samples should
belong to the extension that they are demonstrating. This means the 
language

samples xxxCalculator would be packaged with their extension. THe REST
samples would be in the REST extension (though they would pre-req a 
language
binding e.g. Python). etc.. An alternative would be to package the 
samples

separately.


My feeling is that the samples should come with the appropriate
extension. I'd propose:
tuscany_sca_cpp - CppCalculator
tuscany_sca_ruby - RubyCalculator
tuscany_sca_python - PythonCalculator
tuscany_sca_ws - CppBigBank, RubyBigBank, PythonWeatherForecast
tuscany_sca_binding - HTTPDBigBank
tuscany_sca_rest - RestCalculator, RestCustomer, RestYahoo, 
AlertAggregator


Does that make sense? The WS, REST and SCA binding samples all require
a language extension, but users will need at least one language
extension anyway if they want to do any work with Tuscany!



SCA is mainly about assembly, so most useful samples will assemble 
components with dependencies on different extensions (WS, REST, 
different scripting languages) and it's going to be difficult to package 
them with individual extensions, or if we really want to do that we'll 
have to cut the samples in small chunks and IMO they won't be very 
interesting anymore.




3) Does anyone ever download the Linux binary release? In my 
experience the
download source/build/install model is  used for the vast majority of 
Linux
projects. We only produce a binary for a single Linux anyway so 
unless you
are using RHEL3 you need to go via the source. It may make sense to 
have a
Mac binary download but again this would be for Mac OS X Intel so of 
no use

o the PPC Macs.


This is a very valid point! I think we can drop the non-windows binaries.


+1



I would like to implement 1) and have a 3 downloads per extension: 
Linux/Mac

source, Windows source, Windows binary.
Samples would be included with the relevant extensions.
The extensions would be:

tuscany_sca - the core
tuscany_sca_cpp - C++ language binding
tuscany_sca_ruby - Ruby language binding
tuscany_sca_python - Python language binding
tuscany_sca_ws - Axis2c webservices binding
tuscany_sca_binding - sca binding (based on ws binding)
tuscany_sca_rest - rest binding

3 download artifacts for each.


+1 I think it makes it nice and obvious what technologies are supported.


If you do that, can we keep a single download as well? I'm concerned 
about the complexity that we are introducing here by releasing many more 
small packages and asking the user to put the puzzle together.


I like the user experience I get with PHP, Python, Ruby, Apache Httpd or 
Spring for example. One download, unzip, build, run...
- on Linux, one source distribution, then the configure tool can be used 
to build a subset or even better it only builds what can be built with 
the dependencies available in your environment
- on Windows, one binary distribution, function gets activated or not 
depending on the presence of the required dependencies (for example the 
PHP support gets activated if you have a PHP runtime available)




Cheers
Andy
In regards to 3

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Andrew Borley]

On 3/2/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

On 01/03/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
>
> On 3/1/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> > Andrew Borley wrote:
> > > On 3/1/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > >> I'm just about at a point where  I can produce a release candidate
> which
> > >> includes everything except the PHP extension. I'm wondering if it
> > >> would be
> > >> best to publish this then release the PHP extension as a separate
> > >> entity. We
> > >> could go the whole hog and release a core package and then separate
> > >> packages
> > >> for cpp, Ruby, Python, WS binding etc..
> > >>
> > >> Ultimately I think this is the way to go So If I just want to develop
> in
> > >> Ruby and use REST I can download core, Ruby and Rest extensions and
> not
> > >> worry about the others, and more impoortantly, their dependencies.
> > >>
> > >> Any thoughts?
> > >
> > > +1 from me. I've had some experience of building the PHP extension and
> > > it's quite a process - you need to build PHP with the right flags,
> > > then download and build a particular branch of the PECL SCA_SDO
> > > package and then you can build the Tuscany PHP extension! (see [1])
> > > It may be worth waiting until the AVOCET branch of the SCA_SDO package
> > > becomes the main downloadable package from the PECL site - I believe
> > > this is the plan for the next SCA_SDO release. This (I think) will
> > > remove (or at least vastly simplify) the first 2 steps in the above
> > > process.
> > >
> > > Cheers
> > > Andy
> > >
> > > [1]
> > >
> 
http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/runtime/extensions/php/README
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > +1 from me.
> >
> > If I understand correctly then the Tuscany PHP extension will work with
> > an actual release of the PECL SCA_SDO package. Correct?
> >
>
> Not with the current release of the PECL SCA_SDO package (1.1.2), but
> it will with the next release, which will be based on the AVOCET
> branch that the Tuscany PHP extension depends on.
>
> Cheers
> Andy


I can now build the PHP extension and a distro of it's source/binaries
separate from the rest of the release (at leat on Linux for now). I have
some other questions on how we should package the release.

1) Should we produce a source and binary download for core and each
extension? This would produce many download files but would improve the
modularity and flexibility of future releases. e.g. if the Ruby extension
gets a major update there is no need to package, release and test the other
extensions.



I think this is the second time around this loop! I'm happy to go with
the "separate artifacts" plan for the reasons you mention in 1) above,
albeit with the reduced simplicity that you get with a single download
package. Perhaps in the future an installer system could be used that
allows users to get the kernel & the extensions they require.


2) If we do 1) where should the samples go? I think the samples should
belong to the extension that they are demonstrating. This means the language
samples xxxCalculator would be packaged with their extension. THe REST
samples would be in the REST extension (though they would pre-req a language
binding e.g. Python). etc.. An alternative would be to package the samples
separately.


My feeling is that the samples should come with the appropriate
extension. I'd propose:
tuscany_sca_cpp - CppCalculator
tuscany_sca_ruby - RubyCalculator
tuscany_sca_python - PythonCalculator
tuscany_sca_ws - CppBigBank, RubyBigBank, PythonWeatherForecast
tuscany_sca_binding - HTTPDBigBank
tuscany_sca_rest - RestCalculator, RestCustomer, RestYahoo, AlertAggregator

Does that make sense? The WS, REST and SCA binding samples all require
a language extension, but users will need at least one language
extension anyway if they want to do any work with Tuscany!



3) Does anyone ever download the Linux binary release? In my experience the
download source/build/install model is  used for the vast majority of Linux
projects. We only produce a binary for a single Linux anyway so unless you
are using RHEL3 you need to go via the source. It may make sense to have a
Mac binary download but again this would be for Mac OS X Intel so of no use
o the PPC Macs.


This is a very valid point! I think we can drop the non-windows binaries.


I would like to implement 1) and have a 3 downloads per extension: Linux/Mac
source, Windows source, Windows binary.
Samples would be included with the relevant extensions.
The extensions would be:

tuscany_sca - the core
tuscany_sca_cpp - C++ language binding
tuscany_sca_ruby - Ruby language binding
tuscany_sca_python - Python language binding
tuscany_sca_ws - Axis2c webservices binding
tuscany_sca_binding - sca binding (based on ws binding)
tuscany_s

Re: Native M3 release status

[Pete Robbins]

On 01/03/07, Andrew Borley <[EMAIL PROTECTED]> wrote:


On 3/1/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> Andrew Borley wrote:
> > On 3/1/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >> I'm just about at a point where  I can produce a release candidate
which
> >> includes everything except the PHP extension. I'm wondering if it
> >> would be
> >> best to publish this then release the PHP extension as a separate
> >> entity. We
> >> could go the whole hog and release a core package and then separate
> >> packages
> >> for cpp, Ruby, Python, WS binding etc..
> >>
> >> Ultimately I think this is the way to go So If I just want to develop
in
> >> Ruby and use REST I can download core, Ruby and Rest extensions and
not
> >> worry about the others, and more impoortantly, their dependencies.
> >>
> >> Any thoughts?
> >
> > +1 from me. I've had some experience of building the PHP extension and
> > it's quite a process - you need to build PHP with the right flags,
> > then download and build a particular branch of the PECL SCA_SDO
> > package and then you can build the Tuscany PHP extension! (see [1])
> > It may be worth waiting until the AVOCET branch of the SCA_SDO package
> > becomes the main downloadable package from the PECL site - I believe
> > this is the plan for the next SCA_SDO release. This (I think) will
> > remove (or at least vastly simplify) the first 2 steps in the above
> > process.
> >
> > Cheers
> > Andy
> >
> > [1]
> >
http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/runtime/extensions/php/README
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> +1 from me.
>
> If I understand correctly then the Tuscany PHP extension will work with
> an actual release of the PECL SCA_SDO package. Correct?
>

Not with the current release of the PECL SCA_SDO package (1.1.2), but
it will with the next release, which will be based on the AVOCET
branch that the Tuscany PHP extension depends on.

Cheers
Andy



I can now build the PHP extension and a distro of it's source/binaries
separate from the rest of the release (at leat on Linux for now). I have
some other questions on how we should package the release.

1) Should we produce a source and binary download for core and each
extension? This would produce many download files but would improve the
modularity and flexibility of future releases. e.g. if the Ruby extension
gets a major update there is no need to package, release and test the other
extensions.

2) If we do 1) where should the samples go? I think the samples should
belong to the extension that they are demonstrating. This means the language
samples xxxCalculator would be packaged with their extension. THe REST
samples would be in the REST extension (though they would pre-req a language
binding e.g. Python). etc.. An alternative would be to package the samples
separately.

3) Does anyone ever download the Linux binary release? In my experience the
download source/build/install model is  used for the vast majority of Linux
projects. We only produce a binary for a single Linux anyway so unless you
are using RHEL3 you need to go via the source. It may make sense to have a
Mac binary download but again this would be for Mac OS X Intel so of no use
o the PPC Macs.

I would like to implement 1) and have a 3 downloads per extension: Linux/Mac
source, Windows source, Windows binary.
Samples would be included with the relevant extensions.
The extensions would be:

tuscany_sca - the core
tuscany_sca_cpp - C++ language binding
tuscany_sca_ruby - Ruby language binding
tuscany_sca_python - Python language binding
tuscany_sca_ws - Axis2c webservices binding
tuscany_sca_binding - sca binding (based on ws binding)
tuscany_sca_rest - rest binding

3 download artifacts for each.

Cheers,

--
Pete

Re: Native M3 release status

[Andrew Borley]

On 3/1/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:

Andrew Borley wrote:
> On 3/1/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>> I'm just about at a point where  I can produce a release candidate which
>> includes everything except the PHP extension. I'm wondering if it
>> would be
>> best to publish this then release the PHP extension as a separate
>> entity. We
>> could go the whole hog and release a core package and then separate
>> packages
>> for cpp, Ruby, Python, WS binding etc..
>>
>> Ultimately I think this is the way to go So If I just want to develop in
>> Ruby and use REST I can download core, Ruby and Rest extensions and not
>> worry about the others, and more impoortantly, their dependencies.
>>
>> Any thoughts?
>
> +1 from me. I've had some experience of building the PHP extension and
> it's quite a process - you need to build PHP with the right flags,
> then download and build a particular branch of the PECL SCA_SDO
> package and then you can build the Tuscany PHP extension! (see [1])
> It may be worth waiting until the AVOCET branch of the SCA_SDO package
> becomes the main downloadable package from the PECL site - I believe
> this is the plan for the next SCA_SDO release. This (I think) will
> remove (or at least vastly simplify) the first 2 steps in the above
> process.
>
> Cheers
> Andy
>
> [1]
> 
http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/runtime/extensions/php/README
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

+1 from me.

If I understand correctly then the Tuscany PHP extension will work with
an actual release of the PECL SCA_SDO package. Correct?



Not with the current release of the PECL SCA_SDO package (1.1.2), but
it will with the next release, which will be based on the AVOCET
branch that the Tuscany PHP extension depends on.

Cheers
Andy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Jean-Sebastien Delfino]

Andrew Borley wrote:

On 3/1/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

I'm just about at a point where  I can produce a release candidate which
includes everything except the PHP extension. I'm wondering if it 
would be
best to publish this then release the PHP extension as a separate 
entity. We
could go the whole hog and release a core package and then separate 
packages

for cpp, Ruby, Python, WS binding etc..

Ultimately I think this is the way to go So If I just want to develop in
Ruby and use REST I can download core, Ruby and Rest extensions and not
worry about the others, and more impoortantly, their dependencies.

Any thoughts?


+1 from me. I've had some experience of building the PHP extension and
it's quite a process - you need to build PHP with the right flags,
then download and build a particular branch of the PECL SCA_SDO
package and then you can build the Tuscany PHP extension! (see [1])
It may be worth waiting until the AVOCET branch of the SCA_SDO package
becomes the main downloadable package from the PECL site - I believe
this is the plan for the next SCA_SDO release. This (I think) will
remove (or at least vastly simplify) the first 2 steps in the above
process.

Cheers
Andy

[1] 
http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/runtime/extensions/php/README 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




+1 from me.

If I understand correctly then the Tuscany PHP extension will work with 
an actual release of the PECL SCA_SDO package. Correct?


--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Andrew Borley]

On 3/1/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

I'm just about at a point where  I can produce a release candidate which
includes everything except the PHP extension. I'm wondering if it would be
best to publish this then release the PHP extension as a separate entity. We
could go the whole hog and release a core package and then separate packages
for cpp, Ruby, Python, WS binding etc..

Ultimately I think this is the way to go So If I just want to develop in
Ruby and use REST I can download core, Ruby and Rest extensions and not
worry about the others, and more impoortantly, their dependencies.

Any thoughts?


+1 from me. I've had some experience of building the PHP extension and
it's quite a process - you need to build PHP with the right flags,
then download and build a particular branch of the PECL SCA_SDO
package and then you can build the Tuscany PHP extension! (see [1])
It may be worth waiting until the AVOCET branch of the SCA_SDO package
becomes the main downloadable package from the PECL site - I believe
this is the plan for the next SCA_SDO release. This (I think) will
remove (or at least vastly simplify) the first 2 steps in the above
process.

Cheers
Andy

[1] 
http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/runtime/extensions/php/README

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Pete Robbins]

I'm just about at a point where  I can produce a release candidate which
includes everything except the PHP extension. I'm wondering if it would be
best to publish this then release the PHP extension as a separate entity. We
could go the whole hog and release a core package and then separate packages
for cpp, Ruby, Python, WS binding etc..

Ultimately I think this is the way to go So If I just want to develop in
Ruby and use REST I can download core, Ruby and Rest extensions and not
worry about the others, and more impoortantly, their dependencies.

Any thoughts?

--
Pete

Re: Native M3 release status

[Simon Laws]

On 2/28/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


On 28/02/07, Simon Laws <[EMAIL PROTECTED]> wrote:
>
> On 2/28/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >
> > I think we have resolved the issues with the Python samples when mixed
> > with
> > Ruby and/or httpd so we have:
> >
> > Windows/Linux : core, cpp, ruby, python, ws, rest, sca
> > Mac: core, cpp, ruby, python, rest
> >
> > Tomorrow I will try and integrate the PHP extension into the
> distribution
> > and hopefully get a release candidate out this week.
> >
> > Cheers,
> >
> Hi Pete,
>
> What was the fix? I'm wondering whether it could also be applied to fix
> our
> lingering PHP extension linux build problem.
>
> Simon
>

It was a mismatch in the expat library that Python includes and the one
that
Ruby or httpd use. To fix this we use LD_PRELOAD=
before invoking Ruby (or starting httpd). This pulls in the expat that
Python insists on and the other components are happy using that version.

Cheers,

--
Pete


Ok, thanks Pete. So maybe not a solution for PHP but interesting none the
less.

Regards

Simon

Re: Native M3 release status

[Pete Robbins]

On 28/02/07, Simon Laws <[EMAIL PROTECTED]> wrote:


On 2/28/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> I think we have resolved the issues with the Python samples when mixed
> with
> Ruby and/or httpd so we have:
>
> Windows/Linux : core, cpp, ruby, python, ws, rest, sca
> Mac: core, cpp, ruby, python, rest
>
> Tomorrow I will try and integrate the PHP extension into the
distribution
> and hopefully get a release candidate out this week.
>
> Cheers,
>
Hi Pete,

What was the fix? I'm wondering whether it could also be applied to fix
our
lingering PHP extension linux build problem.

Simon



It was a mismatch in the expat library that Python includes and the one that
Ruby or httpd use. To fix this we use LD_PRELOAD=
before invoking Ruby (or starting httpd). This pulls in the expat that
Python insists on and the other components are happy using that version.

Cheers,

--
Pete

Re: Native M3 release status

[Simon Laws]

On 2/28/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


I think we have resolved the issues with the Python samples when mixed
with
Ruby and/or httpd so we have:

Windows/Linux : core, cpp, ruby, python, ws, rest, sca
Mac: core, cpp, ruby, python, rest

Tomorrow I will try and integrate the PHP extension into the distribution
and hopefully get a release candidate out this week.

Cheers,


Hi Pete,

What was the fix? I'm wondering whether it could also be applied to fix our
lingering PHP extension linux build problem.

Simon

Re: Native M3 release status

[Pete Robbins]

I think we have resolved the issues with the Python samples when mixed with
Ruby and/or httpd so we have:

Windows/Linux : core, cpp, ruby, python, ws, rest, sca
Mac: core, cpp, ruby, python, rest

Tomorrow I will try and integrate the PHP extension into the distribution
and hopefully get a release candidate out this week.

Cheers,

Re: Native M3 release status

[Simon Laws]

On 2/28/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:


Pete Robbins wrote:
> On 22/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>>  On 22/02/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>> >
>> > Pete Robbins wrote:
>> > > On 22/02/07, Andrew Borley <[EMAIL PROTECTED] > wrote:
>> > >>
>> > >> On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>> > >> > On 21/02/07, Andrew Borley < [EMAIL PROTECTED]> wrote:
>> > >> > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>> > >> > > > On 21/02/07, Andrew Borley < [EMAIL PROTECTED]> wrote:
>> > >> > > > >
>> > >> > > > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED] >
wrote:
>> > >> > > > > > I now have Ruby working on Mac. I will remove the ws
>> > bindings
>> > >> and
>> > >> > > > > clients
>> > >> > > > > > from the *Calculator samples so we have a simple
>> sample for
>> >
>> > >> each
>> > >> > > > > language.
>> > >> > > > > > $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to
>> > the
>> > >> > > > > LD_LIBRARY_PATH
>> > >> > > > > > (or PATH on windows) to run the Ruby clients. I've
>> updated
>> > the
>> > >> runclient
>> > >> > > > > > scripts.
>> > >> > > > >
>> > >> > > > > Running a Linux build against the latest code gives me an
>> > error
>> > >> with
>> > >> > > > > the new Ruby layout:
>> > >> > > > >
>> > >> > > > > make[5]: Entering directory
>> > >> > > > >
>> > >> > > > >
>> > >>
>> >
>>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
>>
>> >
>> > >>
>> > >> > > > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
>> > >> -fexceptions
>> > >> > > > > -fstack-protector --param=ssp-buffer-size=4 -m32
>> -march=i386
>> > >> > > > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC
>> > -I.
>> > >> > > > > -I/usr/lib/ruby/1.8/i386-linux
>> -I/usr/lib/ruby/1.8/i386-linux
>> > >> -I.   -c
>> > >> > > > > Extension.cpp
>> > >> > > > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No
>> such
>> > >> file
>> > >> or
>> > >> > > > > directory
>> > >> > > > > Extension.cpp:29:51: error:
>> > >> tuscany/sca/ruby/RubyCompositeContext.h:
>> > >> > > > > No such file or directory
>> > >> > > > >
>> > >> > > > > Did everything get checked in? Am I missing an env
>> variable?
>> > >> > > >
>> > >> > > >
>> > >> > > > Everything is checked in. The extconf.rb RUby script
>> generates
>> > the
>> > >> makefile.
>> > >> > > > It should add the lib and include paths nexessary. Are there
>> > >> messages before
>> > >> > > > the compile like:
>> > >> > > >
>> > >> > > > checking for #include
>> 
>> > >> > > >
>> > >> > > > ?
>> > >> > > >
>> > >> > >
>> > >> > > Yep, the full build log for
>> sca/runtime/extensions/ruby/extension
>> > >> is:
>> > >> > >
>> > >> > > Making install in extension
>> > >> > > make[4]: Entering directory
>> > >> > >
>> > >>
>> >
>>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
>>
>> > >>
>> > >> > > cd src; ruby extconf.rb; make
>> > >> > > checking for tuscany/sca/ruby/RubyCompositeContext.h... yes
>> > >> > > checking for main() in -ltuscany_sca_ruby_lang... yes
>> > >> > > creating Makefile
>> > >> > > make[5]: Entering directory
>> > >> > >
>> > >>
>> >
>>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
>>
>> >
>> > >>
>> > >> > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
>> -fexceptions
>> > >> > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
>> > >> > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
>> > >> > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux
>> > >> -I.   -c
>> > >> > > Extension.cpp
>> > >> > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such
>> file
>> > or
>> > >> directory
>> > >> > > Extension.cpp:29:51: error:
>> > tuscany/sca/ruby/RubyCompositeContext.h:
>> > >> > > No such file or directory
>> > >> > > Extension.cpp:35: error: āVALUEā does not name a type
>> > >> > > Extension.cpp: In function āvoid Init_tuscany_sca_ruby()ā:
>> > >> > > Extension.cpp:47: error: āVALUEā was not declared in this
scope
>> > >> > > Extension.cpp:47: error: expected `;' before āmoduleā
>> > >> > > Extension.cpp:48: error: āmoduleā was not declared in this
>> scope
>> > >> > > Extension.cpp:48: error: expected primary-expression before
ā)ā
>> > >> token
>> > >> > > Extension.cpp :48: error: āANYARGSā was not declared in this
>> > scope
>> > >> > > Extension.cpp:48: error: ārb_define_module_functionā was not
>> > >> declared
>> > >> > > in this scope
>> > >> > > make[5]: *** [ Extension.o] Error 1
>> > >> > > make[5]: Leaving directory
>> > >> > >
>> > >>
>> >
>>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
>>
>> > >>
>> > >> > > make[4]: *** [extension_build] Error 2
>> > >> > > make[4]: Leaving directory
>> > >> > >
>> > >>
>> >
>>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
>>
>> > >>
>> > >> > > make[3]: *** [install-recursive] Error 1
>> > >> 

Re: Native M3 release status

[Jean-Sebastien Delfino]

Pete Robbins wrote:

On 22/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:




 On 22/02/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> Pete Robbins wrote:
> > On 22/02/07, Andrew Borley <[EMAIL PROTECTED] > wrote:
> >>
> >> On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >> > On 21/02/07, Andrew Borley < [EMAIL PROTECTED]> wrote:
> >> > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >> > > > On 21/02/07, Andrew Borley < [EMAIL PROTECTED]> wrote:
> >> > > > >
> >> > > > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED] > wrote:
> >> > > > > > I now have Ruby working on Mac. I will remove the ws
> bindings
> >> and
> >> > > > > clients
> >> > > > > > from the *Calculator samples so we have a simple 
sample for

>
> >> each
> >> > > > > language.
> >> > > > > > $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to
> the
> >> > > > > LD_LIBRARY_PATH
> >> > > > > > (or PATH on windows) to run the Ruby clients. I've 
updated

> the
> >> runclient
> >> > > > > > scripts.
> >> > > > >
> >> > > > > Running a Linux build against the latest code gives me an
> error
> >> with
> >> > > > > the new Ruby layout:
> >> > > > >
> >> > > > > make[5]: Entering directory
> >> > > > >
> >> > > > >
> >>
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src' 


>
> >>
> >> > > > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
> >> -fexceptions
> >> > > > > -fstack-protector --param=ssp-buffer-size=4 -m32 
-march=i386

> >> > > > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC
> -I.
> >> > > > > -I/usr/lib/ruby/1.8/i386-linux 
-I/usr/lib/ruby/1.8/i386-linux

> >> -I.   -c
> >> > > > > Extension.cpp
> >> > > > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No 
such

> >> file
> >> or
> >> > > > > directory
> >> > > > > Extension.cpp:29:51: error:
> >> tuscany/sca/ruby/RubyCompositeContext.h:
> >> > > > > No such file or directory
> >> > > > >
> >> > > > > Did everything get checked in? Am I missing an env 
variable?

> >> > > >
> >> > > >
> >> > > > Everything is checked in. The extconf.rb RUby script 
generates

> the
> >> makefile.
> >> > > > It should add the lib and include paths nexessary. Are there
> >> messages before
> >> > > > the compile like:
> >> > > >
> >> > > > checking for #include 


> >> > > >
> >> > > > ?
> >> > > >
> >> > >
> >> > > Yep, the full build log for 
sca/runtime/extensions/ruby/extension

> >> is:
> >> > >
> >> > > Making install in extension
> >> > > make[4]: Entering directory
> >> > >
> >>
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension' 


> >>
> >> > > cd src; ruby extconf.rb; make
> >> > > checking for tuscany/sca/ruby/RubyCompositeContext.h... yes
> >> > > checking for main() in -ltuscany_sca_ruby_lang... yes
> >> > > creating Makefile
> >> > > make[5]: Entering directory
> >> > >
> >>
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src' 


>
> >>
> >> > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
-fexceptions

> >> > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> >> > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> >> > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux
> >> -I.   -c
> >> > > Extension.cpp
> >> > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such 
file

> or
> >> directory
> >> > > Extension.cpp:29:51: error:
> tuscany/sca/ruby/RubyCompositeContext.h:
> >> > > No such file or directory
> >> > > Extension.cpp:35: error: āVALUEā does not name a type
> >> > > Extension.cpp: In function āvoid Init_tuscany_sca_ruby()ā:
> >> > > Extension.cpp:47: error: āVALUEā was not declared in this scope
> >> > > Extension.cpp:47: error: expected `;' before āmoduleā
> >> > > Extension.cpp:48: error: āmoduleā was not declared in this 
scope

> >> > > Extension.cpp:48: error: expected primary-expression before ā)ā
> >> token
> >> > > Extension.cpp :48: error: āANYARGSā was not declared in this
> scope
> >> > > Extension.cpp:48: error: ārb_define_module_functionā was not
> >> declared
> >> > > in this scope
> >> > > make[5]: *** [ Extension.o] Error 1
> >> > > make[5]: Leaving directory
> >> > >
> >>
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src' 


> >>
> >> > > make[4]: *** [extension_build] Error 2
> >> > > make[4]: Leaving directory
> >> > >
> >>
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension' 


> >>
> >> > > make[3]: *** [install-recursive] Error 1
> >> > > make[3]: Leaving directory
> >> > > 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby'

> >> > > make[2]: *** [install-recursive] Error 1
> >> > > make[2]: Leaving directory
> >> > > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions'
> >> > > make[1]: *** [install-recursive] Error 1
> >> > > make[1]: Leaving directory
> >> `/home/ajborley/workspace/TuscanyCPP/sca/runtime'
> >> > > make: *** [install-recursive] Error 1
> >> > >
> >> > > So 

Re: Tuscany Native M3 release

[Pete Robbins]

Good stuff. Anything checked in will be included. I'm not ready yet to
freeze the release.

We have a few problems with Python and Rest on linux and I haven't yet tried
out the new PHP extension. I've made changes for building the distribution
for Linux but still need to make some changes on windows.

Good news is that your SDO changes seem to work with SCA.

Cheers,


On 23/02/07, Geoffrey Winn <[EMAIL PROTECTED]> wrote:


I've changed my mind about changes to SDO that should be in M3. I've just
checked in an alteration to Type::getProperties that is good for a 25%
speed-up in the overall execution of SDO. (See TUSCANY-1136, r510951). I
would like to see that included in M3.

Regards,

Geoff.

On 19/02/07, Geoffrey Winn <[EMAIL PROTECTED]> wrote:
>
> Pete,
>
> There are no pending changes in SDO that we should wait for if you are
> looking to generate a candidate this week (week beginning 19-Feb). I
will
> aim to complete as much as I can from 1078 (which may help resolve some
php
> issues), 959 (which I am part way through) and 747 (load an XML document
> without a schema).
>
> I also think we should close 750 and 95.
> 750 describes schema validation and that is not likely to be done in
> advance of the spec group's conclusions.
> 95 describes the type safe interface, which again is unlikely to ever be
> done for C++.
>
> Regards,
>
> Geoff.
>
> On 16/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >
> > On 16/02/07, Geoffrey Winn <[EMAIL PROTECTED]> wrote:
> > >
> > > On 15/02/07, Pete Robbins <[EMAIL PROTECTED] > wrote:
> > > >
> > > >
> > > > I'll review the SCA Jiras and we can agree on which are must-fix
for
> > the
> > > > release. Can someone review the SDO C++ Jiras and propose a list
of
> > > > must-fix?
> > >
> > >
> > > I'll do the JIRA review for SDO C++
> > >
> > > Geoff.
> > >
> >
> >
> > Thanks Geoff. Are there any features in the pipeline that should be in
> > the
> > M3 release? Assuming we cut a candidate next week is there anything we
> > should wiat for?
> >
> > Cheers,
> >
> > --
> > Pete
> >
>
>





--
Pete

Re: Tuscany Native M3 release

[Geoffrey Winn]

I've changed my mind about changes to SDO that should be in M3. I've just
checked in an alteration to Type::getProperties that is good for a 25%
speed-up in the overall execution of SDO. (See TUSCANY-1136, r510951). I
would like to see that included in M3.

Regards,

Geoff.

On 19/02/07, Geoffrey Winn <[EMAIL PROTECTED]> wrote:


Pete,

There are no pending changes in SDO that we should wait for if you are
looking to generate a candidate this week (week beginning 19-Feb). I will
aim to complete as much as I can from 1078 (which may help resolve some php
issues), 959 (which I am part way through) and 747 (load an XML document
without a schema).

I also think we should close 750 and 95.
750 describes schema validation and that is not likely to be done in
advance of the spec group's conclusions.
95 describes the type safe interface, which again is unlikely to ever be
done for C++.

Regards,

Geoff.

On 16/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
> On 16/02/07, Geoffrey Winn <[EMAIL PROTECTED]> wrote:
> >
> > On 15/02/07, Pete Robbins <[EMAIL PROTECTED] > wrote:
> > >
> > >
> > > I'll review the SCA Jiras and we can agree on which are must-fix for
> the
> > > release. Can someone review the SDO C++ Jiras and propose a list of
> > > must-fix?
> >
> >
> > I'll do the JIRA review for SDO C++
> >
> > Geoff.
> >
>
>
> Thanks Geoff. Are there any features in the pipeline that should be in
> the
> M3 release? Assuming we cut a candidate next week is there anything we
> should wiat for?
>
> Cheers,
>
> --
> Pete
>

Re: Native M3 release status

[Pete Robbins]

On 22/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:




 On 22/02/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> Pete Robbins wrote:
> > On 22/02/07, Andrew Borley <[EMAIL PROTECTED] > wrote:
> >>
> >> On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >> > On 21/02/07, Andrew Borley < [EMAIL PROTECTED]> wrote:
> >> > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >> > > > On 21/02/07, Andrew Borley < [EMAIL PROTECTED]> wrote:
> >> > > > >
> >> > > > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED] > wrote:
> >> > > > > > I now have Ruby working on Mac. I will remove the ws
> bindings
> >> and
> >> > > > > clients
> >> > > > > > from the *Calculator samples so we have a simple sample for
>
> >> each
> >> > > > > language.
> >> > > > > > $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to
> the
> >> > > > > LD_LIBRARY_PATH
> >> > > > > > (or PATH on windows) to run the Ruby clients. I've updated
> the
> >> runclient
> >> > > > > > scripts.
> >> > > > >
> >> > > > > Running a Linux build against the latest code gives me an
> error
> >> with
> >> > > > > the new Ruby layout:
> >> > > > >
> >> > > > > make[5]: Entering directory
> >> > > > >
> >> > > > >
> >>
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
>
> >>
> >> > > > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
> >> -fexceptions
> >> > > > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> >> > > > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC
> -I.
> >> > > > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux
> >> -I.   -c
> >> > > > > Extension.cpp
> >> > > > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such
> >> file
> >> or
> >> > > > > directory
> >> > > > > Extension.cpp:29:51: error:
> >> tuscany/sca/ruby/RubyCompositeContext.h:
> >> > > > > No such file or directory
> >> > > > >
> >> > > > > Did everything get checked in? Am I missing an env variable?
> >> > > >
> >> > > >
> >> > > > Everything is checked in. The extconf.rb RUby script generates
> the
> >> makefile.
> >> > > > It should add the lib and include paths nexessary. Are there
> >> messages before
> >> > > > the compile like:
> >> > > >
> >> > > > checking for #include 
> >> > > >
> >> > > > ?
> >> > > >
> >> > >
> >> > > Yep, the full build log for sca/runtime/extensions/ruby/extension
> >> is:
> >> > >
> >> > > Making install in extension
> >> > > make[4]: Entering directory
> >> > >
> >>
> `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
> >>
> >> > > cd src; ruby extconf.rb; make
> >> > > checking for tuscany/sca/ruby/RubyCompositeContext.h... yes
> >> > > checking for main() in -ltuscany_sca_ruby_lang... yes
> >> > > creating Makefile
> >> > > make[5]: Entering directory
> >> > >
> >>
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
>
> >>
> >> > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> >> > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> >> > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> >> > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux
> >> -I.   -c
> >> > > Extension.cpp
> >> > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file
> or
> >> directory
> >> > > Extension.cpp:29:51: error:
> tuscany/sca/ruby/RubyCompositeContext.h:
> >> > > No such file or directory
> >> > > Extension.cpp:35: error: āVALUEā does not name a type
> >> > > Extension.cpp: In function āvoid Init_tuscany_sca_ruby()ā:
> >> > > Extension.cpp:47: error: āVALUEā was not declared in this scope
> >> > > Extension.cpp:47: error: expected `;' before āmoduleā
> >> > > Extension.cpp:48: error: āmoduleā was not declared in this scope
> >> > > Extension.cpp:48: error: expected primary-expression before ā)ā
> >> token
> >> > > Extension.cpp :48: error: āANYARGSā was not declared in this
> scope
> >> > > Extension.cpp:48: error: ārb_define_module_functionā was not
> >> declared
> >> > > in this scope
> >> > > make[5]: *** [ Extension.o] Error 1
> >> > > make[5]: Leaving directory
> >> > >
> >>
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> >>
> >> > > make[4]: *** [extension_build] Error 2
> >> > > make[4]: Leaving directory
> >> > >
> >>
> `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
> >>
> >> > > make[3]: *** [install-recursive] Error 1
> >> > > make[3]: Leaving directory
> >> > > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby'
> >> > > make[2]: *** [install-recursive] Error 1
> >> > > make[2]: Leaving directory
> >> > > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions'
> >> > > make[1]: *** [install-recursive] Error 1
> >> > > make[1]: Leaving directory
> >> `/home/ajborley/workspace/TuscanyCPP/sca/runtime'
> >> > > make: *** [install-recursive] Error 1
> >> > >
> >> > > So the check for tuscany/sca/ruby/RubyCompositeContext.h is there
>

Re: Native M3 release status

[Simon Laws]

On 2/22/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


On 22/02/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> Pete Robbins wrote:
> > On 22/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> >>
> >> On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >> > On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> >> > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >> > > > On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> >> > > > >
> >> > > > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >> > > > > > I now have Ruby working on Mac. I will remove the ws
bindings
> >> and
> >> > > > > clients
> >> > > > > > from the *Calculator samples so we have a simple sample for
> >> each
> >> > > > > language.
> >> > > > > > $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to
the
> >> > > > > LD_LIBRARY_PATH
> >> > > > > > (or PATH on windows) to run the Ruby clients. I've updated
> the
> >> runclient
> >> > > > > > scripts.
> >> > > > >
> >> > > > > Running a Linux build against the latest code gives me an
error
> >> with
> >> > > > > the new Ruby layout:
> >> > > > >
> >> > > > > make[5]: Entering directory
> >> > > > >
> >> > > > >
> >>
>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> >>
> >> > > > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
> >> -fexceptions
> >> > > > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> >> > > > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC
-I.
> >> > > > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux
> >> -I.   -c
> >> > > > > Extension.cpp
> >> > > > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such
> >> file
> >> or
> >> > > > > directory
> >> > > > > Extension.cpp:29:51: error:
> >> tuscany/sca/ruby/RubyCompositeContext.h:
> >> > > > > No such file or directory
> >> > > > >
> >> > > > > Did everything get checked in? Am I missing an env variable?
> >> > > >
> >> > > >
> >> > > > Everything is checked in. The extconf.rb RUby script generates
> the
> >> makefile.
> >> > > > It should add the lib and include paths nexessary. Are there
> >> messages before
> >> > > > the compile like:
> >> > > >
> >> > > > checking for #include 
> >> > > >
> >> > > > ?
> >> > > >
> >> > >
> >> > > Yep, the full build log for sca/runtime/extensions/ruby/extension
> >> is:
> >> > >
> >> > > Making install in extension
> >> > > make[4]: Entering directory
> >> > >
> >>
>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
> >>
> >> > > cd src; ruby extconf.rb; make
> >> > > checking for tuscany/sca/ruby/RubyCompositeContext.h... yes
> >> > > checking for main() in -ltuscany_sca_ruby_lang... yes
> >> > > creating Makefile
> >> > > make[5]: Entering directory
> >> > >
> >>
>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> >>
> >> > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> >> > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> >> > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> >> > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux
> >> -I.   -c
> >> > > Extension.cpp
> >> > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file
> or
> >> directory
> >> > > Extension.cpp:29:51: error:
> tuscany/sca/ruby/RubyCompositeContext.h:
> >> > > No such file or directory
> >> > > Extension.cpp:35: error: āVALUEā does not name a type
> >> > > Extension.cpp: In function āvoid Init_tuscany_sca_ruby()ā:
> >> > > Extension.cpp:47: error: āVALUEā was not declared in this scope
> >> > > Extension.cpp:47: error: expected `;' before āmoduleā
> >> > > Extension.cpp:48: error: āmoduleā was not declared in this scope
> >> > > Extension.cpp:48: error: expected primary-expression before ā)ā
> >> token
> >> > > Extension.cpp:48: error: āANYARGSā was not declared in this scope
> >> > > Extension.cpp:48: error: ārb_define_module_functionā was not
> >> declared
> >> > > in this scope
> >> > > make[5]: *** [Extension.o] Error 1
> >> > > make[5]: Leaving directory
> >> > >
> >>
>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> >>
> >> > > make[4]: *** [extension_build] Error 2
> >> > > make[4]: Leaving directory
> >> > >
> >>
>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
> >>
> >> > > make[3]: *** [install-recursive] Error 1
> >> > > make[3]: Leaving directory
> >> > > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby'
> >> > > make[2]: *** [install-recursive] Error 1
> >> > > make[2]: Leaving directory
> >> > > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions'
> >> > > make[1]: *** [install-recursive] Error 1
> >> > > make[1]: Leaving directory
> >> `/home/ajborley/workspace/TuscanyCPP/sca/runtime'
> >> > > make: *** [install-recursive] Error 1
> >> > >
> >> > > So the check for tuscany/sca/ruby/RubyCompositeContext.h is there
> >> > > (although there isn't

Re: Native M3 release status

[Pete Robbins]

On 22/02/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:


Pete Robbins wrote:
> On 22/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
>>
>> On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>> > On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
>> > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>> > > > On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
>> > > > >
>> > > > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>> > > > > > I now have Ruby working on Mac. I will remove the ws bindings
>> and
>> > > > > clients
>> > > > > > from the *Calculator samples so we have a simple sample for
>> each
>> > > > > language.
>> > > > > > $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to the
>> > > > > LD_LIBRARY_PATH
>> > > > > > (or PATH on windows) to run the Ruby clients. I've updated
the
>> runclient
>> > > > > > scripts.
>> > > > >
>> > > > > Running a Linux build against the latest code gives me an error
>> with
>> > > > > the new Ruby layout:
>> > > > >
>> > > > > make[5]: Entering directory
>> > > > >
>> > > > >
>>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
>>
>> > > > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
>> -fexceptions
>> > > > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
>> > > > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
>> > > > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux
>> -I.   -c
>> > > > > Extension.cpp
>> > > > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such
>> file
>> or
>> > > > > directory
>> > > > > Extension.cpp:29:51: error:
>> tuscany/sca/ruby/RubyCompositeContext.h:
>> > > > > No such file or directory
>> > > > >
>> > > > > Did everything get checked in? Am I missing an env variable?
>> > > >
>> > > >
>> > > > Everything is checked in. The extconf.rb RUby script generates
the
>> makefile.
>> > > > It should add the lib and include paths nexessary. Are there
>> messages before
>> > > > the compile like:
>> > > >
>> > > > checking for #include 
>> > > >
>> > > > ?
>> > > >
>> > >
>> > > Yep, the full build log for sca/runtime/extensions/ruby/extension
>> is:
>> > >
>> > > Making install in extension
>> > > make[4]: Entering directory
>> > >
>>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
>>
>> > > cd src; ruby extconf.rb; make
>> > > checking for tuscany/sca/ruby/RubyCompositeContext.h... yes
>> > > checking for main() in -ltuscany_sca_ruby_lang... yes
>> > > creating Makefile
>> > > make[5]: Entering directory
>> > >
>>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
>>
>> > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
>> > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
>> > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
>> > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux
>> -I.   -c
>> > > Extension.cpp
>> > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file
or
>> directory
>> > > Extension.cpp:29:51: error:
tuscany/sca/ruby/RubyCompositeContext.h:
>> > > No such file or directory
>> > > Extension.cpp:35: error: āVALUEā does not name a type
>> > > Extension.cpp: In function āvoid Init_tuscany_sca_ruby()ā:
>> > > Extension.cpp:47: error: āVALUEā was not declared in this scope
>> > > Extension.cpp:47: error: expected `;' before āmoduleā
>> > > Extension.cpp:48: error: āmoduleā was not declared in this scope
>> > > Extension.cpp:48: error: expected primary-expression before ā)ā
>> token
>> > > Extension.cpp:48: error: āANYARGSā was not declared in this scope
>> > > Extension.cpp:48: error: ārb_define_module_functionā was not
>> declared
>> > > in this scope
>> > > make[5]: *** [Extension.o] Error 1
>> > > make[5]: Leaving directory
>> > >
>>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
>>
>> > > make[4]: *** [extension_build] Error 2
>> > > make[4]: Leaving directory
>> > >
>>
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
>>
>> > > make[3]: *** [install-recursive] Error 1
>> > > make[3]: Leaving directory
>> > > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby'
>> > > make[2]: *** [install-recursive] Error 1
>> > > make[2]: Leaving directory
>> > > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions'
>> > > make[1]: *** [install-recursive] Error 1
>> > > make[1]: Leaving directory
>> `/home/ajborley/workspace/TuscanyCPP/sca/runtime'
>> > > make: *** [install-recursive] Error 1
>> > >
>> > > So the check for tuscany/sca/ruby/RubyCompositeContext.h is there
>> > > (although there isn't one for Ruby.h) and looks like it succeeds,
>> but
>> > > the build still seems to fail to find it.
>> > >
>> >
>> > The checks are supposed to add the -I and -L stuff for where it finds
>> > the headers and libraries so here should be a -I../../src in the
>> > command line. This works on Mac and my RHEL3 

Re: Native M3 release status

[Jean-Sebastien Delfino]

Pete Robbins wrote:

On 22/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:


On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > > On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> > > >
> > > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > > > > I now have Ruby working on Mac. I will remove the ws bindings
and
> > > > clients
> > > > > from the *Calculator samples so we have a simple sample for 
each

> > > > language.
> > > > > $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to the
> > > > LD_LIBRARY_PATH
> > > > > (or PATH on windows) to run the Ruby clients. I've updated the
runclient
> > > > > scripts.
> > > >
> > > > Running a Linux build against the latest code gives me an error
with
> > > > the new Ruby layout:
> > > >
> > > > make[5]: Entering directory
> > > >
> > > >
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src' 

> > > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 
-fexceptions

> > > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> > > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> > > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux
-I.   -c
> > > > Extension.cpp
> > > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such 
file

or
> > > > directory
> > > > Extension.cpp:29:51: error:
tuscany/sca/ruby/RubyCompositeContext.h:
> > > > No such file or directory
> > > >
> > > > Did everything get checked in? Am I missing an env variable?
> > >
> > >
> > > Everything is checked in. The extconf.rb RUby script generates the
makefile.
> > > It should add the lib and include paths nexessary. Are there
messages before
> > > the compile like:
> > >
> > > checking for #include 
> > >
> > > ?
> > >
> >
> > Yep, the full build log for sca/runtime/extensions/ruby/extension 
is:

> >
> > Making install in extension
> > make[4]: Entering directory
> >
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension' 


> > cd src; ruby extconf.rb; make
> > checking for tuscany/sca/ruby/RubyCompositeContext.h... yes
> > checking for main() in -ltuscany_sca_ruby_lang... yes
> > creating Makefile
> > make[5]: Entering directory
> >
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src' 


> > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux 
-I.   -c

> > Extension.cpp
> > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file or
directory
> > Extension.cpp:29:51: error: tuscany/sca/ruby/RubyCompositeContext.h:
> > No such file or directory
> > Extension.cpp:35: error: âVALUEâ does not name a type
> > Extension.cpp: In function âvoid Init_tuscany_sca_ruby()â:
> > Extension.cpp:47: error: âVALUEâ was not declared in this scope
> > Extension.cpp:47: error: expected `;' before âmoduleâ
> > Extension.cpp:48: error: âmoduleâ was not declared in this scope
> > Extension.cpp:48: error: expected primary-expression before â)â 
token

> > Extension.cpp:48: error: âANYARGSâ was not declared in this scope
> > Extension.cpp:48: error: ârb_define_module_functionâ was not 
declared

> > in this scope
> > make[5]: *** [Extension.o] Error 1
> > make[5]: Leaving directory
> >
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src' 


> > make[4]: *** [extension_build] Error 2
> > make[4]: Leaving directory
> >
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension' 


> > make[3]: *** [install-recursive] Error 1
> > make[3]: Leaving directory
> > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby'
> > make[2]: *** [install-recursive] Error 1
> > make[2]: Leaving directory
> > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions'
> > make[1]: *** [install-recursive] Error 1
> > make[1]: Leaving directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime'
> > make: *** [install-recursive] Error 1
> >
> > So the check for tuscany/sca/ruby/RubyCompositeContext.h is there
> > (although there isn't one for Ruby.h) and looks like it succeeds, 
but

> > the build still seems to fail to find it.
> >
>
> The checks are supposed to add the -I and -L stuff for where it finds
> the headers and libraries so here should be a -I../../src in the
> command line. This works on Mac and my RHEL3 linux. Which linux are
> you running?
>

I'm on Fedora core 5 with Ruby 1.8.5



I've checked in a new version of extconf.rb which is more simple and 
works

on Mac and RHEL.

Cheers,



Hi,

It looks like we have 3 sets of changes going on:
- packaging changes for the extensions
- Ruby build changes
-  PHP patches?

Could you guys please post a message here when these changes are in 
(even before you h

Re: Native M3 release status

[Jean-Sebastien Delfino]

Pete Robbins wrote:

On 21/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:



The Rest binding builds on Mac but is crashing when the SCARuntime loads
the extension which tries to register the reference binding 
extension. I'll

investigate that next.




The Rest binding is crashing because of the way TuscanyRuntime loads the
extensions. We load every library we find under the extensions folder.
Unfortunately one of these is tuscany_sca_mod_rest which is not an 
extension

but does link with one. So we load this library and discover it isn't an
extension, then unload it. Next up we load the tuscany_sca_rest_service
extension but for some reason the load is not calling the static
initializers, maybe because this library has already been loaded as a
separate instance when loading mod_rest. Removing the 
tuscany_sca_mod_rest

library from the extension path resolves the problem.

This goes back to a problem discussed on an earlier thread where we 
agreed
to change the extension loading so that only libraries in a "modules" 
folder

would be loaded. The layout of an extension will look like:

$TUSCANY_SCACPP/extensions
   myExtension/
 lib/
 mylibs_that_arent_extensions.so
 bin/
 ...
 xsd/
 
any_other_folder/
 ...
modules/
libmyExtensionLibrary.so


Only the libraries under modules will be loaded. Most likely these 
would be

symbolic links to the library in the lib/ folder.

I propose to make this change sometime today as it resolves a few 
problems.


Cheers,




Sounds good, +1 from me.

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Pete Robbins]

On 22/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:


On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > > On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> > > >
> > > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > > > > I now have Ruby working on Mac. I will remove the ws bindings
and
> > > > clients
> > > > > from the *Calculator samples so we have a simple sample for each
> > > > language.
> > > > > $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to the
> > > > LD_LIBRARY_PATH
> > > > > (or PATH on windows) to run the Ruby clients. I've updated the
runclient
> > > > > scripts.
> > > >
> > > > Running a Linux build against the latest code gives me an error
with
> > > > the new Ruby layout:
> > > >
> > > > make[5]: Entering directory
> > > >
> > > >
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> > > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> > > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> > > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> > > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux
-I.   -c
> > > > Extension.cpp
> > > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file
or
> > > > directory
> > > > Extension.cpp:29:51: error:
tuscany/sca/ruby/RubyCompositeContext.h:
> > > > No such file or directory
> > > >
> > > > Did everything get checked in? Am I missing an env variable?
> > >
> > >
> > > Everything is checked in. The extconf.rb RUby script generates the
makefile.
> > > It should add the lib and include paths nexessary. Are there
messages before
> > > the compile like:
> > >
> > > checking for #include 
> > >
> > > ?
> > >
> >
> > Yep, the full build log for sca/runtime/extensions/ruby/extension is:
> >
> > Making install in extension
> > make[4]: Entering directory
> >
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
> > cd src; ruby extconf.rb; make
> > checking for tuscany/sca/ruby/RubyCompositeContext.h... yes
> > checking for main() in -ltuscany_sca_ruby_lang... yes
> > creating Makefile
> > make[5]: Entering directory
> >
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I.   -c
> > Extension.cpp
> > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file or
directory
> > Extension.cpp:29:51: error: tuscany/sca/ruby/RubyCompositeContext.h:
> > No such file or directory
> > Extension.cpp:35: error: âVALUEâ does not name a type
> > Extension.cpp: In function âvoid Init_tuscany_sca_ruby()â:
> > Extension.cpp:47: error: âVALUEâ was not declared in this scope
> > Extension.cpp:47: error: expected `;' before âmoduleâ
> > Extension.cpp:48: error: âmoduleâ was not declared in this scope
> > Extension.cpp:48: error: expected primary-expression before â)â token
> > Extension.cpp:48: error: âANYARGSâ was not declared in this scope
> > Extension.cpp:48: error: ârb_define_module_functionâ was not declared
> > in this scope
> > make[5]: *** [Extension.o] Error 1
> > make[5]: Leaving directory
> >
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> > make[4]: *** [extension_build] Error 2
> > make[4]: Leaving directory
> >
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
> > make[3]: *** [install-recursive] Error 1
> > make[3]: Leaving directory
> > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby'
> > make[2]: *** [install-recursive] Error 1
> > make[2]: Leaving directory
> > `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions'
> > make[1]: *** [install-recursive] Error 1
> > make[1]: Leaving directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime'
> > make: *** [install-recursive] Error 1
> >
> > So the check for tuscany/sca/ruby/RubyCompositeContext.h is there
> > (although there isn't one for Ruby.h) and looks like it succeeds, but
> > the build still seems to fail to find it.
> >
>
> The checks are supposed to add the -I and -L stuff for where it finds
> the headers and libraries so here should be a -I../../src in the
> command line. This works on Mac and my RHEL3 linux. Which linux are
> you running?
>

I'm on Fedora core 5 with Ruby 1.8.5



I've checked in a new version of extconf.rb which is more simple and works
on Mac and RHEL.

Cheers,

--
Pete

Re: Native M3 release status

[Andrew Borley]

On 2/22/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

On 21/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
>
> The Rest binding builds on Mac but is crashing when the SCARuntime loads
> the extension which tries to register the reference binding extension. I'll
> investigate that next.
>
>

The Rest binding is crashing because of the way TuscanyRuntime loads the
extensions. We load every library we find under the extensions folder.
Unfortunately one of these is tuscany_sca_mod_rest which is not an extension
but does link with one. So we load this library and discover it isn't an
extension, then unload it. Next up we load the tuscany_sca_rest_service
extension but for some reason the load is not calling the static
initializers, maybe because this library has already been loaded as a
separate instance when loading mod_rest. Removing the tuscany_sca_mod_rest
library from the extension path resolves the problem.

This goes back to a problem discussed on an earlier thread where we agreed
to change the extension loading so that only libraries in a "modules" folder
would be loaded. The layout of an extension will look like:

$TUSCANY_SCACPP/extensions
myExtension/
  lib/
  mylibs_that_arent_extensions.so
  bin/
  ...
  xsd/
  
 any_other_folder/
  ...
 modules/
 libmyExtensionLibrary.so


Only the libraries under modules will be loaded. Most likely these would be
symbolic links to the library in the lib/ folder.

I propose to make this change sometime today as it resolves a few problems.



+1 for this.
Andy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Andrew Borley]

On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> > >
> > > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > > > I now have Ruby working on Mac. I will remove the ws bindings and
> > > clients
> > > > from the *Calculator samples so we have a simple sample for each
> > > language.
> > > > $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to the
> > > LD_LIBRARY_PATH
> > > > (or PATH on windows) to run the Ruby clients. I've updated the runclient
> > > > scripts.
> > >
> > > Running a Linux build against the latest code gives me an error with
> > > the new Ruby layout:
> > >
> > > make[5]: Entering directory
> > >
> > > 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> > > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> > > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> > > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> > > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I.   -c
> > > Extension.cpp
> > > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file or
> > > directory
> > > Extension.cpp:29:51: error: tuscany/sca/ruby/RubyCompositeContext.h:
> > > No such file or directory
> > >
> > > Did everything get checked in? Am I missing an env variable?
> >
> >
> > Everything is checked in. The extconf.rb RUby script generates the makefile.
> > It should add the lib and include paths nexessary. Are there messages before
> > the compile like:
> >
> > checking for #include 
> >
> > ?
> >
>
> Yep, the full build log for sca/runtime/extensions/ruby/extension is:
>
> Making install in extension
> make[4]: Entering directory
> `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
> cd src; ruby extconf.rb; make
> checking for tuscany/sca/ruby/RubyCompositeContext.h... yes
> checking for main() in -ltuscany_sca_ruby_lang... yes
> creating Makefile
> make[5]: Entering directory
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I.   -c
> Extension.cpp
> Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file or directory
> Extension.cpp:29:51: error: tuscany/sca/ruby/RubyCompositeContext.h:
> No such file or directory
> Extension.cpp:35: error: âVALUEâ does not name a type
> Extension.cpp: In function âvoid Init_tuscany_sca_ruby()â:
> Extension.cpp:47: error: âVALUEâ was not declared in this scope
> Extension.cpp:47: error: expected `;' before âmoduleâ
> Extension.cpp:48: error: âmoduleâ was not declared in this scope
> Extension.cpp:48: error: expected primary-expression before â)â token
> Extension.cpp:48: error: âANYARGSâ was not declared in this scope
> Extension.cpp:48: error: ârb_define_module_functionâ was not declared
> in this scope
> make[5]: *** [Extension.o] Error 1
> make[5]: Leaving directory
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> make[4]: *** [extension_build] Error 2
> make[4]: Leaving directory
> `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
> make[3]: *** [install-recursive] Error 1
> make[3]: Leaving directory
> `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby'
> make[2]: *** [install-recursive] Error 1
> make[2]: Leaving directory
> `/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions'
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory `/home/ajborley/workspace/TuscanyCPP/sca/runtime'
> make: *** [install-recursive] Error 1
>
> So the check for tuscany/sca/ruby/RubyCompositeContext.h is there
> (although there isn't one for Ruby.h) and looks like it succeeds, but
> the build still seems to fail to find it.
>

The checks are supposed to add the -I and -L stuff for where it finds
the headers and libraries so here should be a -I../../src in the
command line. This works on Mac and my RHEL3 linux. Which linux are
you running?



I'm on Fedora core 5 with Ruby 1.8.5

Cheers
Andy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Pete Robbins]

On 21/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:



The Rest binding builds on Mac but is crashing when the SCARuntime loads
the extension which tries to register the reference binding extension. I'll
investigate that next.




The Rest binding is crashing because of the way TuscanyRuntime loads the
extensions. We load every library we find under the extensions folder.
Unfortunately one of these is tuscany_sca_mod_rest which is not an extension
but does link with one. So we load this library and discover it isn't an
extension, then unload it. Next up we load the tuscany_sca_rest_service
extension but for some reason the load is not calling the static
initializers, maybe because this library has already been loaded as a
separate instance when loading mod_rest. Removing the tuscany_sca_mod_rest
library from the extension path resolves the problem.

This goes back to a problem discussed on an earlier thread where we agreed
to change the extension loading so that only libraries in a "modules" folder
would be loaded. The layout of an extension will look like:

$TUSCANY_SCACPP/extensions
   myExtension/
 lib/
 mylibs_that_arent_extensions.so
 bin/
 ...
 xsd/
 
any_other_folder/
 ...
modules/
libmyExtensionLibrary.so


Only the libraries under modules will be loaded. Most likely these would be
symbolic links to the library in the lib/ folder.

I propose to make this change sometime today as it resolves a few problems.

Cheers,


--
Pete

Re: Native M3 release status

[Pete Robbins]

On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:

On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> >
> > On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > > I now have Ruby working on Mac. I will remove the ws bindings and
> > clients
> > > from the *Calculator samples so we have a simple sample for each
> > language.
> > > $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to the
> > LD_LIBRARY_PATH
> > > (or PATH on windows) to run the Ruby clients. I've updated the runclient
> > > scripts.
> >
> > Running a Linux build against the latest code gives me an error with
> > the new Ruby layout:
> >
> > make[5]: Entering directory
> >
> > 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> > g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> > -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> > -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> > -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I.   -c
> > Extension.cpp
> > Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file or
> > directory
> > Extension.cpp:29:51: error: tuscany/sca/ruby/RubyCompositeContext.h:
> > No such file or directory
> >
> > Did everything get checked in? Am I missing an env variable?
>
>
> Everything is checked in. The extconf.rb RUby script generates the makefile.
> It should add the lib and include paths nexessary. Are there messages before
> the compile like:
>
> checking for #include 
>
> ?
>

Yep, the full build log for sca/runtime/extensions/ruby/extension is:

Making install in extension
make[4]: Entering directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
cd src; ruby extconf.rb; make
checking for tuscany/sca/ruby/RubyCompositeContext.h... yes
checking for main() in -ltuscany_sca_ruby_lang... yes
creating Makefile
make[5]: Entering directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
-mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
-I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I.   -c
Extension.cpp
Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file or directory
Extension.cpp:29:51: error: tuscany/sca/ruby/RubyCompositeContext.h:
No such file or directory
Extension.cpp:35: error: âVALUEâ does not name a type
Extension.cpp: In function âvoid Init_tuscany_sca_ruby()â:
Extension.cpp:47: error: âVALUEâ was not declared in this scope
Extension.cpp:47: error: expected `;' before âmoduleâ
Extension.cpp:48: error: âmoduleâ was not declared in this scope
Extension.cpp:48: error: expected primary-expression before â)â token
Extension.cpp:48: error: âANYARGSâ was not declared in this scope
Extension.cpp:48: error: ârb_define_module_functionâ was not declared
in this scope
make[5]: *** [Extension.o] Error 1
make[5]: Leaving directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
make[4]: *** [extension_build] Error 2
make[4]: Leaving directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/ajborley/workspace/TuscanyCPP/sca/runtime'
make: *** [install-recursive] Error 1

So the check for tuscany/sca/ruby/RubyCompositeContext.h is there
(although there isn't one for Ruby.h) and looks like it succeeds, but
the build still seems to fail to find it.



The checks are supposed to add the -I and -L stuff for where it finds
the headers and libraries so here should be a -I../../src in the
command line. This works on Mac and my RHEL3 linux. Which linux are
you running?

--
Pete

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Andrew Borley]

On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
>
> On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > I now have Ruby working on Mac. I will remove the ws bindings and
> clients
> > from the *Calculator samples so we have a simple sample for each
> language.
> > $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to the
> LD_LIBRARY_PATH
> > (or PATH on windows) to run the Ruby clients. I've updated the runclient
> > scripts.
>
> Running a Linux build against the latest code gives me an error with
> the new Ruby layout:
>
> make[5]: Entering directory
>
> 
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
> g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
> -mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
> -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I.   -c
> Extension.cpp
> Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file or
> directory
> Extension.cpp:29:51: error: tuscany/sca/ruby/RubyCompositeContext.h:
> No such file or directory
>
> Did everything get checked in? Am I missing an env variable?


Everything is checked in. The extconf.rb RUby script generates the makefile.
It should add the lib and include paths nexessary. Are there messages before
the compile like:

checking for #include 

?



Yep, the full build log for sca/runtime/extensions/ruby/extension is:

Making install in extension
make[4]: Entering directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
cd src; ruby extconf.rb; make
checking for tuscany/sca/ruby/RubyCompositeContext.h... yes
checking for main() in -ltuscany_sca_ruby_lang... yes
creating Makefile
make[5]: Entering directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
-mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
-I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I.   -c
Extension.cpp
Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file or directory
Extension.cpp:29:51: error: tuscany/sca/ruby/RubyCompositeContext.h:
No such file or directory
Extension.cpp:35: error: âVALUEâ does not name a type
Extension.cpp: In function âvoid Init_tuscany_sca_ruby()â:
Extension.cpp:47: error: âVALUEâ was not declared in this scope
Extension.cpp:47: error: expected `;' before âmoduleâ
Extension.cpp:48: error: âmoduleâ was not declared in this scope
Extension.cpp:48: error: expected primary-expression before â)â token
Extension.cpp:48: error: âANYARGSâ was not declared in this scope
Extension.cpp:48: error: ârb_define_module_functionâ was not declared
in this scope
make[5]: *** [Extension.o] Error 1
make[5]: Leaving directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
make[4]: *** [extension_build] Error 2
make[4]: Leaving directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/ajborley/workspace/TuscanyCPP/sca/runtime'
make: *** [install-recursive] Error 1

So the check for tuscany/sca/ruby/RubyCompositeContext.h is there
(although there isn't one for Ruby.h) and looks like it succeeds, but
the build still seems to fail to find it.

Cheers
Andy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Pete Robbins]

On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:


On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> I now have Ruby working on Mac. I will remove the ws bindings and
clients
> from the *Calculator samples so we have a simple sample for each
language.
> $TUSCANY_SCACPP/extensions/ruby/lib needs to be added to the
LD_LIBRARY_PATH
> (or PATH on windows) to run the Ruby clients. I've updated the runclient
> scripts.

Running a Linux build against the latest code gives me an error with
the new Ruby layout:

make[5]: Entering directory

`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
-mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
-I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I.   -c
Extension.cpp
Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file or
directory
Extension.cpp:29:51: error: tuscany/sca/ruby/RubyCompositeContext.h:
No such file or directory

Did everything get checked in? Am I missing an env variable?



Everything is checked in. The extconf.rb RUby script generates the makefile.
It should add the lib and include paths nexessary. Are there messages before
the compile like:

checking for #include 

?







--
Pete

Re: Native M3 release status

[Andrew Borley]

On 2/21/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

I now have Ruby working on Mac. I will remove the ws bindings and clients
from the *Calculator samples so we have a simple sample for each language.
$TUSCANY_SCACPP/extensions/ruby/lib needs to be added to the LD_LIBRARY_PATH
(or PATH on windows) to run the Ruby clients. I've updated the runclient
scripts.


Running a Linux build against the latest code gives me an error with
the new Ruby layout:

make[5]: Entering directory
`/home/ajborley/workspace/TuscanyCPP/sca/runtime/extensions/ruby/extension/src'
g++ -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386
-mtune=generic -fasynchronous-unwind-tables -Wall  -fPIC   -I.
-I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I.   -c
Extension.cpp
Extension.cpp:28:35: error: tuscany/sca/ruby/Ruby.h: No such file or directory
Extension.cpp:29:51: error: tuscany/sca/ruby/RubyCompositeContext.h:
No such file or directory

Did everything get checked in? Am I missing an env variable?

Cheers
Andy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Pete Robbins]

I now have Ruby working on Mac. I will remove the ws bindings and clients
from the *Calculator samples so we have a simple sample for each language.
$TUSCANY_SCACPP/extensions/ruby/lib needs to be added to the LD_LIBRARY_PATH
(or PATH on windows) to run the Ruby clients. I've updated the runclient
scripts.

The Rest binding builds on Mac but is crashing when the SCARuntime loads the
extension which tries to register the reference binding extension. I'll
investigate that next.

Cheers,

--
Pete

Re: Native M3 release status

[Pete Robbins]

On 21/02/07, Andrew Borley <[EMAIL PROTECTED]> wrote:


On 2/20/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
> On 2/20/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> > I'm currently working through building/testing the extensions and
samples
> > across Windows, Linux and Mac OS.
> >
> > Cpp: extension and samples look good (CppBigBank does not run on Mac
as we
> > have no ws binding extension)
> >
> > Ruby: Works fine on Windows and Linux (after fix I applied yesterday).
> > Currently re-structuring the extension to work with Mac, I think this
should
> > be done by tomorrow.
> >
> > Python: Basic sample runs fine across all platforms.
> >
> > PHP: ? - I haven't built this yet
> >
> > REST: partially tested on Win and Linux
> >
> > So... there's still a fair bit to get through. Anyone care to fill in
some
> > of the blanks?
> >
> > Cheers,
> >
> > --
> > Pete
> >
>
> All the WS, REST and Python samples run fine on my Windows system, but
> I'm having a Python issue on Linux (I think because my Python is v2.4
> and it seems hard to get it updated..)
>
> Cheers
> Andy
>

On further investigation, it's actually not vary hard to update to
Python 2.5 (well, run 2.5 alongside 2.4). What is hard is getting the
Python ElementTree package to run happily within a Ruby environment.
This is the case in the RestYahoo sample where we have a Ruby local
client invoking a Python component. I get an exception thrown within
the ElementTree code when it tries to load the xml.parsers.expat
module (which is a binary library). I think this is due to Python
needing to use its newer version of the expat lib than the one that
Ruby must have loaded. There doesn't seem to be a way of upgrading the
expat package on my system - the 1.95 version I have is required by
400 other packages!

We could change the sample to have a Python client instead of Ruby, as
it is more about demonstrating the REST extension rather than Ruby
talking to Python, but it looks like we have a restriction here.

Anyone have any ideas?



Not off the top of my head. You could try building Ruby against the expat
that Python needs???

Cheers,

--
Pete

Re: Native M3 release status

[Andrew Borley]

On 2/20/07, Andrew Borley <[EMAIL PROTECTED]> wrote:

On 2/20/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> I'm currently working through building/testing the extensions and samples
> across Windows, Linux and Mac OS.
>
> Cpp: extension and samples look good (CppBigBank does not run on Mac as we
> have no ws binding extension)
>
> Ruby: Works fine on Windows and Linux (after fix I applied yesterday).
> Currently re-structuring the extension to work with Mac, I think this should
> be done by tomorrow.
>
> Python: Basic sample runs fine across all platforms.
>
> PHP: ? - I haven't built this yet
>
> REST: partially tested on Win and Linux
>
> So... there's still a fair bit to get through. Anyone care to fill in some
> of the blanks?
>
> Cheers,
>
> --
> Pete
>

All the WS, REST and Python samples run fine on my Windows system, but
I'm having a Python issue on Linux (I think because my Python is v2.4
and it seems hard to get it updated..)

Cheers
Andy



On further investigation, it's actually not vary hard to update to
Python 2.5 (well, run 2.5 alongside 2.4). What is hard is getting the
Python ElementTree package to run happily within a Ruby environment.
This is the case in the RestYahoo sample where we have a Ruby local
client invoking a Python component. I get an exception thrown within
the ElementTree code when it tries to load the xml.parsers.expat
module (which is a binary library). I think this is due to Python
needing to use its newer version of the expat lib than the one that
Ruby must have loaded. There doesn't seem to be a way of upgrading the
expat package on my system - the 1.95 version I have is required by
400 other packages!

We could change the sample to have a Python client instead of Ruby, as
it is more about demonstrating the REST extension rather than Ruby
talking to Python, but it looks like we have a restriction here.

Anyone have any ideas?

Cheers
Andy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Native M3 release status

[Andrew Borley]

On 2/20/07, Pete Robbins <[EMAIL PROTECTED]> wrote:

I'm currently working through building/testing the extensions and samples
across Windows, Linux and Mac OS.

Cpp: extension and samples look good (CppBigBank does not run on Mac as we
have no ws binding extension)

Ruby: Works fine on Windows and Linux (after fix I applied yesterday).
Currently re-structuring the extension to work with Mac, I think this should
be done by tomorrow.

Python: Basic sample runs fine across all platforms.

PHP: ? - I haven't built this yet

REST: partially tested on Win and Linux

So... there's still a fair bit to get through. Anyone care to fill in some
of the blanks?

Cheers,

--
Pete



All the WS, REST and Python samples run fine on my Windows system, but
I'm having a Python issue on Linux (I think because my Python is v2.4
and it seems hard to get it updated..)

Cheers
Andy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Native M3 release status

[Pete Robbins]

I'm currently working through building/testing the extensions and samples
across Windows, Linux and Mac OS.

Cpp: extension and samples look good (CppBigBank does not run on Mac as we
have no ws binding extension)

Ruby: Works fine on Windows and Linux (after fix I applied yesterday).
Currently re-structuring the extension to work with Mac, I think this should
be done by tomorrow.

Python: Basic sample runs fine across all platforms.

PHP: ? - I haven't built this yet

REST: partially tested on Win and Linux

So... there's still a fair bit to get through. Anyone care to fill in some
of the blanks?

Cheers,

--
Pete

Re: Tuscany Native M3 release

[Geoffrey Winn]

Pete,

There are no pending changes in SDO that we should wait for if you are
looking to generate a candidate this week (week beginning 19-Feb). I will
aim to complete as much as I can from 1078 (which may help resolve some php
issues), 959 (which I am part way through) and 747 (load an XML document
without a schema).

I also think we should close 750 and 95.
750 describes schema validation and that is not likely to be done in advance
of the spec group's conclusions.
95 describes the type safe interface, which again is unlikely to ever be
done for C++.

Regards,

Geoff.

On 16/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:


On 16/02/07, Geoffrey Winn <[EMAIL PROTECTED]> wrote:
>
> On 15/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
> >
> >
> > I'll review the SCA Jiras and we can agree on which are must-fix for
the
> > release. Can someone review the SDO C++ Jiras and propose a list of
> > must-fix?
>
>
> I'll do the JIRA review for SDO C++
>
> Geoff.
>


Thanks Geoff. Are there any features in the pipeline that should be in the
M3 release? Assuming we cut a candidate next week is there anything we
should wiat for?

Cheers,

--
Pete

Re: Tuscany Native M3 release

[Pete Robbins]

On 16/02/07, Geoffrey Winn <[EMAIL PROTECTED]> wrote:


On 15/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
>
>
> I'll review the SCA Jiras and we can agree on which are must-fix for the
> release. Can someone review the SDO C++ Jiras and propose a list of
> must-fix?


I'll do the JIRA review for SDO C++

Geoff.




Thanks Geoff. Are there any features in the pipeline that should be in the
M3 release? Assuming we cut a candidate next week is there anything we
should wiat for?

Cheers,

--
Pete

Re: Tuscany Native M3 release

[Geoffrey Winn]

On 15/02/07, Pete Robbins <[EMAIL PROTECTED]> wrote:



I'll review the SCA Jiras and we can agree on which are must-fix for the
release. Can someone review the SDO C++ Jiras and propose a list of
must-fix?



I'll do the JIRA review for SDO C++

Geoff.

Tuscany Native M3 release

[Pete Robbins]

As no-one leapt in to overrule my volunteering to be RM while I've been
away... I'd better start preparing for the release ;-)

Over several threads we have discussed the content and the consensus has
been that we should produce binary downloads for Windows, Linux and Mac OS X
which contain all the extensions/samples that are available for the
platform. There will be a source download for Windows and one for Linux and
Mac (source is the same).

I will produce a matrix of platform/extensions/samples to show what we
intend to include in each download.

The release should also include a cut of SDO that we know works with the SCA
release. I've been runnning off the HEAD for SDO and it seems fine and
stable.

I'll review the SCA Jiras and we can agree on which are must-fix for the
release. Can someone review the SDO C++ Jiras and propose a list of
must-fix?

Cheers,

--
Pete