Re: Unable to acquire memory errors in HiveCompatibilitySuite

he number of active tasks. If a task is launched before > others and hogs a lot of memory quickly, the other tasks that are launched > after it might not be able to get enough memory allocation, and thus will > fail. This is not super ideal, but probably fine because tasks can be > retried, and

Re: Unable to acquire memory errors in HiveCompatibilitySuite

so forcing the ShuffleMemoryManager to assume 32 cores and therefore calculate a pagesize of 1MB passes the tests. How can we determine the correct value to use in getPageSize rather than Runtime.getRuntime.availableProcessors()? On 16 September 2015 at 10:17, Pete Robbins <robbin...@gmail.

Re: Unable to acquire memory errors in HiveCompatibilitySuite

Oops... I meant to say "The page size calculation is NOT the issue here" On 16 September 2015 at 06:46, Pete Robbins <robbin...@gmail.com> wrote: > The page size calculation is the issue here as there is plenty of free > memory, although there is maybe a fair bit of wast

Re: Unable to acquire memory errors in HiveCompatibilitySuite

euristics in memory calculation to use > SparkContext.defaultParallelism if it is local mode. > > > On Tue, Sep 15, 2015 at 10:28 AM, Pete Robbins <robbin...@gmail.com> > wrote: > >> Yes and at least there is an override by setting spark.sql.test.master >> to local[8

Re: Unable to acquire memory errors in HiveCompatibilitySuite

than 4MB. >> https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/shuffle/ShuffleMemoryManager.scala#L174 >> >> Maybe there is a place that in the maven tests that we explicitly set the >> page size (spark.buffer.pageSize) to 4MB? If yes, we need to find it and &

Re: Unable to acquire memory errors in HiveCompatibilitySuite

gt; Yea I think this is where the heuristics is failing -- it uses 8 cores to > approximate the number of active tasks, but the tests somehow is using 32 > (maybe because it explicitly sets it to that, or you set it yourself? I'm > not sure which one) > > On Mon, Sep 14, 2015 at 11:06

Re: Unable to acquire memory errors in HiveCompatibilitySuite

xplicitly sets it to that, or you set it yourself? I'm > > not sure which one) > > > > On Mon, Sep 14, 2015 at 11:06 PM, Pete Robbins <robbin...@gmail.com> > wrote: > >> > >> Reynold, thanks for replying. > >> > >> getPageSize parameters: maxMemo

Re: Unable to acquire memory errors in HiveCompatibilitySuite

) so maybe that should be changed to limit threads to num cores? Cheers, On 15 September 2015 at 08:50, Pete Robbins <robbin...@gmail.com> wrote: > Ok so it looks like the max number of active tasks reaches 30. I'm not > setting anything as it is a clean environment with clean spark

Unable to acquire memory errors in HiveCompatibilitySuite

I keep hitting errors running the tests on 1.5 such as - join31 *** FAILED *** Failed to execute query using catalyst: Error: Job aborted due to stage failure: Task 9 in stage 3653.0 failed 1 times, most recent failure: Lost task 9.0 in stage 3653.0 (TID 123363, localhost):

Re: Flaky test in DAGSchedulerSuite?

raised https://issues.apache.org/jira/browse/SPARK-10454 and PR On 4 September 2015 at 21:24, Pete Robbins <robbin...@gmail.com> wrote: > I've also just hit this and was about to raise a JIRA for this if there > isn't one already. I have a simple fix. > > On 4 September 2015

[jira] [Commented] (SPARK-10454) Flaky test: o.a.s.scheduler.DAGSchedulerSuite.late fetch failures don't cause multiple concurrent attempts for the same map stage

[ https://issues.apache.org/jira/browse/SPARK-10454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731377#comment-14731377 ] Pete Robbins commented on SPARK-10454: -- This is another case of not waiting for events to drain form

Re: Flaky test in DAGSchedulerSuite?

I've also just hit this and was about to raise a JIRA for this if there isn't one already. I have a simple fix. On 4 September 2015 at 19:09, Cheolsoo Park wrote: > Hi devs, > > I noticed this test case fails intermittently in Jenkins. > > For eg, see the following builds-

[jira] [Created] (SPARK-10454) Flaky test: o.a.s.scheduler.DAGSchedulerSuite.late fetch failures don't cause multiple concurrent attempts for the same map stage

Pete Robbins created SPARK-10454: Summary: Flaky test: o.a.s.scheduler.DAGSchedulerSuite.late fetch failures don't cause multiple concurrent attempts for the same map stage Key: SPARK-10454 URL: https

[jira] [Created] (SPARK-10431) Intermittent test failure in InputOutputMetricsSuite

Pete Robbins created SPARK-10431: Summary: Intermittent test failure in InputOutputMetricsSuite Key: SPARK-10431 URL: https://issues.apache.org/jira/browse/SPARK-10431 Project: Spark Issue

[jira] [Commented] (SPARK-9869) InputStreamSuite.socket input stream is flaky in Jenkins

[ https://issues.apache.org/jira/browse/SPARK-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729024#comment-14729024 ] Pete Robbins commented on SPARK-9869: - My pull request build for https://issues.apache.org/jira/browse

[jira] [Commented] (SPARK-9869) InputStreamSuite.socket input stream is flaky in Jenkins

[ https://issues.apache.org/jira/browse/SPARK-9869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729030#comment-14729030 ] Pete Robbins commented on SPARK-9869: - should I add this change to the PR for Spark-10431 or submit PR

[jira] [Commented] (SPARK-9644) Support update DecimalType with precision 18 in UnsafeRow

[ https://issues.apache.org/jira/browse/SPARK-9644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702705#comment-14702705 ] Pete Robbins commented on SPARK-9644: - Thanks. I think this needs to go in to 1.5

[jira] [Commented] (SPARK-9644) Support update DecimalType with precision 18 in UnsafeRow

[ https://issues.apache.org/jira/browse/SPARK-9644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14701202#comment-14701202 ] Pete Robbins commented on SPARK-9644: - This change makes assumptions about

[jira] [Commented] (SPARK-9644) Support update DecimalType with precision 18 in UnsafeRow

[ https://issues.apache.org/jira/browse/SPARK-9644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14701926#comment-14701926 ] Pete Robbins commented on SPARK-9644: - How much slower is the public API? We would

Re: Reliance on java.math.BigInteger implementation

That would be me then ;-) I'm working on a patch. Cheers, On 14 August 2015 at 23:43, Reynold Xin r...@databricks.com wrote: I pinged the IBM team to submit a patch that would work on IBM JVM. On Fri, Aug 14, 2015 at 11:27 AM, Pete Robbins robbin...@gmail.com wrote: ref: https

Reliance on java.math.BigInteger implementation

ref: https://issues.apache.org/jira/browse/SPARK-9370 The code to handle BigInteger types in org.apache.spark.sql.catalyst.expressions.UnsafeRowWriters.java and org.apache.spark.unsafe.Platform.java is dependant on the implementation of java.math.BigInteger eg: try {

[jira] [Commented] (SPARK-6873) Some Hive-Catalyst comparison tests fail due to unimportant order of some printed elements

[ https://issues.apache.org/jira/browse/SPARK-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14647322#comment-14647322 ] Pete Robbins commented on SPARK-6873: - We've been trying to get a clean build/test

Re: [VOTE] Graduate Apache Tuscany as a Top Level Project

lresende at apache dot org - Mark Combellack mcombellack at apache dot org - Matthieu Riou mriou at apache dot org - Mike Edwards edwardsmj at apache dot org - Paul Fremantle pzf at apache dot org - Pete Robbins robbinspg at apache dot org - Raymond Feng rfeng at apache

[jira] Assigned: (TUSCANY-2041) Repeated nill elements of extended type cause Parser found unknown element exception

[ https://issues.apache.org/jira/browse/TUSCANY-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Robbins reassigned TUSCANY-2041: - Assignee: Pete Robbins Repeated nill elements of extended type cause Parser found

[jira] Commented: (TUSCANY-2041) Repeated nill elements of extended type cause Parser found unknown element exception

[ https://issues.apache.org/jira/browse/TUSCANY-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12567999#action_12567999 ] Pete Robbins commented on TUSCANY-2041: --- I checked in a fix

Re: [C++] Decrease memory footprint of Tuscany Native?

I think the libxml2/iconv libraries are only required by SDO. Factoring SDO out of SCA implementation would require some substantial rework as we use SDO for parsing and loading our xml configuration files. Altering the way we do this would require a new method of parsing the files which again may

Re: BigBank C++ running problem

Has the ws extension been built and installed in your runtime? e.g. in deploy-dir/extensions/ws This extension should register the WebServiceBinding. Cheers, On 10/12/2007, Adriano Crestani [EMAIL PROTECTED] wrote: Hi, Can somebody help me with this problem:

Re: [SDO C++] Problem with special characters in property names

I've checked a fix for this into the branch. I'll apply it to head later. Cheers, On 22/11/2007, Pete Robbins [EMAIL PROTECTED] wrote: I'll need to look into this. I can't find any restrictions in the spec for characters in property names so I'm assuming NCName. So I think your patch looks

Re: [SDO C++] Escaping special characters in XML

I've applied this patch to the branch. I'll apply it to head later. I had to change a couple of lines to construct SDOString from a start and end iterator as this caused compile errors on VC8. Cheers, On 30/11/2007, Caroline Maynard [EMAIL PROTECTED] wrote: I've uploaded a proposed patch for

Re: [SDO C++] Problem with special characters in property names

I'll need to look into this. I can't find any restrictions in the spec for characters in property names so I'm assuming NCName. So I think your patch looks good. The usual place where hyphens in names become a problem is when mapping to programming language label but that is something that code

Re: Problem with ant on building TuscanyMSVC8DevStudioCCompiler adaptor tool

as it is, cause it will probably be deleted soon when the cpp-tasks bug is fixed. Do you have any news about a fix for this bug Brady? Regards, Adriano Crestani On Nov 7, 2007 3:45 AM, Pete Robbins [EMAIL PROTECTED] wrote: The jar files are checked in to svn so should not be deleted I guess

Re: Problem with ant on building TuscanyMSVC8DevStudioCCompiler adaptor tool

This jar file will have to be part of the Release distributions as well so we will need to include LICENCE information in a similar way to our scagen jar (cpp\sca\runtime\extensions\cpp\tools\scagen\META-INF) Cheers, On 07/11/2007, Pete Robbins [EMAIL PROTECTED] wrote: Yes, you're right we

Re: [Propose] A Tuscany Native release with SCA, SDO and DAS

@ws.apache.org Subject: Re: [Propose] A Tuscany Native release with SCA, SDO and DAS thanks brady ; ) On Nov 5, 2007 12:43 PM, Pete Robbins [EMAIL PROTECTED] wrote: good stuff. I'll check it out. On 05/11/2007, Brady Johnson [EMAIL PROTECTED] wrote: I just submit the first SCA

Re: Problem with ant on building TuscanyMSVC8DevStudioCCompiler adaptor tool

The jar files are checked in to svn so should not be deleted I guess?? It will be re-built if the java src gets updated. Cheers, On 07/11/2007, Adriano Crestani [EMAIL PROTECTED] wrote: All 3 native projects have a tool called TuscanyMSVC8DevStudioCCompiler that is an adaptor that fixes a bug

Re: [Propose] A Tuscany Native release with SCA, SDO and DAS

Up to now we have tried to keep the distros separate so that we could, for example, create an SDO release without SCA. I'd like to keep it like this. Cheers, On 04/11/2007, Adriano Crestani [EMAIL PROTECTED] wrote: Agreed ; ) Adriano Crestani On 11/2/07, Luciano Resende [EMAIL PROTECTED]

Re: [SDO C++] AccessViolation in XMLHelperImpl

Thanks for that. I'll fix it right away. On 02/11/2007, Caroline Maynard [EMAIL PROTECTED] wrote: A user has found a vulnerability in XMLHelperImpl::createDocument, the one with the const char * parameters. The problem being that the root element name is initialized with the parameter before

Re: [Native] VS build versus ant build

I think we should be using ant for everything. The goal is to have a command line build and ant will give us that. We need to ensure that the samples can also be built/deployed using an ant script and that the documentation is updated to reflect this. While we are at it we should write some ant

Re: RAT on Cpp trunk

On 05/11/2007, Adriano Crestani [EMAIL PROTECTED] wrote: I ran rat on the entire cpp trunk and got some thoughts about the results: 1-These files have no asf headers, however they have another lincense on it, so I don't know if the asf headers should be inserted or not:

Re: [Native] VS build versus ant build

to include sample source as well as a zip of the deployed runtime. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Monday, November 05, 2007 2:11 AM

Re: [Propose] A Tuscany Native release with SCA, SDO and DAS

Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Monday, November 05, 2007 1:34 AM To: tuscany-dev@ws.apache.org Subject: Re: [Propose] A Tuscany Native release with SCA, SDO and DAS Up to now we have tried to keep the distros

Re: [SCA Native] next release content [was: Tuscany roadmap]

On 10/23/07, Pete Robbins [EMAIL PROTECTED] wrote: I think this is one for the legal discuss list. This has been discussed before and I think the conclusion was that because you code to the cxxtest apis to write your test code it could be considered a derivative work. Cheers, On 23

[NOTICE] Michael Yoder voted as Tuscany committer

The Tuscany PPMC and Incubator PMC have voted for Michael to become a Tuscany committer. Congratulations and welcome! I look forward to your continued excellent contributions to Tuscany. Cheers, -- Pete - To unsubscribe,

Re: [SCA Native] next release content [was: Tuscany roadmap]

(architecture, get started and user doc) to help new people come on board faster? Another thought might be to have an integration story between Native and Java. Some of this work started for OSCon, for example a sample of a composite which include C++ and Java components. On 7/26/07, Pete Robbins

Re: [VOTE] Graduate Tuscany as a top level project

lresende at apache dot org Mike Edwards edwardsmj at apache dot org Pete Robbinsrobbinspg at apache dot org Raymond Feng rfeng at apache dot org Simon Laws slaws

Re: [SCA Native] Does the Operation class duplicate the SDO

is referencing the SDO, the memory will be released. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, September 27, 2007 2:50 PM To: tuscany-dev

Re: [SCA Native] Does the Operation class duplicate the SDO

I would imagine we can map the contents of the Operation into an SDO. Would this cope with pass by reference semantics? Would we be storing copies of the parameters in the SDO or pointers to them as is the case now with the Operation class? If so do we still get the same memory management problems

[jira] Closed: (TUSCANY-1529) Tuscany SDO native for windows is not msvc backwards compatible

[ https://issues.apache.org/jira/browse/TUSCANY-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Robbins closed TUSCANY-1529. - Resolution: Fixed Tuscany SDO native for windows is not msvc backwards compatible

[jira] Closed: (TUSCANY-1509) Change TuscanySDO Native build system to use ant

[ https://issues.apache.org/jira/browse/TUSCANY-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Robbins closed TUSCANY-1509. - Resolution: Fixed New Jiras will be raised fr any outstanding problems Change TuscanySDO

Re: SDO C++ M3 :: Tests passed: 100/118

Stansilaw, I have not seen these patces submitted and we can only accept them if they are attached to a Jira with the Licence to Apache checkbox ticked. Please let me know which Jira's these patches belong to. I don't recall seeing a memory leak defect. If you want an M3 + several bug fixes

Re: [jira] Updated: (TUSCANY-1370) C++ SDO spec compliance/portability: DataObject

I applied v2 and then v2_b Cheers, On 28/08/2007, Michael Yoder (JIRA) tuscany-dev@ws.apache.org wrote: [ https://issues.apache.org/jira/browse/TUSCANY-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Yoder updated TUSCANY-1370:

Re: FW: [jira] Updated: (TUSCANY-1548) multi-valued properties should require indexed xpath

Patch applied. Can you resolve/close the Jiras if the work is now complete on them? Cheers, On 28/08/2007, Michael Yoder [EMAIL PROTECTED] wrote: Hi, I have uploaded a patch for TUSCANY-1548. If someone could review and apply it that would be great. Thanks, Michael Rogue Wave Software,

Re: FW: [jira] Updated: (TUSCANY-1548) multi-valued properties should require indexed xpath

] Software Developer - HydraSDO -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 29, 2007 3:13 AM To: tuscany-dev@ws.apache.org Subject: Re: FW: [jira] Updated: (TUSCANY-1548) multi-valued properties should require indexed xpath Patch applied

Re: FW: [jira] Updated: (TUSCANY-1375) C++ SDO spec portability: C++ type definition API

Patch applied. One thing we need to do is update the NOTICE file to include the licence from the wsdl schema files. Cheers, On 30/08/2007, Michael Yoder [EMAIL PROTECTED] wrote: Hi, I uploaded an addendum patch to TUSCANY-1375. If someone could review and apply it that would be great.

Re: FW: [jira] Updated: (TUSCANY-1370) C++ SDO spec compliance/portability: DataObject

Hi, I have applied 1368 and 1374. This patch gets conflicts with the patches I've applied. They looked reasonably straight forward to resolve but I must have done something wrong as the sdo tests crash :-( Could you do an extract from HEAD and create a new patch for this Jira? Cheers, On

Re: FW: [jira] Updated: (TUSCANY-1368) C++ SDO portability: class interface Type off-spec enum values

to the spec committee. -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, June 21, 2007 9:21 AM To: tuscany-dev@ws.apache.org Subject: Re: SDO spec compliance/portability: Type enums the num_type is just a convenient way to know the extent of an enum

Re: FW: [jira] Updated: (TUSCANY-1371) C++ SDO spec compliance/portability: DataObject::getInstanceProperty(const std::string prop)

Applied now. Another great patch. Thanks! On 22/08/07, Michael Yoder [EMAIL PROTECTED] wrote: Hi, I uploaded a patch for TUSCANY-1371. If someone could review and apply it that would be great. Thanks, Michael -Original Message- From: Michael Yoder (JIRA) [mailto:[EMAIL

[jira] Commented: (TUSCANY-1566) Element coming out in the wrong namespace

[ https://issues.apache.org/jira/browse/TUSCANY-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521534 ] Pete Robbins commented on TUSCANY-1566: --- This should be fairly easy to fix. I think it is in the logic where

[jira] Resolved: (TUSCANY-1566) Element coming out in the wrong namespace

[ https://issues.apache.org/jira/browse/TUSCANY-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Robbins resolved TUSCANY-1566. --- Resolution: Fixed Fix Version/s: Cpp-Next Fixed in HEAD and the branch. Element

[jira] Commented: (TUSCANY-1564) xsi:type not always set for complexTypes

[ https://issues.apache.org/jira/browse/TUSCANY-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521605 ] Pete Robbins commented on TUSCANY-1564: --- I have applied a patch to the branch only which I believe works. I

Re: FW: [jira] Updated: (TUSCANY-1366) C++ SDO spec portability: SDORuntimeException off-spec member functions

to build Tuscany SCA. Since the SDO spec is separate from SCA, we were thinking this would be a good goal. That seems to mean making them internal to Tuscany SDO or taking them to the committee. Michael -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday

Re: [SCA Native] Next Release Design

Brady, sorry I haven't had too much time to comment on this but it all looks sensible and in the right direction to me. Regarding the schema loading, where you say sca-implementation-java.xsd (loaded but ignored) I think this means we will load this schema but as no extension is registered to

Re: [SCA Native] java implementation and interface schema files loaded but not used

On 14/08/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, The SCA Java runtime doesn't use the XSD for the assembly or extensions at runtime to parse the composite file. A StAX-based artifact processor is plugged into the runtime to handle the extensions such as implementation.java,

Re: [SCA Native] java implementation and interface schema files loaded but not used

On 13/08/07, David Haney [EMAIL PROTECTED] wrote: -Original Message- From: Jean-Sebastien Delfino [mailto:[EMAIL PROTECTED] Sent: Friday, August 10, 2007 8:33 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] java implementation and interface schema files loaded but

Re: [SCA Native] Test suite is stale and hasn't been maintained for ages

I've deleted this. It has been proposed several times to remove this and I've never seen any objections. It's gone! Cheers, On 13/08/07, Brady Johnson [EMAIL PROTECTED] wrote: I wrote a JIRA about this: https://issues.apache.org/jira/browse/TUSCANY-1533 Why don't we just delete it to

Re: [SCA Native] Tuscany SCA Native for Windows is not msvc backwards compatible

I've applied 1529 and 1530. Cheers, On 10/08/07, Brady Johnson [EMAIL PROTECTED] wrote: Hello all, I created a JIRA for this compilation issue and have already uploaded a patch. Can someone submit it please. https://issues.apache.org/jira/browse/TUSCANY-1530 Thanks

Re: FW: [jira] Updated: (TUSCANY-1375) C++ SDO spec portability: C++ type definition API

Another great patch! Thanks! Should SDO.h only include headers for the public (i.e. spec) APIs? I think it should so things like DASValue.h should be removed. Anyone who wants to utilize the internal APIs should have to know they are doing it! What do you think? Cheers, On 10/08/07, Michael

Re: FW: [jira] Updated: (TUSCANY-1376) C++ SDO spec portability: RefCountingPointer

to bool member function. -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 6:16 AM To: tuscany-dev@ws.apache.org Subject: Re: C++ SDO spec portability: RefCountingPointer Michael, I strongly suspect that the operator T*() ws put

Re: [SCA Native] preliminary ant build

] ruby.include.dir= /nfs/homes/bjohnson/tuscany_cpp/ruby-1.8.6/deploy/include [echo] BUILD SUCCESSFUL Total time: 1 second [EMAIL PROTECTED] sca]$ -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Friday, July 27, 2007 1:13 PM To: tuscany-dev

Re: [SDO Native] ant build system for SDO Native

Thanks. I'll get on the case soon. I really appreciate the effort you have put in to this. Cheers, On 07/08/07, Brady Johnson [EMAIL PROTECTED] wrote: Hello all, I just uploaded a patch for JIRA: https://issues.apache.org/jira/browse/TUSCANY-1509

Re: FW: [jira] Updated: (TUSCANY-1376) C++ SDO spec portability: RefCountingPointer

- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 6:16 AM To: tuscany-dev@ws.apache.org Subject: Re: C++ SDO spec portability: RefCountingPointer Michael, I strongly suspect that the operator T*() ws put in for a good reason. It may be a good idea to remove

[jira] Commented: (TUSCANY-1504) getSequence() returns null with a complexType defined without mixed=true

[ https://issues.apache.org/jira/browse/TUSCANY-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517911 ] Pete Robbins commented on TUSCANY-1504: --- Matthew, the speciifcation is available from here: http

SDO sequenced DataObject vs XSD sequence

A Jira (https://issues.apache.org/jira/browse/TUSCANY-1504) has been raised against the SDO C++ implementation which is saying that for a schema: ?xml version=1.0 encoding=UTF-8? xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; xmlns:letter=http://letterSchema;

Re: [SCA Native] preliminary ant build

Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, July 26, 2007 12:44 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build More good stuff. I've applied

Re: [SCA Native] preliminary ant build

and the basedir of the root project/ element. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Friday, July 27, 2007 3:15 AM To: tuscany-dev

Re: [SCA Native] preliminary ant build

and now I've moved the core schema to cpp/sca/runtime/core/xsd On 27/07/07, Pete Robbins [EMAIL PROTECTED] wrote: OK.. done! runtime/core/build.xml replaces runtime/core/src/build.xml I'll move the xsd dir later. Cheers, On 27/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Your changes

[jira] Resolved: (TUSCANY-1448) CppBigBank example windows deploy script deploy.bat fails to deploy XML Schema

[ https://issues.apache.org/jira/browse/TUSCANY-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Robbins resolved TUSCANY-1448. --- Resolution: Fixed patch applied CppBigBank example windows deploy script deploy.bat

[jira] Resolved: (TUSCANY-1423) There are no tools to verify or display tuscany services

[ https://issues.apache.org/jira/browse/TUSCANY-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Robbins resolved TUSCANY-1423. --- Resolution: Fixed I believe this is all applied now There are no tools to verify

Re: [SCA Native] Test suite

I'm sure this has come up before. I will try and find out what the resolution was. On 26/07/07, Brady Johnson [EMAIL PROTECTED] wrote: As I understand it, the only issue would be if we distribute LPGL software under the ASF licensing. What if we don't distribute CxxTest with Tuscany, but

Re: [SCA Native] next release content [was: Tuscany roadmap]

] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, July 12, 2007 11:00 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] next release content [was: Tuscany roadmap] On 12/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I forgot to mention another one

Re: [SCA Native] preliminary ant build

More good stuff. I've applied the latest patch but there are some issues. From a clean build if you just type ant in the top level cpp/sca directory then the build will fail on tuscany_sca_cpp because it needs to link against deploy_dir/lib/tuscany_sca.dll which has not yet been installed as

Re: [SCA Native] SDO Build error on Linux

Works fine on all our linuxes including my RHEL... I've removed the unnecessary qualifier so you should be fine now. Cheers, On 25/07/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: Trying to build Native/C++ SDO on Linux RHEL5 gives me this error: if /bin/sh ../../../../../libtool

[jira] Resolved: (TUSCANY-1425) Compile failure on Fedora 6

[ https://issues.apache.org/jira/browse/TUSCANY-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Robbins resolved TUSCANY-1425. --- Resolution: Fixed Fix Version/s: Cpp-Next Compile error fixed in branch and head

Re: [SCA Native] SDO Build error on Linux

The fix is in the branch as well. Sorry I did not see that Jira. On 25/07/07, Caroline Maynard [EMAIL PROTECTED] wrote: Jean-Sebastien Delfino wrote: Trying to build Native/C++ SDO on Linux RHEL5 gives me this error: if /bin/sh ../../../../../libtool --tag=CXX --mode=compile g++

Re: FW: [jira] Updated: (TUSCANY-1478) For schemas with elementFormDefault=true, serialized instance documents are invalid

I'm looking at it right now! On 25/07/07, Michael Yoder [EMAIL PROTECTED] wrote: Hi, I uploaded a patch for C++ SDO which fixes its XML serialization to produce XML valid against schemas with elementFormDefault=true. If someone could verify and apply it that would be great. This gets the SCA

[jira] Resolved: (TUSCANY-1478) For schemas with elementFormDefault=true, serialized instance documents are invalid

[ https://issues.apache.org/jira/browse/TUSCANY-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pete Robbins resolved TUSCANY-1478. --- Resolution: Fixed Fix Version/s: Cpp-Next Patch applied to HEAD and the sdo-cpp

Re: bad compile

Sorry for the slow response. The compiler errors suggest that LIBXML2_INCLUDE is not set?? You could try modifying build_sdocpp.sh adding an env to see what is set when the script is invoked. Cheers, On 20/07/07, brandon [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1

Re: [SCA Native] preliminary ant build

by the individual projects. It would be very similar to the root build.xml for TuscanySCA. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007

Re: [SCA Native] preliminary ant build

. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 2:44 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build

Re: [SCA Native] preliminary ant build

as a base for future patches? Cheers, On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I'll give this a go. I should be able to run it on Mac as well. Cheers, On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I updated the jira1438 with update 3, which includes the following: https

Re: [SCA Native] preliminary ant build

the definition of the Tuscany-BaseCompiler Cheers, On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I've applied the patch. How are you creating the patches? I had trouble applying it on Windows using ToirtoiseSVN. I've included the changes in the patch to the tools/TuscanyDriver build. I haven't

Re: [SCA Native] preliminary ant build

/target Tomorrow I'll have the python, ruby, rest, and maybe php extensions complete. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Monday

Re: [SCA Native] preliminary ant build

inline --- /* #undef inline */ -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 4:22 PM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build yeah I figured that... I did exactly the same when committing changes earlier

Re: [SCA Native] preliminary ant build

I've taken out the references to tuscany_sca_config.h and patched the automake for now with setting -DIS_DARWIN on mac. Yet to test it on Mac as I need to kick the kids off my machine! On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote: Automake generates a config file with lots of standard

Re: [SCA Native] preliminary ant build

dont have write access to %ANT_HOME%\lib, do the following: - create ${user.home}\.ant\lib - place the jars here Avoid adding optional ant tasks to your classpath, this is problematic. -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 17, 2007 1:24 AM

Re: [SCA Native] preliminary ant build

make sense? Cheers, On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I'd like some info on what I need to edit in the platform.properties. Particularly: platform.compiler-definition=g++m32 platform=rhas4u4_gcc346 One good thing about automake is that it detects your platform/compiler etc

Re: [SCA Native] preliminary ant build

On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I ran into a couple of issues tryingt o run this ant build. Firstly I got an error with a path x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to the fact that the property core.dir is set in the top level build.xml

Re: [SCA Native] preliminary ant build

build.xml I added: property name=tuscanySCA.root.dir location=$env.PWD} / and then based other properties from this. It seemed to work! Do these changes make sense? Cheers, On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I'd like some info on what I need to edit in the platform.properties

Re: [SCA Native] preliminary ant build

On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, Thanks for trying out the ant build scripts. Regarding core.dir, you're right, the name will need to change. I can do that no problem. As for the tuscanySCA.root.dir : Your

Re: [SCA Native] preliminary ant build

Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 9:00 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, Thanks for trying out the ant

Re: [SCA Native] preliminary ant build

] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 9:00 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote

<    1   2   3   4   5   6   7   8   9   10   >