On Wed, Jan 11, 2012 at 2:36 PM, Millies, Sebastian <[email protected]> wrote: >> -----Original Message----- >> From: Simon Laws [mailto:[email protected]] >> Sent: Wednesday, January 11, 2012 3:23 PM >> To: [email protected] >> Subject: Re: Possible bug resolving resource imports >> >> On Tue, Jan 10, 2012 at 10:02 AM, Millies, Sebastian >> <[email protected]> wrote: > [snip] >> > >> > The problem is that the presence of c3 HIDES the imports that are >> > present in c2 at the >> > time the composite is resolved. > [snip] >> As a matter of interest how have you constructed the import/export >> statements in the sca-contribution.xml files. I'm interested that you >> mention ArtifactModelResolver. I'd assumed you would be using, for >> example, <import uri="namespace of xsd/>. >> >> Regards >> >> Simon > > I am using three kinds of imports, here are examples: > > <import namespace="http://ps.softwareag.com/job-manager/"/> > <import.resource uri="SDOTypes/job.xsd"/> > <import.java package="com.softwareag.ps.platform.batchjob" /> > > I use namespace imports only for implementation.composite. > XSD files are imported using resource imports and then included in > composites this way: <dbsdo:import.sdo location="SDOTypes/job.xsd"/> > > -- Sebastian > > IDS Scheer Consulting GmbH > Geschäftsführer/Managing Directors: Kamyar Niroumand, Ivo Totev > Sitz/Registered office: Altenkesseler Straße 17, 66115 Saarbrücken, Germany - > Registergericht/Commercial register: Saarbrücken HRB 19681 > http://www.softwareag.com >
Ok, I can believe there are bugs in import/export.resource as I don't think that's been used as much as the default import based on namespaces. Might be interesting to try importing the xsd by namespace and see if you get different results. Are you able to share your failing test case? Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
