+1 on the multiple <xsd:any/>, I don't really know what the precise semantic is. Do they collapse into one? How do you deal with multiplicity? ... Anyway, the toolings I've worked with seems to be able to cope with that (SOAPScape and Sun J2EE server). Another way we can do this is to define the new Application element and manually add all the posix:XYZ elements that we need in a sequence without using any of the XSD extension mechanism. William --- William Lee - Software Coordinator --- --- London e-Science Centre, Imperial College London --- A: Room 380, Department of Computing, Imperial College London, Huxley Building, South Kensington campus, London SW7 2AZ, UK E: wwhl at doc.ic.ac.uk | william at imageunion.com W: www.lesc.ic.ac.uk | www.imageunion.com P: +44(0)20 7594 8310 F: +44(0)20 7581 8024 -----Original Message----- From: Donal K. Fellows [mailto:donal.k.fellows@manchester.ac.uk] Sent: 23 February 2006 13:12 To: Lee, William Cc: JSDL WG Subject: Re: [jsdl-wg] Future plans for JSDL Lee, William wrote:
Roughly.... <xsd:complexType name="MPIApplicationType"> <xsd:complexContent> <xsd:extension base="jsdl-posix:POSIXApplication_Type"> <xsd:sequence> <xsd:element ref="ProcessorCount"/> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType>
How does that work with <xsd:any>? When I've tried that sort of thing, the results have tended to be less than satisfactory when tooled up (multiple anys in the element, etc.) Donal.