On Wed, Jul 14, 2010 at 9:59 AM, ant elder <[email protected]> wrote: > On Wed, Jul 14, 2010 at 9:12 AM, Simon Laws <[email protected]> wrote: >>>> >>>> A full build to test the 2022 changes has made 2016 work somewhat >>>> mysteriously. >>> >>> 2016 is one of the ones i'd fixed >>> >>>> mysteriously. I'm still not seeing failures in 5001 so would be >>>> interested in hearing if anyone else is. >>>> >> >> I only meant that I thought that I had the latest code, including all >> your fixes, and I was still seeing 2016 fail in my previous post. >> However I must have been doing something wrong as it subsequently >> worked. >> >>> >>> 5001 is still failing for me on the very latest otest and trunk code. >>> I'll do some debugging. >>> >>> ...ant >>> >> >> Ok, splendid. >> >> Simon >> >> > > Is it possible that you've local changes that aren't checked in? I'm > also getting itest fails eg in itest/ws/wsdl: > > Caused by: org.oasisopen.sca.ServiceRuntimeException: Component > AccountService Service Account interface is incompatible with the > interface of the reference binding - Account - Operations called > getCustomerProfile are not compatible Operation argument types source > = {http://accounts}customerProfileData target = customerProfileData > don't match for output types - [(@16166715)Endpoint: URI = > AccountService#service-binding(Account/Account)] > > ...ant >
Ooops, this is the thing I mentioned in my commit comment about the WSDL gen not getting the namespaces quite right. I missed out my fix for it. Checked in at r963981 Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
