there seems to be a build problem. I downloaded the contents of https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk once again to T:\source_current, switched to the distribution directory and ran "mvn -DskipTests=true".
Do I have to build the source another way? Because with this procedure, strangely, although modules\databinding-sdo\src\main\java\org\apache\tuscany\sca\databinding\sdo\SDOTypeHelper.java contains the new coding, when I decompile distribution\target\apache-tuscany-sca-1.7-SNAPSHOT.dir\tuscany-sca-1.7-SNAPSHOT\modules\tuscany-databinding-sdo-1.7-SNAPSHOT.jar I do not see that new coding, as if there were another source for that jar. For another thing, I get an error because a path does not exist [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to create assembly: Error creating assembly archive featurecore: Manifest not found: T:\source_current\too ls\eclipse\features\core\target\classes\META-INF\MANIFEST.MF (Das System kann den angegebenen Pfad nicht finden) Can anyone see what may be wrong? -- Sebastian > -----Original Message----- > From: Simon Nash [mailto:[email protected]] > Sent: Wednesday, November 24, 2010 11:41 AM > To: [email protected] > Subject: Re: FW: [jira] Resolved: (TUSCANY-3797) Tuscany generates > incorrect WSDL for SDO > > Millies, Sebastian wrote: > > Hello Simon, > > > > thanks for the fix. Is it in the current code line? Could it > > be included in the planned 1.6.1 release as well? > > > > I just (a few hours ago) downloaded and built the source > > from https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk > > but I still see the > > <xs:import namespace="http://sdo.commonj/"/> > > in my wsdl. > > > The fix was committed to the 1.x trunk at 11.43 am GMT on 23 November. > It's in the databinding-sdo module and it adds the following code to > SDOTypeHelper.java around line 73: > } else if (javaType == commonj.sdo.DataObject.class) { > return new TypeInfo(SimpleTypeMapperImpl.XSD_ANYTYPE, true, > null); > > If you have this fix and are still getting the import generated, please > reopen TUSCANY-3797 and post a complete test case there. > > Simon >
