I think this behaviour was intentional due to a statement in the WSRF spec:
"A resource property element must appear as the immediate child of the root element of a resource properties document." Unless we've misinterpreted that statement, in order for a resource property element to be the immediate child of the resource properties document it would need to be declared under the element declaration of the resource properties document....I realize this is just semantics, but that line of the spec is where we got the idea to impose that restriction....It's the difference of how the document is statically defined vs. its instance doc.... -----Original Message----- From: Murray, Bryan P. Sent: Monday, March 14, 2005 4:47 PM To: [email protected] Subject: Resource Property doc definition I started working with the Alpha 2 version of Apollo. Its great to be able to import a schema from the WSDL doc. Thanks for getting this working so quickly. I tried declaring the resource property document element as follows: <complexType name="FooPropertiesType"> <sequence> </sequence> </complexType> <element name="FooProperties" type="tns:FooPropertiesType"/> Tns is defined for the target namespace of this document. I get an error saying it is necessary to either include the type attribute or include the complexType within the element. The work-around I used successfully was to move the complexType be be a child of the element for the resource properties doc. Bryan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
